Considering Cleanup of Some Transforms

[Mark Davis ☕️ via CLDR-Users]

Thanks, this sounds like a useful project to me.

For something like this, you should file a ticket first, and then you can
get the committee's take on the design before doing the work on it.

For each one of the planned changes in the ticket, please add a link to a
file that shows the issue, and what the change would look like in that
file, so that the committee can see exactly what you plan. I give one
simple one below.


   1. add <![CDATA[ ... ]]> child nodes to encompass all rules (impacts 214
   files)
   2. Set XML comments, <!-- ... --> to # comments (impacts 3 files)
   3. Fix a commented out <?xml ...?> header (one file)
   4. Update Copyright end date to all files (set to 2020 ?)

https://github.com/unicode-org/cldr/blob/master/common/transforms/Amharic-Latin-BGN.xml
-4 Copyright © 1991-2013 Unicode, Inc.
+4 Copyright © 1991-2020 Unicode, Inc.

   1. replace $wordBoundary variable with corresponding ICU marker (31
   files, having introduced this variable I feel some sense of responsibility
   for it)


Mark


On Sun, Oct 20, 2019 at 5:10 PM Daniel Yacob via CLDR-Users <
cldr-users at unicode.org> wrote:

> Greetings,
>
> Looking through the CLDR transforms recently, I noticed mixed conventions
> in the <tRule> nodes and thought that I could volunteer some time to make
> them more consistent.  What I have in mind is:
>
> * add <![CDATA[ ... ]]> child nodes to encompass all rules (impacts 214
> files)
> * Set XML comments, <!-- ... --> to # comments (impacts 3 files)
> * Fix a commented out <?xml ...?> header (one file)
> * Update Copyright end date to all files (set to 2020 ?)
> * replace $wordBoundary variable with corresponding ICU marker (31 files,
> having introduced this variable I feel some sense of responsibility for it)
>
> I would fork the repo and make a pull request to provide an update.
> Before undertaking this work though, I would like to have some assurance
> that a pull request with these updates would be accepted.  LMK if so and I
> will go forward with these revisions -or just some as advised.
>
> thanks!
>
> -Daniel
>
> _______________________________________________
> 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/20191020/4c233136/attachment-0001.html>