From spp at 123GREETINGS.COM  Mon Mar  4 20:39:01 2002
From: spp at 123GREETINGS.COM (Greetings Card from Lili)
Date: Mon Mar  4 20:39:01 2002
Subject: [interchange-i18n] An E-Card for you!
Message-ID: <200203050138.g251cbJ12021@interchange.redhat.com>

An HTML attachment was scrubbed...
URL: http://www.icdevgroup.org/pipermail/interchange-i18n/attachments/20020304/9e0d02a3/attachment.htm 

From ehms at lipsia.net  Fri Mar  8 07:39:00 2002
From: ehms at lipsia.net (Holger Ehms)
Date: Fri Mar  8 07:39:00 2002
Subject: [interchange-i18n] LC-Statement
Message-ID: <3C88B08C.2030004@lipsia.net>

Hi,
I try to use the [LC] [/LC] statement in a catalog-side without any 
success.
At the same time the [L] [/L] statement works.
(I find some archived mail containing the same problem, but no solution 
on this.)

How can I find out the cause of this problem?

Holger



From dogtags at doglover.com  Fri Mar  8 13:50:00 2002
From: dogtags at doglover.com (Dog Tags)
Date: Fri Mar  8 13:50:00 2002
Subject: [interchange-i18n] Newbie - converting all product data to multiple languages -
 using multiple tables
Message-ID: <20020308184822.22854.qmail@mail.com>

Hi All

Would someone be able to explain the ABC's of adding extra tables or fields to allow total product data translation.

I have read the manual several times, and I'm having a hard time getting started.

What I want to do is 1) offer up to 6 languages on the site, 2) translate all site navigation and other buttons, and 3) also translate all product data.

This would all be accomplished through a Preferences select box type of thing.

I imagine that the nav buttons and other standard site features can be translated using a text file, but the big thing for me is how to make the product data translated. Should I create a separate table for each language to help with search speed? I'm using mysql.

I think that once I get started in the right direction that I'll be okay.

Thanks very much for your help. 

DT

-- 

_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Travelocity.com is giving away two million travel miles.
http://ad.doubleclick.net/clk;3969773;6991039;g?http://svc.travelocity.com/promos/millionmiles_main/0,,TRAVELOCITY,00.html



From racke at linuxia.de  Sat Mar  9 09:43:01 2002
From: racke at linuxia.de (Stefan Hornburg Racke)
Date: Sat Mar  9 09:43:01 2002
Subject: [interchange-i18n] LC-Statement
In-Reply-To: <3C88B08C.2030004@lipsia.net>
References: <3C88B08C.2030004@lipsia.net>
Message-ID: <87u1rpvkpw.fsf@snowflake.linuxia.de>

Holger Ehms <ehms at lipsia.net> writes:

> Hi,
> I try to use the [LC] [/LC] statement in a catalog-side without any success.
> 
> At the same time the [L] [/L] statement works.
> (I find some archived mail containing the same problem, but no solution on
> this.)

[LC] should work.

> 
> 
> How can I find out the cause of this problem?

Maybe post an example for failing [LC] with a more thorough description.

Ciao
        Racke

-- 
Think of it !

For projects and other business stuff please refer to COBOLT NetServices
(URL: http://www.cobolt.net; Email: info at cobolt.net; Phone: 0041-1-3884400)


From michel.matte at sympatico.ca  Sat Mar  9 11:41:01 2002
From: michel.matte at sympatico.ca (Michel Matte)
Date: Sat Mar  9 11:41:01 2002
Subject: [interchange-i18n] Newbie - converting all product data to multiple 
 languages -using multiple tables
References: <20020308184822.22854.qmail@mail.com>
Message-ID: <3C8A3E37.D5FBC830@sympatico.ca>


Dog Tags wrote:

>
> What I want to do is 1) offer up to 6 languages on the site, 2) translate all site navigation and other buttons, and 3) also translate all product data.
>

You can place translations in locale.txt or in a separate file: yourlocale.cfg (
i. e. es_ES.cfg) in yourcat/config.  This file can then be included in your
catalog.cfg with include statement or incorporated as a Here document.but the
locale.txt setting take precedence over individual locale files.

