Addition request: alsatian

[Mark Davis]

> If gsw-alsatian is
> also used on the other side of the Rhine, then it is not
> clear to use gsw-FR for "alsatian as spoken in DE".

I haven't seen yet a convincing case for a separate "alsatian". We need to
remember that variant tags are not free:

   1. not everyone supports them (for example, Google doesn't)
   2. if we present two ways of doing things, inevitably people will get
   mixed up.

For example, if we introduced "en-american" for American English, we would
just cause confusion with "en-US" being used for that purpose. The broad
variants of Alemanic that can reasonably be broadly distinguished by the
tags gsw-FR, gsw-DE, and gsw-CH should just use those tags as is.

Mark

On Jan 7, 2008 2:20 PM, Frank Ellermann <nobody at xyzzy.claranet.de> wrote:

> Stephane Bortzmeyer wrote:
>
> >>> I would say that "alsatian" and "gsw-FR" are almost
> >>> the same thing but not completely.
>
> >> Which means what?
>
> > That I think that using "gsw-FR" to mean "alsatian" is
> > acceptable, if not ideal.
>
> A case where it would be not ideal:  If gsw-alsatian is
> also used on the other side of the Rhine, then it is not
> clear to use gsw-FR for "alsatian as spoken in DE". (*1)
>
> Opposite case:  gsw-CH is a broad tag, taggers could try
> to use gsw-FR for "gsw-CH as used in regions of CH where
> French is the predominant language".
>
> The variant alsatian is clearer than gsw-FR workarounds.
>
>  Frank
> --
> *1: Actually I don't *think* that's the case, but to be
>    sure I'd had to ask folks living in Kehl (the German
>    town next to Strasbourg)
>
> _______________________________________________
> Ietf-languages mailing list
> Ietf-languages at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/ietf-languages
>



-- 
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/ietf-languages/attachments/20080107/a530502f/attachment.html