"Petr Morávek [Xificurk]" wrote:
While I can understand why you propose this, it makes 'decoding' the
>languages by tools a little more difficult,
Not really, it's a matter of simple regular expression.
>and 'hard codes' a format, which alternative uses may need to replace?
What? That was the point of my proposal, NO hard-coded format (hard
coded in the sense of specifying_one-true-format_ in the algorithm itself).
If you stick with my proposal:
- you can easily satisfy "on the ground rule" for the local default
value of tag generated from 'lang' template
- if you don't want/need the default local template, just ignore the
lang value, and generate your own value from key:lang values
- if you only want a list of locally used languages, but don't care
about the locally used format of multilingual signs, it's again a matter
of one simple regular expression (i.e. you can always go in the
direction format string=>list of langs, but you can never go in the
opposite direction)
Actually when you put it that way it does make sense ...
I was thinking more on displaying two or more names while rendering, but of
cause the 'on the ground' format is just as important. I'm just used to keeping
data and format separate ...
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
_______________________________________________
talk mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/talk
