Re: the ultimate solution to the i18n problem...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 
> Almost, but not quite.
> 
> gettext was a  good compromise at the time, but leaves a lot to be desired.
> Especially when one source english term ( "its" for example ) might be
> translated differently depending on context. 

When working carefully with gettext, you can translate all appearances of the 
same word differently. Since the location of the string in the source code is
contained in the po files, it is easy (even without knowing the entire source)
to detect in what context/dialog the word is used.


Salut, Sven 




[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux