New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
\c[BELL] returns the U+0007 control code not U+1F514 BELL #5998
Comments
From @samcvFudged test in S02-literals/char-by-name.t is "\c[BELL]", "🔔", '\c[BELL] returns 🔔, BELL symbol not the control |
From @samcvThis has been fixed on MoarVM as of MoarVM/MoarVM@8161864 BELL now resolves to 🔔 U+1F514 on MoarVM, but this is still broken on the JVM |
From @toolforger
What causes this kind of difference? |
The RT System itself - Status changed from 'new' to 'open' |
From @samcvOn Saturday, 14 January 2017 02.06.57 PST you wrote:
U+0007's Unicode 1 name was BELL, and with version 2 the name was removed. Unicode 1 names are essentially totally deprecated and shouldn't be used for naming characters. For this reason it has been decided we should only guarantee standard Unicode names and Name Alias's. Concerning BELL, in Unicode 1, U+0007 control code was named bell. Since Unicode 2, the control code's names were removed and they were given stable Alias's. As proof that Unicode 1 names shouldn't be relied on, the U+1F514 bell symbol is called BELL. Regarding the JVM, it seems to give us back the canonical Unicode names if they exist, and otherwise give us the Unicode 1 names. There may be some way to get the Name Alias's, but I do not know. I will have to manually go in and add U+1F514 as BELL, and add U+0007 as BEL and ALERT. I manually added a few other Alias Names to JVM recently to fix a few roast tests. See here for the commit that added some Alias Names to JVM: Raku/nqp@0c249e7 Hopefully I have explained this well enough. |
From @toolforgerAm 14.01.2017 um 11:29 schrieb Samantha McVey:
I kinda expected this to be implemented in NQP and hence be identical I am seeing tangential points about this; where should I raise them? |
From @cokeOn Sat, Jan 14, 2017 at 6:40 AM, Joachim Durchholz <jo@durchholz.org> wrote:
Depends on the points. If you want to get the attention of the core developers for a The mailing lists (https://perl6.org/archive/lists/) work as a very To report a bug with rakudo, open a ticket via an email to rakudobug@perl.org -- |
From @samcvThis has now been fixed as of Raku/nqp@deb8cb03e Tests have been added for this and other non-BMP codepoints. Marking resolved. |
@samcv - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#130542 (status was 'resolved')
Searchable as RT130542$
The text was updated successfully, but these errors were encountered: