> > 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
- Re: the ultimate solution to the i18n problem... tomr
- Re: the ultimate solution to the i18n problem... Marc Lehmann
- Re: the ultimate solution to the i18n problem... Ian McKellar
- Re: the ultimate solution to the i18n proble... Marc Lehmann
- Re: the ultimate solution to the i18n problem... Eduardo Perez
- Re: the ultimate solution to the i18n problem... Sven Neumann
- Re: the ultimate solution to the i18n problem... Jon A. Cruz
- Re: the ultimate solution to the i18n proble... Marc Lehmann
- Re: the ultimate solution to the i18n pr... David Monniaux
- Re: the ultimate solution to the i1... Marc Lehmann
- Re: the ultimate solution to the i18n proble... Sven Neumann
- Re: the ultimate solution to the i18n pr... Jon A. Cruz
- Re: the ultimate solution to the i18n problem... Tuomas Kuosmanen
