Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Address feedback on character.jsp from the public mailing list #1153

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

Merged
merged 7 commits into from
May 19, 2025

Conversation

eggrobin
Copy link
Member

@eggrobin eggrobin commented May 16, 2025

See https://corp.unicode.org/pipermail/unicode/2025-May/011446.html from @NeatNit and my reply https://corp.unicode.org/pipermail/unicode/2025-May/011447.html.

  • Drop the links to the blank properties.jsp (blanked in Bring back the JSPs #1018).
  • Show links to the individual character property pages for string-valued properties, e.g., for U+FDFA, image or for U+00DF, image
  • Link to the null query from null values.

Also fix various bits of bidic.jsp being stuck at Unicode 14 or Unicode 15.1.

@eggrobin eggrobin requested a review from markusicu May 16, 2025 18:57
@markusicu
Copy link
Member

CI check failures...

Copy link
Member

@markusicu markusicu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as usual, i am not trying to understand every aspect...

@eggrobin
Copy link
Member Author

CI check failures...

Ah, we are using an older JDK than the one I have on my machine…

markusicu
markusicu previously approved these changes May 17, 2025
@NeatNit
Copy link

NeatNit commented May 19, 2025

Thank you so much for addressing my feedback.

Will you add mirroring to bidi-c in this PR as well, or in a separate one?

My guess is it'd be something like this:

[NeatNit posts code, redacted]

Edit: although you might want to add some indication that the character has been mirrored. Terrible mock-up to get the idea across:

image

But this would require looking up which code points are Bidi_Mirrored, which would increase code complexity. I'll let you make the appropriate considerations.

@eggrobin
Copy link
Member Author

Will you add mirroring to bidi-c in this PR as well

I will deal with that separately, when I can find time.

Please don’t post code in issue comments, we can’t look at it anyway because you haven’t signed the CLA.

And the point of the bidi-c demo is not to be a layout engine (this is most obvious in that it shows unshaped Arabic and does nothing about rule L3), nor to illustrate which characters the font happens to support mirroring for, but to be a versioned demo of the algorithm as specified, so of course it needs to look up the Bidi_Mirrored for the correct version of Unicode and flag those characters to which rule L4 applies.

It is not clear that it would be a good idea to actually cause the characters to mirror (or rather to maybe mirror if the font supports it) by setting the dir attribute; the display really shows the characters in isolation, not the glyphs they would have (this is striking in Arabic where it is unshaped), so changing the glyphs can make it trickier to figure out who is who; in addition, for the characters that do not have a Bidi_Mirroring_Glyph, actual support for the RTL glyph is usually limited to specialized fonts, so the display would be unreliable.

@eggrobin eggrobin requested a review from markusicu May 19, 2025 16:10
@eggrobin eggrobin merged commit c40ca79 into unicode-org:main May 19, 2025
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants