Hi Mesar,Yes. I can use Poedit. But, how to read the instructions to the translators and whether it is used in Braille or not, etc.?
Thanks, DINAKAR On 23/01/2012 12:19 PM, Mesar Hameed wrote:
Good Morning, I think with notepad++ you need to ensure the nvda.po file is saved as utf8 without bom each time it is saved/committed. Now that the poedit app module is included in main, maybe you can play with poedit and see if it has become easier to use? Poedit ensures that the po file is always saved in the correct format. Best wishes. On Thu 29/12/11,16:06, DINAKAR T.D. wrote:Dear Mesar, I am fine. Thank you for fixing the po file. I use both Notepad++ and Poedit. Notepad++ for translating and Poedit to compile the mo file so that I can test it. In future, I shall ensure that the file is not utf8-bom and only utf8. The option is in the "encoding" menu in Notepad++. Thanks again. DINAKAR On 28/12/2011, Mesar Hameed<mesar.hameed@xxxxxxxxx> wrote:Dear Dinakar, I hope this email finds you in good health. Today I committed the translation work to nvda bzr, and I noticed that there is a small issue with ta/nvda.po It has a utf8-bom at the start of the file, which prevents it from being correctly updated/merged by the automatic scripts, and would also not work for nvda. I have fixed it, but wanted to check with you to prevent it from causing an unintentional error. I assume you are not using poedit to translate the nvda.po file, (I think poedit would have complained)? Maybe you are using notepad++? If so, when you edit and save nvda.po in the future, can you make sure please that it has a utf8 encoding without a bom. I dont have windows here now, but i think the option is in the encoding submenu in the file menu. If you cant find it I'm sure one of the team will tell us where it is. Thank you for your good work. Mesar