Rockbox mail archive

• Next message: Daniel Stenberg: "Re: .lang files"
• Previous message: Magnus Holmgren: "Re: cvs: firmware id3.c,1.41,1.42"
• In reply to: Daniel Stenberg: ".lang files"
• Next in thread: Daniel Stenberg: "Re: .lang files"
• Reply: Daniel Stenberg: "Re: .lang files"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

On Mon, 16 Sep 2002, Daniel Stenberg wrote:

> now I really only want really well-thought objections with motivations why
> this language file format is bad:

Uhu, I'm out of topic then - because I think it is pretty good. :-)

Extending your example I understand that this is what you want when you got
more items:

---- snip ----
id: LANG_LOADING
desc: the text popping up when a playlist is loading
eng: "Loading..."
new: "Laddar in..."
id: LANG_ANSWER_NO
desc: the no-answer in yes/no (not confusing with "none")
eng: "No"
new: "Nej"
---- snip ----

> The order of these keywords are important. They should only come in the order
> as stated above (to make writing scripts for this easier).

Nah, I'm against that. Writing a perl script is easy anyway. If you say the
order is important than you (almost) say that we will never extend the
format (easiest way to write a script is in your case to always read four
lines and skip the tag text).

> We might want some header to the language file, stating which charset this
> language is using.

Yep. New tag items for me.

Do we want comments too? # good to have or just messing up the script
writing?

 // Kjell

• Next message: Daniel Stenberg: "Re: .lang files"
• Previous message: Magnus Holmgren: "Re: cvs: firmware id3.c,1.41,1.42"
• In reply to: Daniel Stenberg: ".lang files"
• Next in thread: Daniel Stenberg: "Re: .lang files"
• Reply: Daniel Stenberg: "Re: .lang files"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]