At 2007.04.12-15:06(-0700), Mark Davis wrote:
Actually, we do have the ability
to give fairly detailed messages based on regular expression matches on
the XML path in a "zoomed" view, and soon we will have the
ability to require people to go to the zoomed view before editing, and
thus see those messages. So we can add specific clarifications on the use
of "und" or other special cases.
On 4/12/07, Asmus Freytag
- On 4/12/2007 2:25 PM, Kent Karlsson wrote:
- > FWIW, in CLDR 1.4 some of the translations for "und"
has the word "language"
- > (translated of course) in them, in accordance with John Cowan's
<language type="und">Sproget kan ikke
<language type="und">Sprache nicht
I thought "obestamt" was "unstated".
- The sample translations show that there's general difficulty in
- on the concept. The German translation says "no language (has
- determined", while the Danish translation says that "no
- be determined". In my reading the Swedish allows both
- perhaps implies more strongly than the other two that assigning
- language to the contents would be meaningful. (The Italian
- seems to most closely agree with the Swedish one to the extent of
- command of Italian)
- > (I would be to blame for the last one, but apparently I'm not
the only one to (maybe)
- > be misguided). Perhaps those ones should be retranslated not to
refer to language,
- > **if** "und" may apply also to "maybe not in any
- The problem is that the scheme does not explicitly accounts for all
- types of edge conditions that you can get into when analyzing text
- language up front. Instead, labels are added here and there to
- some of these as they become urgent enough to require attention. As
- result, all the translators have to go by is the shorthand
- description for the label. And that's not written with enough
- to overcome the limitation of not having thought through all
- possible cases.