-
-
Notifications
You must be signed in to change notification settings - Fork 767
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
ICU-22921 Add howto guide to try MF 2.0 final candidate draft impls #3334
Conversation
Page preview in personal fork GH Pages site: https://echeran.github.io/icu/userguide/format_parse/messages/try-mf2.html |
UParseError parseError; | ||
|
||
icu::Calendar* cal(Calendar::createInstance(errorCode)); | ||
cal->set(2025, Calendar::JANUARY, 28); |
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.
The text on line 112 says the message will say "January 13", but this sets the calendar to the 28th???
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.
Thanks, updated (created suggestion in my review)
@mihnita Note that the same bug is in the Java instructions. The calendar is set to |
|
||
--- | ||
|
||
# Hello `MessageFormat2` |
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.
Some style guides seem to prefer one single heading 1 in the whole document, as "the title of the page"
I don't feel strongly about that.
But in this case, looking at the rendered page that you shared, is this bringing anything extra?
What we have is basically:
Trying MF 2.0 Final Candidate
{TOC}
Hello MessageFormat2
Suggestion: just remove this heading
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.
Done.
# end | ||
``` | ||
|
||
1. This will output |
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.
I don't think this is a separate bullet.
Feels like a part of "Build your application and run it"
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.
Done.
|
||
```cmd | ||
git clone https://github.com/unicode-org/icu.git | ||
|
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.
nitpick: remove trailing spaces
cd icu\icu4c | ||
msbuild source/allinone/allinone.sln /p:Configuration=Release /p:Platform=x64 /p:SkipUWP=true | ||
cd ..\.. | ||
|
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.
nitpick: remove trailing spaces
UParseError parseError; | ||
|
||
icu::Calendar* cal(Calendar::createInstance(errorCode)); | ||
cal->set(2025, Calendar::JANUARY, 28); |
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.
Thanks, updated (created suggestion in my review)
Thank you for the catch! I've updated the real code, but missed updating the .md |
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.
It seems like:
- We want a TOC, so that people can just jump to the case they are interested in, instead of scanning.
- Instead of "create a minimal C++ file", can we put hello_mf2.cpp into the directory so people can just copy it? Then the instructions for all the C++ cases for that file are identical and simple.
- Put the scarier cases after the simpler ones
- Move "From Visual Studio with minimal work" first under "C++ Windows with Visual Studio"
Is already there.
Done. |
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 very much!
M
Looks like you can merge now if you squash with the right commit message. Please let me know when you do |
535f6fd
to
de912e2
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
I see the following message in the (failing) copyright scan. Is that due to a missing copyright in the .cpp file?
|
de912e2
to
5f26553
Compare
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Yes, indeed. Fixed now. |
🤞 on test completion |
The final landing URL will be
https://unicode-org.github.io/icu/userguide/format_parse/messages/try-mf2.md,
right? I'll update the blog post.
…On Wed, Jan 15, 2025 at 2:00 PM Elango Cheran ***@***.***> wrote:
I see the following message in the (failing) copyright scan. Is that due
to a missing copyright in the .cpp file?
Yes, indeed. Fixed now.
—
Reply to this email directly, view it on GitHub
<#3334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMDRT2V2G3IPJYEG7V32K3K6NAVCNFSM6AAAAABVGCBQFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJUGAZDINBZGE>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
Just approved, so I think we are just waiting on the checks. |
I'm taking the liberty of punching the button... |
About how long do you think it is before it shows up on https://unicode-org.github.io/icu/userguide/format_parse/messages/? |
Should be very soon b/c the job is in progress. I'll keep a watch out. |
Done! User Guide is updated. Be sure to update the URL to be this (your previous guesses had a typo somehow): |
Great, thanks!
…On Wed, Jan 15, 2025 at 2:34 PM Elango Cheran ***@***.***> wrote:
Done! User Guide is updated. Be sure to update the URL to be this (your
previous guesses had a typo somehow):
https://unicode-org.github.io/icu/userguide/format_parse/messages/try-mf2.html
—
Reply to this email directly, view it on GitHub
<#3334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMBFR5GCS3TX6QE7MRL2K3PABAVCNFSM6AAAAABVGCBQFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJUGA3TIOJTHA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Add a how-to guide in the User Guide to show users how to try out MF 2.0 final candidate using the implementations in ICU (C++ and Java)
Checklist