Hi,
Similar question has been discussed before:
http://www.winehq.org/pipermail/wine-devel/2006-November/052140.html http://www.winehq.org/pipermail/wine-devel/2006-November/052142.html http://www.winehq.org/pipermail/wine-devel/2006-November/052143.html
You only need to add an English resource; the other language files are made
by
whoever translates the English strings into their language.
The better way is to add string untranslated into every resource, otherwise it will not be loaded.
More info at http://www.winehq.org/pipermail/wine-devel/2006-November/052135.html
-- Kirill
On Wed, Mar 28, 2007 at 11:59:45AM +0400, Kirill K. Smirnov wrote:
Hi,
Similar question has been discussed before:
http://www.winehq.org/pipermail/wine-devel/2006-November/052140.html http://www.winehq.org/pipermail/wine-devel/2006-November/052142.html http://www.winehq.org/pipermail/wine-devel/2006-November/052143.html
You only need to add an English resource; the other language files are made
by
whoever translates the English strings into their language.
The better way is to add string untranslated into every resource, otherwise it will not be loaded.
More info at http://www.winehq.org/pipermail/wine-devel/2006-November/052135.html -- Kirill
Hi Kirill, what about updating the Developer Guide: http://winehq.org/site/docs/winedev-guide/adding-languages
It will save precious time during several review rounds. Regards Vit
"Kirill K. Smirnov" lich@math.spbu.ru writes:
You only need to add an English resource; the other language files are made
by
whoever translates the English strings into their language.
The better way is to add string untranslated into every resource, otherwise it will not be loaded.
That's only if you are adding a string to an existing table. If you are creating a new resource you only need to create the English one.
-
Alexandre Julliard -
Kirill K. Smirnov -
Vit Hrachovy