Re: [Phpslash-devel] i18n

[Joe S. <joe...@us...>]

On Wed, Jul 16, 2003 at 06:37:32PM -0400, Luis M wrote:
> >
> >I use phpslash-0.7.2 for a German speaking site.
> >Consequently I need a complete translation.
> >As far as I see, the procedure is as follows:
> >
> 
> I do the spanish translation (most of the time) and I can relate to you on 
> this...
> 
> >Once you find a string in a template you
> >1. create a entry in include/locale/en.php
> >2. put a translation in include/locale/de.php
> >3. make up a macro name
> >4. substitute the string with the macro name, across all themes
> >5. have a look for the template file name in *.php and add
> >   a pslgetText statement to "$template->set_var"
> 
> That's 100% right. Although I believe that we are trying to move all 
> strings out of the .tpl files and more to the "locale" files. That way we 
> won't have to make too many corrections in different templates/$LANG 
> directories. However, that happens and we do have lots of strings still 
> flying around the .tpl files. More on this Joe?
> 

I'm still of the opinion that much of the text is easier to modify and
translate if it stays in the tpl.  That way it is in the context that it
will be displayed.

> >
> >Of course the string can occur more than once in multiple
> >templates. In some languages the translation can be different,
> >according to context, though.
> >
> >a) What directory should I diff against?
> >   phpslash-ft/public_html/templates/en
> 
> phpslash-ft is the old module which makes the current stable release. It's 
> being slowly face out -- pretty much the migration is done I would say. We 
> still work on -dev and "backport" things to phpslash-ft when necessary, but 
> -dev is so ahead of the game that it's a matter of time before we move on 
> to -dev to make releases. However, Joe would ultimately be the guy to ask 
> in this manner. To be safe, work on -dev always and diff against that.
> 

I guess it kind of depends on what you are working on.  Preferably we
would be working to get the -dev release ready.  But if you're only
running the -ft, patches against it are fine.

> >   or
> >   phpslash-dev/include/templates/en
> >

Whichever.  We'll work the patches in.

> >b) Is there a system behind template macro names?
> 
> ditto.
> 

don't think so.  If someone wants to help with an API doc and update the
coding guidelines, that would be great.

> >
> >c) How should I handle different word order or higher
> >   macro levels? For example
> >
> >   from the {DEPT} dept.
> >
> >   is translated as
> >
> >   Aus der Abteilung {DEPT}
> 
> Usually this has to be done in the order that's more natural to the given 
> language. For as long as that makes perfect sense to you who speak natively 
> that language, go ahead and submit it like you think is better. Usually I 
> give grammar explanations on my locale translations (as comments) in case 
> somebody looks at a string and dislike the translation; however, I welcome 
> corrections if they are necessary.
> 

Definitely you should be able to output text with grammar that makes sense
in that language.  If there is some difficulty in doing this, please point
it out.  You may decide that a language specific template set is best.

thanks,

Joe

> ----)(-----
> Luis Mondesi
> System Administrator
> LatinoMixed.com
> 
> le...@ho...
> 
> "...The Mac does this so smoothly, it feels like an extension of your 
> mind." - Paula Speer, MacWorld Magazine 2003-04
> 
> Public signature: http://www.latinomixed.com/lems1/public-a.asc