-
Notifications
You must be signed in to change notification settings - Fork 384
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
CLDR-17844 Modify the date report #3920
CLDR-17844 Modify the date report #3920
Conversation
Once the charts resync, the following should show up: |
I changed to rtl vs auto, which resolved a bunch of problems. Also added for comparison: https://unicode.org/cldr/charts/46/verify/dates/fa.html Will update with screenshots. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
595dde3
Final cleanup for this PR. Am getting now no "alerts" indicating letter or number collisions. Also regenerated the charts. |
Just updated the description, so would appreciate review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great except minor nitpicking comments
} | ||
|
||
/** | ||
* Return a list of the , where each span is a sequence of: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
word missing before the comma? Actually this whole comment looks unattached to anything, obsoleted by the following comment Gets the fields
* @return a set of fields, in the same order as found in the text but duplicates removed (ike | ||
* LinkedHashSeet). | ||
*/ | ||
public static Set<String> getFields(String reordred, Set<String> result) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reordred
should be reordered
and the comment above should have @param reordered
and @param result
return ""; | ||
} | ||
// there can still be differences within a field of OTHERS, that we ignore. | ||
// EG ⚠️ 20,28,2B; 2B,28,20 " (+" vs " (+" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2B,28,20 should be " ( "?
.collect(Collectors.joining(LRM + ", " + LRM, LRM, LRM)); | ||
} | ||
|
||
public static String alphagram(String string) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
alphagram seems unused?
UnicodeSet escapesToShow, String tableOptions, String cellOptions) { | ||
if (!escapesToShow.strings().isEmpty()) { | ||
throw new IllegalArgumentException("No strings allowed in the unicode set."); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe also confirm tableOptions and cellOptions start with spaces if not empty -- either throw IllegalArgumentException or insert the spaces if missing
final String id = cpe.name(); | ||
final String shortName = cpe.getShortName(); | ||
final String description = cpe.getDescription(); | ||
addREsult(result, tdPlus, id, shortName, description); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is capital E in addREsult a typo?
: "However, two examples are provided if the locale is right-to-left, like Arabic or Hebrew, " | ||
+ "<i>and</i> the paragraph direction can cause a different display. " | ||
+ "The first has a <b>RTL</b> paragraph direction, " | ||
+ "while the second has a <b>auto</b> paragraph direction (LTR unless the first 'strong' character is RTL) " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a --> an (before auto)
+ spanEnd | ||
+ " shows those characters with short IDs ❰…❱: see the <b>Key</b> below the table. " | ||
+ "So that the ordering of the characters in memory is clear, they are presented left-to-right one at a time. " | ||
+ "so that the placement is clear. " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"so that the placement is clear. " looks like leftover variant, delete?
Thanks! |
CLDR-17844
Modify the date report to help figure out what is happening with the date formats, and present the user with more and clearer information.
Added BidiUtils with utilities for display of examples/reports
Small changes to CodePointEscaper, plus support for printing a table of escape IDs in a report.
DateTypeFormats
This PR completes the ticket.
ALLOW_MANY_COMMITS=true