[OpenType] RE: [mpeg-OTspec] Re: Languages tags (Buruchaski & North Slavey)

Denis Jacquerye moyogo at gmail.com
Tue May 24 21:21:46 CEST 2016

OK. I see now.
John and Peter’s suggestion is fine.


On Tue, 24 May 2016 at 19:56 Peter Constable <petercon at microsoft.com> wrote:

> I agree that OT language system tags and ISO 639 IDs represent different
> information. However, the OT language system tags were badly
> under-documented. The mappings were provided since, otherwise, there would
> be no indication whatsoever what the language system tags are intended to
> mean.
> As for actual mapping usage, I can't think of any usage scenario in which
> one would map from the language system tag to an ISO 639 language ID. But
> mapping in the other direction certainly can happen since content is often
> tagged for language using BCP 47 tags. Hence this mapping information could
> get picked up in implementations to use as a default mapping from a
> language tag to a language system tag — if the font uses that tag (else
> default).
> With that in mind, SLA could be left as a higher-level category, and the
> language tag scs could be left as a mapping. But if we really want it to be
> a higher-level category, then the mapping should list both scs and xsl.
> Then we'd be left with this:
> Lang system tag: SLA
> Description: Slavey
> ISO 639-3 mappings: scs, xsl
> Lang system tag: SSL
> Description: South Slavey
> ISO 639-3 mappings: xsl
> That suggests a gap that could be filled, as John suggests:
> Lang system tag: SCS
> Description: North Slavey
> ISO 639-3 mappings: scs
> That would work and wouldn't conflict with anything. I wonder if it's
> overkill: is anybody going to implement fonts that have different glyphs or
> layout behaviour for SLA versus SSL versus SCS? But I won't object if
> that's how people want to proceed.
> Peter
> -----Original Message-----
> From: John Hudson [mailto:john at tiro.ca]
> Sent: Tuesday, May 24, 2016 9:58 AM
> To: Denis Jacquerye <moyogo at gmail.com>; Levantovsky, Vladimir <
> Vladimir.Levantovsky at monotype.com>; OTspec (mpeg-OTspec at yahoogroups.com) <
> mpeg-OTspec at yahoogroups.com>; Peter Constable <petercon at microsoft.com>
> Subject: Re: [OpenType] RE: [mpeg-OTspec] Re: Languages tags (Buruchaski &
> North Slavey)
> On 24/05/16 09:30, Denis Jacquerye wrote:
> > The OT language system tag SLA already maps to ISO 639 [scs] (the ISO
> > 639 code for North Slavey).
> > Slavey; SLA; scs
> Mapping of OTL language system tags to ISO 639 codes was not part of the
> original intent of the former, and I'm still not convinced it is a good
> idea, since they represent different types of data that only sometimes
> align. I certainly don't think it makes sense to use ISO 639 codes — which
> I think can only constitute an annotation to OTL language system tags — to
> determine the intent of the latter.
> That said, in this case I don't imagine there are many fonts that would be
> affected by redefining SLA as North Slavey.
> JH
> --
> John Hudson
> Tiro Typeworks Ltd    www.tiro.com
> Salish Sea, BC        tiro at tiro.com
> Getting Spiekermann to not like Helvetica is like training a cat to stay
> out of water. But I'm impressed that people know who to ask when they want
> to ask someone to not like Helvetica. That's progress. -- David Berlow
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20160524/c91157bc/attachment.html>

More information about the mpeg-otspec mailing list