Re: TTML2: encoding

Well, one implementation supports both UTF-8 and UTF-16, namely TTV; it
also supports UTF-32. At present, we don't mandate a particular concrete
encoding of TTML1 or TTML2, so I think it is best left as is. It would be
strange to disallow an encoding that is sanctioned by XML but not required
be supported by TTML.


On Fri, Sep 5, 2014 at 9:29 AM, Nigel Megitt <nigel.megitt@bbc.co.uk> wrote:

>  The argument to change comes from implementations, where there seems to
> be a strong desire to settle on a single encoding. Simply because XML
> processors in general must be able to read entities in UTF-16 doesn't mean
> that TTML2 documents must be conformant if they're UTF-16.
>
>  In other words, we do at least have an option to be more restrictive,
> and the industry seems to be heading in that direction.
>
>
>  ------------------------------
> *From:* Glenn Adams [glenn@skynav.com]
> *Sent:* 05 September 2014 17:11
> *To:* Nigel Megitt
> *Cc:* TTWG
> *Subject:* Re: TTML2: encoding
>
>   I see no reason to change. We recommend (SHOULD USE) utf-8. XML itself
> also states "All XML processors must be able to read entities in both the
> UTF-8 and UTF-16 encodings. " [1], which text applies also to TTML as we
> normatively include it.
>
>  [1] http://www.w3.org/TR/REC-xml/#charencoding
>
>
> On Fri, Sep 5, 2014 at 2:25 AM, Nigel Megitt <nigel.megitt@bbc.co.uk>
> wrote:
>
>>  In the context of http://www.w3.org/TR/encoding/ (for which transition
>> to CR has just been requested) should we deprecate any other encoding than
>> UTF-8 for TTML2?
>>
>>   *--*
>>
>>
>>  *Nigel Megitt*
>>
>> Lead Technologist, BBC Technology, Distribution & Archives
>>
>> Telephone: +44 (0)208 0082360
>>
>> Telephone (Lync): +44 (0)3030807996
>>
>> Lync internal: 0807996
>>
>> BC4 A3 Broadcast Centre, Media Village, 201 Wood Lane, London W12 7TP
>>
>>
>>
>