http://bugzilla.suse.com/show_bug.cgi?id=1052205 http://bugzilla.suse.com/show_bug.cgi?id=1052205#c1 Ladislav Slezák changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com Flags| |needinfo?(lnussel@suse.com) --- Comment #1 from Ladislav Slezák --- How much urgent is it? I mean it's not trivial so we need to plan for that. And for planning we need the priority. ;-) Yes, the JSON parser is part of the Ruby stdlib. However, I'm not sure if it is the best format to use... The disadvantage of JSON is that you cannot put comments there. And some comments are really important, like this one https://github.com/yast/yast-country/blob/master/console/src/data/consolefon... For that reason the YAML format could be better. Another problem is that some files use _() translations, like https://github.com/yast/yast-country/blob/master/language/src/data/languages.... And that would be hard to encode in JSON. (I'm not sure about YAML.) We already use translatable strings in XML files (control.xml), so also the XML format is possible. So the question is which one to use? JSON/YAML/XML? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1052205 http://bugzilla.suse.com/show_bug.cgi?id=1052205#c3 --- Comment #3 from Fabian Vogt --- IMO JSON is still the best option here, followed by XML. If JSON does not work for the lack of comments or the ability to call gettext from it, that is IMO not data, it is code. I'd suggest to move the calls to gettext to the actual code instead. If the lack of comments is an issue, there could be a comment hash entry for the entries that need it. It would be possible to work with XML as well, in theory that could be converted to JSON at buildtime for JeOS if really necessary... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1052205 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|please provide |package getcountrydata.rb |yast2-country data as json |for JeOS -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1052205 http://bugzilla.suse.com/show_bug.cgi?id=1052205#c6 --- Comment #6 from Ladislav Slezák --- (In reply to Ludwig Nussel from comment #4)

I didn't know about https://build.opensuse.org/package/view_file/openSUSE:Factory/kiwi-config- openSUSE/getcountrydata.rb

Oh, so no need to change anything in YaST?

So we just need to package that in a way reusable by Lives and JeOS. Will to Alex to to take that for future JeOS so yast can keep those shiny ycp maps.

BTW in the long term we want to get rid of the YCP format anyway. I already converted some YaST data files to YAML. The other files are blocked by translations, we haven't decided how to solve that yet. And because these are just static data files changed rarely it has a low priority for us... -- You are receiving this mail because: You are on the CC list for the bug.