Supplemental data - characters.xml

[Mark Davis ☕️]

I think the main issue is that we have not really maintained and extended
that file, and without people committed to working on it, it just becomes
more and more stale. We don't know of a big user of the data, either.

So I think the appropriate action to take, unless some people are willing
to step up to the plate, is to deprecate that file in some way. Some
options are:

   - remove it
   - replace the contents of the file by a pointer to the last CLDR version
   where it occurs
   - keep it, but document in the file and outside that it is stale data

In any case, we would need to document the status, and also remove the
chart:
http://www.unicode.org/cldr/charts/25/supplemental/character_fallback_substitutions.html


Mark <https://google.com/+MarkDavis>

 *— Il meglio è l’inimico del bene —*


On Thu, Jun 12, 2014 at 9:55 AM, Markus Scherer <markus.icu at gmail.com>
wrote:

> On Wed, Jun 11, 2014 at 3:44 PM, John Emmons <emmo at us.ibm.com> wrote:
>
>>  The CLDR TC is considering retiring the "characters.xml" file from our
>> distribution.  The file is intended to provide a set of fallback characters
>> that can be used as reasonable alternatives for a given character if the
>> character does not exist in a particular font.
>>
> The data could be at least as useful for conversion from Unicode to other
> charsets, except we don't do that so much any more, relatively speaking.
>
>> See http://unicode.org/cldr/trac/ticket/7123.
>>
> I added a link to the data file there.
>
> markus
>
> _______________________________________________
> CLDR-Users mailing list
> CLDR-Users at unicode.org
> http://unicode.org/mailman/listinfo/cldr-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20140612/b1a204d4/attachment.html>