Using locale.cfg (one for each translation ) files is more manageable but you have to set tags [L text_no] [/l]
inside the pages and [msg text_no]  [/msg] inside templates.  [LC]...[/LC] tags and translations can also  be used inside pages but appear to be less efficient.

> This would all be accomplished through a Preferences select box type of thing.

The following is from Racke:
You can switch the locale by calling (replace de_DE with the proper locale)
process/locale/de_DE/page/index
instead of
index

The locale is then stored in [scratch mv_locale]


> I imagine that the nav buttons and other standard site features can be translated using a text file,

No, you have to create button gif images for each language.

> but the big thing for me is how to make the product data translated. Should I create a separate table for each language to help with search speed? I'm using mysql.

You can add fields in product by deleting the Mysql and recreating from a txt file.  I am using GDBM and I edit the txt file and restart Interchange (not sure about MySQL). These fields are then referenced  by the DescriptionField defined for each locale in
catalog.cfg.  I didn't bother to do it I just created different products and selected the correct one depending on [L] ..[/L] tags. This is not the recommended method for accounting.




From ehms at lipsia.net  Mon Mar 11 09:28:01 2002
From: ehms at lipsia.net (Holger Ehms)
Date: Mon Mar 11 09:28:01 2002
Subject: [interchange-i18n] Re: LC-Statement
Message-ID: <3C8CBE98.90603@lipsia.net>

Stefan Hornburg Racke wrote:

 >> I try to use the [LC] [/LC] statement in a catalog-side without any 
success.
 >>
 >> At the same time the [L] [/L] statement works.
 >> (I find some archived mail containing the same problem, but no 
solution on
 >> this.)
 >
 >[LC] should work.
 >
 >Maybe post an example for failing [LC] with a more thorough description.
 >
You can see the example:
http://www.lipsia.net/cgi-bin/sqltest/index.html

The rest of "index.html" is original from foundation.

<!-- BEGIN CONTENT -->
<table width="95%" border="0">
<tr>
   <td>
     <br>
     Willkommen im <b>Interchange</b> Testshop der Fischer & Ehms KG! <br>
     <br>
     [setlocale en_US] default locale is de_DE (from catalog.cfg)
     <p>
     [L test]en_US or de_DE [/L]
     <p>
     [LC]
           This will not work.
     [en_US]I can't get this![/en_US]
     [de_DE]Oh, es funktioniert doch![/de_DE]
     [/LC]
     <p>
     The "setlocale en_US" takes effekt only for the other component of 
this side (currency-symbol is "$")!
</tr>
</table>

<!-- END CONTENT -->

Thanks!



From jon at redhat.com  Mon Mar 11 09:54:00 2002
From: jon at redhat.com (Jon Jensen)
Date: Mon Mar 11 09:54:00 2002
Subject: [interchange-i18n] Re: LC-Statement
In-Reply-To: <3C8CBE98.90603@lipsia.net>
Message-ID: <Pine.LNX.4.33L2.0203110948100.1386-100000@louche.swelter.net>

On Mon, 11 Mar 2002, Holger Ehms wrote:

> You can see the example:
> http://www.lipsia.net/cgi-bin/sqltest/index.html
>
> The rest of "index.html" is original from foundation.
>
> <!-- BEGIN CONTENT -->
> <table width="95%" border="0">
> <tr>
>    <td>
>      <br>
>      Willkommen im <b>Interchange</b> Testshop der Fischer & Ehms KG! <br>
>      <br>
>      [setlocale en_US] default locale is de_DE (from catalog.cfg)
>      <p>
>      [L test]en_US or de_DE [/L]
>      <p>
>      [LC]
>            This will not work.
>      [en_US]I can't get this![/en_US]
>      [de_DE]Oh, es funktioniert doch![/de_DE]
>      [/LC]
>      <p>
>      The "setlocale en_US" takes effekt only for the other component of
> this side (currency-symbol is "$")!

[L] and [LC] are not standard Interchange tags -- they're preprocessing
directives done at the time the page is loaded, before just about anything
else. Then later your [setlocale] tag is parsed, but by then the [L] and
[LC] are already done.

Alternatives are:

1. Set the locale before the page you're on (using .autoload, or setting
on a previous page, or in the URL, etc.).

2. Use the [loc] or [msg] tags for locale stuff; they *are* standard IC
tags and will parse in the expected order.

I think you can replace [LC]...[/LC] with [msg lc=1]...[/msg] in the above
example and it should work.

Jon



From dogtags at doglover.com  Tue Mar 12 16:41:00 2002
From: dogtags at doglover.com (Dog Tags)
Date: Tue Mar 12 16:41:00 2002
Subject: [interchange-i18n] Newbie - converting all languages -using
    multiple tables
Message-ID: <20020312213956.86549.qmail@mail.com>

 > Dog Tags wrote: 
 > 
 > > 
 > > What I want to do is 1) offer up to 6 languages on the site, 2) translate all site navigation and other buttons, and 3) also translate all product data. 
 > > 
 > 
 > You can place translations in locale.txt or in a separate file: yourlocale.cfg ( 
 > i. e. es_ES.cfg) in yourcat/config. This file can then be included in your 
 > catalog.cfg with include statement or incorporated as a Here document.but the 
 > locale.txt setting take precedence over individual locale files. 
 > 
 > Using locale.cfg (one for each translation ) files is more manageable but you have to set tags [L text_no] [/l] 
 > inside the pages and [msg text_no] [/msg] inside templates. [LC]...[/LC] tags and translations can also be used inside pages but appear to be less efficient. 
 > 
 > > This would all be accomplished through a Preferences select box type of thing. 
 > 
 > The following is from Racke: 
 > You can switch the locale by calling (replace de_DE with the proper locale) 
 > process/locale/de_DE/page/index 
 > instead of 
 > index 
 > 
 > The locale is then stored in [scratch mv_locale] 
 > 
 > 
 > > I imagine that the nav buttons and other standard site features can be translated using a text file, 
 > 
 > No, you have to create button gif images for each language. 
 > 
 > > but the big thing for me is how to make the product data translated. Should I create a separate table for each language to help with search speed? I'm using mysql. 
 > 
 > You can add fields in product by deleting the Mysql and recreating from a txt file. I am using GDBM and I edit the txt file and restart Interchange (not sure about MySQL). These fields are then referenced by the DescriptionField defined for each locale in 
> catalog.cfg. I didn't bother to do it I just created different products and selected the correct one depending on [L] ..[/L] tags. This is not the recommended method for accounting. 
 > 
> --__--__-- 
 
 Thanks very much for your help, Michel. I'll start to work with your suggestions as soon as possible. I'm looking forward to this. 
 
 Thanks, again. 
 
DT 

-- 

_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Travelocity.com is giving away two million travel miles.
http://ad.doubleclick.net/clk;3969773;6991039;g?http://svc.travelocity.com/promos/millionmiles_main/0,,TRAVELOCITY,00.html



From maint at intercollab.net  Wed Mar 13 04:59:00 2002
From: maint at intercollab.net (Alexander Fedorenko)
Date: Wed Mar 13 04:59:00 2002
Subject: [interchange-i18n] Options localization
Message-ID: <002501c1ca75$a7d9d5a0$0400a8c0@pluto>

Hello.

Does anybody succeed in product options localization ?



From ehms at lipsia.net  Thu Mar 14 04:36:01 2002
From: ehms at lipsia.net (Holger Ehms)
Date: Thu Mar 14 04:36:01 2002
Subject: [interchange-i18n] Re: LC-Statement
Message-ID: <3C906EBB.9050400@lipsia.net>

Jon Jensen wrote:

 >> ...
 > [L] and [LC] are not standard Interchange tags -- they're preprocessing
 > directives done at the time the page is loaded, before just about 
anything
 > else. Then later your [setlocale] tag is parsed, but by then the [L] and
 > [LC] are already done.
 >
 > Alternatives are:
 >
 > 1. Set the locale before the page you're on (using .autoload, or setting
 > on a previous page, or in the URL, etc.).
 >
 > 2. Use the [loc] or [msg] tags for locale stuff; they *are* standard IC
 > tags and will parse in the expected order.
 >
 > I think you can replace [LC]...[/LC] with [msg lc=1]...[/msg] in the 
above
 > example and it should work.
 >
 > Jon

