From: Daniel Stenberg <daniel_at_haxx.se>
Date: Mon, 16 Sep 2002 11:02:23 +0200 (MET DST)

Ok, we've had some time to discuss and think things over, and now I really
only want really well-thought objections with motivations why this language
file format is bad:

A single file for each language. Plain text.

Example:

---- snip ----
id: LANG_LOADING
desc: the text popping up when a playlist is loading
eng: "Loading..."
new: "Laddar in..."
---- snip ----

o id would be the ID to use in the source when this string is wanted. The
  code should use str(id) to get the particular string.
o desc would be a volountary/optional description of the phrase
o eng is the english original. We want the english phrase in here to easier
  track when the english original changes and thus check which translated
  files that might want to recheck their translations for this particular id.
o new is the translated phrase

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

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

I'll soon bring on my initial scripts and language files that follow this
format.

-- 
Daniel "Bagder" Stenberg -- http://rockbox.haxx.se/

Received on 2002-09-16