>comments should be fine - we only read the tags that we need, nothing else.
ok, good! to make that clear; my comments are valid xml-comments.
>we have not yet decided how to best handle the build string. it won't hurt leaving it in, ofcourse. ideally, we'd want it updated at build time, but noone has implemented this yet. does it need to be translated at all?
good question. depedns on what the string should say really. my current file has the value 'xbox media center 1.1.0', since it is supposed to be for v1.1.0. this is fine for point releases, 'cause the value contains only the name and version, wich is language neutral (at least at this point, i mean we don't want localized names for xbmc right?)
it is really only a problem in cvs builds where the word 'build' could be translated. i don't know for other languages, but 'build' is a fairly common term in norwegian software development as well. clearly this is a minor problem.
stating that the xbmc is a release, when in fact it is a cvs build is another case. probably it's not a problem, but the language files aren't updated as often as other parts of the project, so version info won't match. a solution to this could also be to add a task in the build script that parses all strings.xml to replace/remove the entry in question?
maybe a bit pointless, insignificant discussing on my part
but i just wanted to have some sort of resolution to this problem. rules are sometimes good in software development.
anyhow, i'll leave the entry in there for now.
sorry, 'bout my long posts.
x-halez