[Foundation-l] languages with INVENTED codes

[Gerard Meijssen]

Hoi,
First of all, the codes that we all agree on that they are wrong need to be
fixed. Then all the invented codes that are not known to either the RFC 4646
or better the ISO-630-3 need to be registered as such. When the people
supporting these invented codes are not able to argue their case that their
"language" is indeed a linguistic entity, I do not think we should support
them. Mind you, even constructed languages are supported here, so it is just
a matter of demonstrating that it is sufficiently unique.

When we publish our data, we indicate in the meta data what linguistic
entity this is. Given that the codes have to be standardised to be
recognised, invented codes are wrong to have. When the code is something
like fiu-x-vro, the x indicates that it is private designation and can be
safely ignored.
Thanks,
      GerardM

On Mon, Oct 20, 2008 at 3:01 AM, Mark Williamson <node.ue at gmail.com> wrote:

> But these are two very different cases. A code like fiu-vro is not
> squatting, it is a macrolanguage code plus an invented code. als is
> squatting, indeed, but that is a unique situation. I don't see what's
> wrong with having xxx-xxx style codes.
>
> Mark
>
> On 18/10/2008, Gerard Meijssen <gerard.meijssen at gmail.com> wrote:
> > Hoi,
> > Really problematic are codes like the one used for Alsation; the "als"
> code.
> > This code is according to the standard to be used by Tosk Albanian while
> we
> > use it for "Alsatian". This is not acceptable for what we currently do,
> > making it compulsory for future new projects is not acceptable either.
> > Projects like these should be renamed as they are squatting ligitimate
> codes
> > for ligitimate languages.
> > Thanks,
> >       GerardM
> >
> > On Sun, Oct 19, 2008 at 12:48 AM, Crazy Lover <
> > always_yours.forever at yahoo.com> wrote:
> >
> >> I add (In language Proposal policy - communiy draft) a clause is for
> >> languages with
> >> active wikis, but which Code has been invented: voro (fiu-vro),
> tarantino
> >> (roa-tara), Cantonese (zh-yue), min nan (zh-min-nan) , etc.
> >>
> >> For new proposal those will continue using the same
> >> invented code that are using.
> >>
> >> The problem: Imagine that they will
> >> use different codes [when get a ISO code or if they have: Min nan (nan),
> >> Cantonese (yue)] for new projects, the technical chaos that would
> >> occur.
> >>
> >> Please check it out:
> >>
> >>
> >>
> http://meta.wikimedia.org/wiki/Meta:Language_proposal_policy/Community_draft
> >>
> >> C.m.l.
> >>
> >>
> >> __________________________________________________
> >> Do You Yahoo!?
> >> Tired of spam?  Yahoo! Mail has the best spam protection around
> >> http://mail.yahoo.com
> >> _______________________________________________
> >> foundation-l mailing list
> >> foundation-l at lists.wikimedia.org
> >> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
> >>
> > _______________________________________________
> > foundation-l mailing list
> > foundation-l at lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
> >
>
> _______________________________________________
> foundation-l mailing list
> foundation-l at lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
>