Hi Jon,

In the archive of this mailing list I found some examples using 
[setlocale xx_XX] for testing "[L]" and "[LC]", changing the locale 
successively in one page. That's why I wondered that the tag dosn't work 
in my example.
Regarding the [LC] tag Racke always wrote "[LC] should work.", but how I 
see some people found, that it may not work in some cases.
I try to understand where it will work and where it's better to use 
[loc] or [msg] tags.

Holger



From jon at redhat.com  Thu Mar 14 11:02:00 2002
From: jon at redhat.com (Jon Jensen)
Date: Thu Mar 14 11:02:00 2002
Subject: [interchange-i18n] Re: LC-Statement
In-Reply-To: <3C906EBB.9050400@lipsia.net>
Message-ID: <Pine.LNX.4.33L2.0203141100410.1346-100000@louche.swelter.net>

On Thu, 14 Mar 2002, Holger Ehms wrote:

> Jon Jensen wrote:
>
>  > [L] and [LC] are not standard Interchange tags -- they're preprocessing
>  > directives done at the time the page is loaded, before just about
> anything
>  > else. Then later your [setlocale] tag is parsed, but by then the [L] and
>  > [LC] are already done.
>  >
>  > Alternatives are:
>  >
>  > 1. Set the locale before the page you're on (using .autoload, or setting
>  > on a previous page, or in the URL, etc.).
>  >
>  > 2. Use the [loc] or [msg] tags for locale stuff; they *are* standard IC
>  > tags and will parse in the expected order.
>  >
>  > I think you can replace [LC]...[/LC] with [msg lc=1]...[/msg] in the
> above
>  > example and it should work.
>
> In the archive of this mailing list I found some examples using
> [setlocale xx_XX] for testing "[L]" and "[LC]", changing the locale
> successively in one page. That's why I wondered that the tag dosn't work
> in my example.
> Regarding the [LC] tag Racke always wrote "[LC] should work.", but how I
> see some people found, that it may not work in some cases.
> I try to understand where it will work and where it's better to use
> [loc] or [msg] tags.

So did you try my suggestion or not? Did it work?

Jon



From ehms at lipsia.net  Fri Mar 15 03:01:01 2002
From: ehms at lipsia.net (Holger Ehms)
Date: Fri Mar 15 03:01:01 2002
Subject: [interchange-i18n] Re: LC-Statement
References: <Pine.LNX.4.33L2.0203141100410.1346-100000@louche.swelter.net>
Message-ID: <3C91A9FD.1080007@lipsia.net>

Jon Jensen wrote:
> On Thu, 14 Mar 2002, Holger Ehms wrote:
> 
> 
>>Jon Jensen wrote:
>>
>> > [L] and [LC] are not standard Interchange tags -- they're preprocessing
>> > directives done at the time the page is loaded, before just about
>>anything
>> > else. Then later your [setlocale] tag is parsed, but by then the [L] and
>> > [LC] are already done.
>> >
>> > Alternatives are:
>> >
>> > 1. Set the locale before the page you're on (using .autoload, or setting
>> > on a previous page, or in the URL, etc.).
>> >
>> > 2. Use the [loc] or [msg] tags for locale stuff; they *are* standard IC
>> > tags and will parse in the expected order.
>> >
>> > I think you can replace [LC]...[/LC] with [msg lc=1]...[/msg] in the
>>above
>> > example and it should work.
>>
>>In the archive of this mailing list I found some examples using
>>[setlocale xx_XX] for testing "[L]" and "[LC]", changing the locale
>>successively in one page. That's why I wondered that the tag dosn't work
>>in my example.
>>Regarding the [LC] tag Racke always wrote "[LC] should work.", but how I
>>see some people found, that it may not work in some cases.
>>I try to understand where it will work and where it's better to use
>>[loc] or [msg] tags.
>>
> 
> So did you try my suggestion or not? Did it work?
> 
> Jon

Sorry, I did not find an example for [msg]. Is this right?

     [msg lc=1]
           This will not work.
     [en_US]I can't get this![/en_US]
     [de_DE]Oh, es funktioniert doch![/de_DE]
     [/msg]

It dosn't work.

Holger



