Notice: A non well formed numeric value encountered in /sites/rockbox.org/flyspray/includes/class.flyspray.php on line 96 Notice: A non well formed numeric value encountered in /sites/rockbox.org/flyspray/includes/class.flyspray.php on line 96 Notice: A non well formed numeric value encountered in /sites/rockbox.org/flyspray/includes/class.flyspray.php on line 96 Deprecated: Function create_function() is deprecated in /sites/rockbox.org/flyspray/includes/class.flyspray.php on line 104 Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /sites/rockbox.org/flyspray/adodb/adodb.inc.php on line 845 Deprecated: Function create_function() is deprecated in /sites/rockbox.org/flyspray/includes/class.user.php on line 111 FS#8550 : new lang format proposal

Rockbox

Tasklist

FS#8550 - new lang format proposal

Attached to Project: Rockbox
Opened by harry tu (bookshare) - Sunday, 03 February 2008, 18:06 GMT
Last edited by Jonas Häggqvist (rasher) - Sunday, 03 February 2008, 23:40 GMT
Task Type Bugs
Category Applications
Status Closed
Assigned To No-one
Operating System All players
Severity Low
Priority Normal
Reported Version Daily build (which?)
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

My format proposal combines langv1 with langv2 and you get this format for one string.
startphrase
id: (string id)
desc: (string description)
user:
source:
target 1: (target 1 string)
target 2: (target 2 string)
dest:
target 1: (target 1 string)
target 2: (target 2 stringz)
voice:
target 1: (target 1 string)
target 2: (target 2 string)
endphrase
I have examined both langv1 and langv2 files and noticed that langv1 is easier to edit. I still wanted to maintain the ability to have 2 strings for each target, so I proposed this format.
This task depends upon

Closed by  Jonas Häggqvist (rasher)
Sunday, 03 February 2008, 23:40 GMT
Reason for closing:  Rejected
Additional comments about closing:  If anything, your version makes it harder, since it makes the strings stand less out than in langv2. If anything, we want to move towards a full XML-based langformat ( FS#8233  ) to facilitate easier scripting and programming of language-related tools.
Comment by Jonas Häggqvist (rasher) - Sunday, 03 February 2008, 18:22 GMT
In which way is this better than langv2? As far as I can tell, you just removed some spacing and the brackets.
Comment by harry tu (bookshare) - Sunday, 03 February 2008, 23:13 GMT
I don't know about you, but I would find this easier to edit for someone that knows nothing about tags/html/xml.

Loading...