[Bf-committers] procedural translation proposal

[John K. Walton]

clarification:
1) are the changes proposed to address the performance problems with this
   feature on some platforms?
2) or there was some functional inadequacy that the previous method
   lacked (e.g. translation was gramatical gibberish).

On Sun, 8 Jun 2003, Ton Roosendaal wrote:

> Hi,
> 
> -----> Shortlist of c files with translatable content:
> 
> (from blender/source/blender/src/)
> 
> buttons.c
> edit**.c  (=wildcard)
> filesel.c
> headerbuttons.c
> space.c
> toets.c
> toolbox.c
> 
> 
> ------> only include strings called with functions:
> 
> uiDefBut*(
> okee(
> error(
> pupmenu(
> add_numbut(
> do_clever_numbuts
> button(
> 
> I prefer a fixed shortlist of function calls that get translated, that  
> way we exactly know what happens... even when it doesn't cover all  
> interface strings.
> For completeness, we then can add a code to force translation:
> /* +TRANS */
> or so. A line with this comments gets its string translated.
> 
> ------> then process the strings:
> 
> Don't know about this one... how gettext will work with strings in  
> pupmenus for example. So maybe:
> 
> - replace '|' with new-line
> - remove '%' and everything that's after '%' up to space or newline
> 
> -Ton-
> 
> 
> ------------------------------------------------------------------------ 
> --
> Ton Roosendaal  Blender Foundation ton@blender.org  
> http://www.blender.org
> 
> _______________________________________________
> Bf-committers mailing list
> Bf-committers@blender.org
> http://www.blender.org/mailman/listinfo/bf-committers
>