Regarding $wordBoundary in Katakana-Latin BGN Transformation

[Mark Davis ☕️ via CLDR-Users]

If that is now handled by ICU (eg there wouldn't be a functional
difference) this sounds great to me. (See my remarks on other email).

Mark


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

> Hi Cameron,
>
> I've just joined the CLDR-Users list and so am not able to reply directly
> to your September 20th email on this topic. The $wordBoundary variable was
> introduced in the BGN transformation when they were composed initially in
> 2006 as a work-around to a bug at the time (#2034 in the old bug tracking
> system).
>
> I'm sure it is no longer needed and the variable can be replaced with a
> standard word boundary marker. Hopefully it is otherwise harmless.
>
> In the Katakana-Latin case, the variable should simply be ignored by ICU
> and have no impact. The fact that it is unused may be the result of a file
> copy from another BGN file when the Katakana-Latin file was created and the
> variable was not removed when it should have been. Or perhaps it was
> referenced at one time and some later edit removed it.
>
> regards,
>
> -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/3e8ae0bf/attachment.html>