locales

CSL Development
1

Question:

Should we not have a convention that all locale terms are capitalized?

We at least need some rules to go by.

Bruce

2

I’d suggest that lowercase by default makes more sense, but once we have an
attribute to control capitalization on terms, this is really just a cosmetic
issue.

3

I’d suggest that lowercase by default makes more sense, but once we
have an
attribute to control capitalization on terms, this is really just a
cosmetic
issue.

Where I foresee a potential problem is terms with more than two words.
We have the text-transform option to lowercase or capitalize, but not
to do title casing.

Also, that attribute is already allowed on terms, isn’t it?

4

I’d suggest that lowercase by default makes more sense, but once we
have an
attribute to control capitalization on terms, this is really just a
cosmetic
issue.

Where I foresee a potential problem is terms with more than two words.
We have the text-transform option to lowercase or capitalize, but not
to do title casing.

Also, that attribute is already allowed on terms, isn’t it?

Oops. I think so.

Or should we have separate files?

I was just thinking about this too.

I think they should be separate files, probably in a separate
directory; e.g.

locales/
terms-en.xml
terms-nl.xml
…

… or maybe just leave off the “terms” and just do “en.xml”

Thoughts?

I think I prefer the single-file approach. In my situation, it’d be even
better if I could use Mozilla’s locale-handling features (just drop the
appropriate terms.xml file in chrome/chromeFiles/locale/en-US/). Perhaps we
should just provide the term files and an Atom feed, and then leave the
specifics up to implementers?

Simon

5

That’d be fine. Any other opinions?

Best case scenario is we end up with, say, 50 locales in a few years,
each with 50 terms.

But maybe it’s best not to worry about that now and cross that bridge
if and when we come to it (because someone complains the locale file is
too big!).

Bruce