The first decision we made was that we don\u2019t want people to have to buy special or complicated tools in order to produce a localized version of WeSay. We want them to be able to just edit a text file, or use a simple free tool<\/a>. Of course, po\/gettext files fit this bill.<\/p>\n The next decision was how to actually use that file\u2026 I tried getting the relevant gnu libraries for .net, but I just kept running into problems. Eric convinced me that I should just to write a little parser for it myself, and even though that felt so terribly wrong, I did have the parser going in a fraction of the time I had spent trying to locate\/use standard libraries.<\/p>\n Anyhow, Eric provided some Portuguese for a few labels, and we produced the following: We get this simply by adding \/ui:br to the shortcut that launches WeSay (\u2018br\u2019 is for Brazil). This causes WeSay to go looking for a file named br.po, first in the user\u2019s project directory, and then in the WeSay common directory. Users will be able to submit po files that they have localized and are willing to include in the next distribution of WeSay. But no one needs to wait for a new distribution\u2026 they can simply make their own po file or share the file with colleagues in the area.<\/p>\n
\n![\"Palavras](\"\/wp-content\/uploads\/sites\/35\/2017\/04\/20060920_14095010692.png\" "\\"Palavras")
\n<\/a><\/p>\n