From goetz.verdieck at com4office.de  Fri Mar 15 08:44:24 2002
From: goetz.verdieck at com4office.de (G=?ISO-8859-1?B?9g==?=tz Verdieck)
Date: Fri Mar 15 08:44:24 2002
Subject: [interchange-i18n] mv_metatag.asc
Message-ID: <B8B7B728.63FC%goetz.verdieck@com4office.de>

Hi,

I tried to change the metatag custview::userdb::mail_list from :
newsletter=Newsletter, alert=Alerts and Recalls, upgrade=Upgrades to:
offer=Angebote, newsletter=Newsletter
I can see the changes in the Admin interface an in the mv_metatag.asc
But my catalog does not show the changes the old values come up.

How do I localize the metatags ?
Shall I use the same procedure like the one with the [L] tag ?
I think the [L] tag is only usable for small databases and not very effectiv
for sites with a lot of pages.


Thanks in advance

Goetz Verdieck

==============================
Goetz.Verdieck at com4office.de






From racke at linuxia.de  Fri Mar 15 08:46:01 2002
From: racke at linuxia.de (Stefan Hornburg Racke)
Date: Fri Mar 15 08:46:01 2002
Subject: [interchange-i18n] Re: LC-Statement
In-Reply-To: <3C91A9FD.1080007@lipsia.net>
References: <Pine.LNX.4.33L2.0203141100410.1346-100000@louche.swelter.net>
	<3C91A9FD.1080007@lipsia.net>
Message-ID: <87heni0wx6.fsf@snowflake.linuxia.de>

Holger Ehms <ehms at lipsia.net> writes:


[...]

> 
> Sorry, I did not find an example for [msg]. Is this right?
> 
>      [msg lc=1]
>            This will not work.
>      [en_US]I can't get this![/en_US]
>      [de_DE]Oh, es funktioniert doch![/de_DE]
>      [/msg]
> 
> It dosn't work.

There is no lc option for the msg tag. RTSL implies that
inline is the option to use, so:

[msg inline=1]
            This will not work.
      [en_US]I can't get this![/en_US]
      [de_DE]Oh, es funktioniert doch![/de_DE]
[/msg]

might be worth a try.

Ciao
        Racke

-- 
Think of it !

For projects and other business stuff please refer to COBOLT NetServices
(URL: http://www.cobolt.net; Email: info at cobolt.net; Phone: 0041-1-3884400)


From ehms at lipsia.net  Fri Mar 15 09:25:00 2002
From: ehms at lipsia.net (Holger Ehms)
Date: Fri Mar 15 09:25:00 2002
Subject: [interchange-i18n] Re: LC-Statement
References: <Pine.LNX.4.33L2.0203141100410.1346-100000@louche.swelter.net>	<3C91A9FD.1080007@lipsia.net> <87heni0wx6.fsf@snowflake.linuxia.de>
Message-ID: <3C9203ED.1040206@lipsia.net>

Stefan Hornburg (Racke) wrote:
> Holger Ehms <ehms at lipsia.net> writes:
> 
> 
> [...]
> 
> 
>>Sorry, I did not find an example for [msg]. Is this right?
>>
>>     [msg lc=1]
>>           This will not work.
>>     [en_US]I can't get this![/en_US]
>>     [de_DE]Oh, es funktioniert doch![/de_DE]
>>     [/msg]
>>
>>It dosn't work.
>>
> 
> There is no lc option for the msg tag. RTSL implies that
> inline is the option to use, so:
> 
> [msg inline=1]
>             This will not work.
>       [en_US]I can't get this![/en_US]
>       [de_DE]Oh, es funktioniert doch![/de_DE]
> [/msg]
> 
> might be worth a try.
> 
> Ciao
>         Racke
> 
No way? It dosn't work.

Holger



From racke at linuxia.de  Fri Mar 15 10:39:01 2002
From: racke at linuxia.de (Stefan Hornburg Racke)
Date: Fri Mar 15 10:39:01 2002
Subject: [interchange-i18n] Re: LC-Statement
In-Reply-To: <3C9203ED.1040206@lipsia.net>
References: <Pine.LNX.4.33L2.0203141100410.1346-100000@louche.swelter.net>
	<3C91A9FD.1080007@lipsia.net> <87heni0wx6.fsf@snowflake.linuxia.de>
	<3C9203ED.1040206@lipsia.net>
Message-ID: <87adt9yh8l.fsf@snowflake.linuxia.de>

Holger Ehms <ehms at lipsia.net> writes:

> Stefan Hornburg (Racke) wrote:
> > Holger Ehms <ehms at lipsia.net> writes:
> > [...]
> 
> >
> 
> >>Sorry, I did not find an example for [msg]. Is this right?
> >>
> >>     [msg lc=1]
> >>           This will not work.
> >>     [en_US]I can't get this![/en_US]
> >>     [de_DE]Oh, es funktioniert doch![/de_DE]
> >>     [/msg]
> >>
> >>It dosn't work.
> >>
> > There is no lc option for the msg tag. RTSL implies that
> 
> > inline is the option to use, so:
> > [msg inline=1]
> 
> >             This will not work.
> >       [en_US]I can't get this![/en_US]
> >       [de_DE]Oh, es funktioniert doch![/de_DE]
> > [/msg]
> > might be worth a try.
> 
> > Ciao
> 
> >         Racke
> >
> 
> No way? It dosn't work.

[msg inline=1]
[en_US]foo[/en_US]
[de_DE]bar[/de_DE]
[/msg]

works definitely. 

Ciao
        Racke

-- 
Think of it !

For projects and other business stuff please refer to COBOLT NetServices
(URL: http://www.cobolt.net; Email: info at cobolt.net; Phone: 0041-1-3884400)


From ehms at lipsia.net  Sat Mar 16 11:50:01 2002
From: ehms at lipsia.net (Holger Ehms)
Date: Sat Mar 16 11:50:01 2002
Subject: [interchange-i18n] Re: LC-Statement
References: <Pine.LNX.4.33L2.0203141100410.1346-100000@louche.swelter.net>	<3C91A9FD.1080007@lipsia.net> <87heni0wx6.fsf@snowflake.linuxia.de>	<3C9203ED.1040206@lipsia.net> <87adt9yh8l.fsf@snowflake.linuxia.de>
Message-ID: <3C93776D.1050609@lipsia.net>

Stefan Hornburg (Racke) wrote:
> 
> [msg inline=1]
> [en_US]foo[/en_US]
> [de_DE]bar[/de_DE]
> [/msg]
> 
> works definitely. 
> 
Yes, this works. - Thank You!

Have You any idea why the the [LC]-tag will not work? May it bee a 
configuration problem?

Holger



From racke at linuxia.de  Mon Mar 18 05:28:01 2002
From: racke at linuxia.de (Stefan Hornburg Racke)
Date: Mon Mar 18 05:28:01 2002
Subject: [interchange-i18n] Re: LC-Statement
In-Reply-To: <3C93776D.1050609@lipsia.net>
References: <Pine.LNX.4.33L2.0203141100410.1346-100000@louche.swelter.net>
	<3C91A9FD.1080007@lipsia.net> <87heni0wx6.fsf@snowflake.linuxia.de>
	<3C9203ED.1040206@lipsia.net> <87adt9yh8l.fsf@snowflake.linuxia.de>
	<3C93776D.1050609@lipsia.net>
Message-ID: <878z8qgoiv.fsf@snowflake.linuxia.de>

Holger Ehms <ehms at lipsia.net> writes:

> Stefan Hornburg (Racke) wrote:
> > [msg inline=1]
> 
> > [en_US]foo[/en_US]
> > [de_DE]bar[/de_DE]
> > [/msg]
> > works definitely.
> 
> Yes, this works. - Thank You!
> 
> Have You any idea why the the [LC]-tag will not work? May it bee a
> configuration problem?

It won't work with variables. The same problem applies to 
components, I guess. 

With current CVS of stable you can wrap any chunk of text with
[parse_locale]__VAR_WITH_L_TAGS__[/parse_locale]
to replace the L+LC tags.

Ciao
        Racke

-- 
Think of it !

For projects and other business stuff please refer to COBOLT NetServices
(URL: http://www.cobolt.net; Email: info at cobolt.net; Phone: 0041-1-3884400)