The solution proposed by Martin Hosken seems to make quite a bit of sense to me. I only see two problems: - This would need a change to the RFC 4646 ABNF. This is serious. - Everything related to lanuguage tags is case-insensitive. The proposal below contains some case rules; these should (and can easily) be dropped. Regards, Martin. At 15:14 06/09/15, Martin Hosken wrote: >I would like to offer a possible solution for people to consider/laugh >at/whatever. > >I suggest that we introduce the concept of a script variant that >modifies a script subtag, that is valid for all languages and is only >scoped by the script it occurs following. The subtag shall be 4 >characters long and start with an initial capital letter just like an >existing script subtag. Given the space within ISO 15924 I'm sure we can >come to some agreement over carving out a codespace for such variants. >Failing that we could make the variant start and finish with a capital >letter or use any capitalisation trick we feel like using to mark this >thing. Since it is exactly 4 chars long it looks like a script tag to >existing mechanisms (although if they are hyper strict they will get fed >up) and would occur before the region subtag and after the script tag. >They would be clearly identifiable since they are neither the right size >for a region subtag or a variant subtag. > >The effect would be to add a mechanism of script variation that would >take priority over regions, be clearly identifiable and would resolve >many of the frustrations over ISO 15924. > >I hasten to add that I am *not* suggesting this as a solution to the >transcription extensions issue, which I agree should be handled via an >extension. I *am* suggesting it as a solution to the scripts question >where a particular script variant may occur across many languages and is >identifiably different in some key respect (here unspecified) to the >script it is varying from. > >Thank you for your consideration. > >Yours, >Martin Hosken > > >_______________________________________________ >Ltru mailing list >Ltru at ietf.org >https://www1.ietf.org/mailman/listinfo/ltru #-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University #-#-# http://www.sw.it.aoyama.ac.jp mailto:duerst at it.aoyama.ac.jp _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.