Re: [nvda-translations] Small problem in nvda.po files
- From: James Teh <jamie@xxxxxxxxxxxx>
- To: Mesar Hameed <mesar.hameed@xxxxxxxxx>
- Date: Tue, 10 Jan 2012 21:10:40 +1000
On 10/01/2012 8:21 PM, Mesar Hameed wrote:
Any chance of running dos2unix over all .py files before you call
xgettext? This would have to be done in a temporary tree, of course.
If we went with the temporary tree, The following would have to be done.
* use python tools reindent to swap tabs for spaces (avoids the original
problem that caused this discussion)
* convert *.py to unix files.
Why? In your original message to bug-gettext, you noted that everything
works fine if you use Unix line endings. Qutoing from the message:
When indented using spaces, text is extracted correctly.
When using tabs, only "line 1\n" is extracted.
When the file is using unix line endings, all seems to be fine.
I assume you meant regardless of indentation. (This would seem to make
sense, since it works fine in Windows where the \r is stripped by the C
runtime.) Did I misunderstand something here? If correct, the only thing
you should have to do is dos2unix all .py files.
I would still vote for doing the extraction serverside.
Me too. I'll try to work on this in the next few days, though I can't
guarantee a quick fix unfortunately.
On that note, it'd be great if you could provide your opinion on this
question in ticket #1524:
•scons needs to be updated to use these tools.
◦Where do we tell the user to place them? We could say gettext in Program Files
or we could install them somewhere in the NVDA build tree.
Jamie
--
James Teh
Vice President, NV Access Inc
Email: jamie@xxxxxxxxxxxx
Web site: http://www.nvaccess.org/
Phone: +61 7 5667 8372
Other related posts:
