Add a New Comment (Rich Markup)
I don't understand two things: 1) Why would anyone convert PO -> MO -> JSON in two steps, rather than PO -> JSON directly in one step? This two-step conversion creates intermediate .mo files that have to be removed. 2) How would this fit into the big picture of localization support in JavaScript? I've started a mail thread about this at http://lists.gnu.org/archive/html/bug-gettext/2016-12/msg00039.html
Dear gettext hackers, I found myself in the position where I need to convert .mo files to the JSON format used by JED.js. AFAIK the path to achieve this is: 1) Create write-json.{c,h} 2) Create mo2json based on msgunfmt Is there something I've forgotten here?
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Follow 2 latest changes.
Copyright © 2023 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.11