-
Notifications
You must be signed in to change notification settings - Fork 3
replaced two-step processing part #84
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
base: gh-pages
Are you sure you want to change the base?
Conversation
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 am not sure if I can improve Shimono-san's English. But let me try
The first level determines the relative positions of ruby base and ruby annotations and creates ruby boxes. Meanwhile, the second level determines the position of ruby boxes in lines. In other words, the relative positions of ruby base and ruby annotation as decided in the first level are not modified in light of any characters or line edges preceding or following ruby boxes.
|
As of now, " Two levels are processed as following, with using ruby column for paired ruby annotation...." is hard to understand. Do we really need this? |
Yeah... really wondering how to locally define two words here.. |
|
drafting back and forth for a while,,, how about something like below?
|
index.html
Outdated
| but without any preceding or following characters, | ||
| and outputs one or more untransparent <a>ruby box</a>.</li> | ||
| <li id="l20220318002">The second level takes a size and preceding and following text of <a>ruby boxes</a>, | ||
| <li id="l20220318001">The first level takes pairs of ruby annotation and its base text |
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.
Suggested edits:
The first level takes pairs of ruby base and its annotation, including parameters needed for processing, such as available space in the inline direction of the current line. The first level outputs one or more [ruby boxes], that indicate the position of the ruby annotation with respect to its base.
The second level looks at the size of untransparent [ruby box] and its surrounding text, and outputs styled text.
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'm not clear what 'untransparent' means (i haven't looked around the document for an explanation).
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 for comment on this. For 'untransparent', there is still discussion on terminology and explanation even in Japanese, and we are seeking better (and clearer?) text for this part...
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.
text updated per discussion within JL-TF. 'untransparent' has gone.
following a suggestion from @r12a
After several offline conversations and discussions,,, how about as following: @murata2makoto @kidayasuo ? |
kidayasuo
left a comment
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.
Changes look good. thank you!
|
Is the only change adding the PDF after my approval? |
Update of PDF is not limited to this PR, since it's not updated as diff but by one binary, so PDF will be updated in parallel as #83 |
kidayasuo
left a comment
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 am fine with the fix. thank you!
r12a
left a comment
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.
In addition to the specific comments here, i think the document needs a thorough edit for English wording. I may be able to help, if i can find time for it, but probably best wait until these and other issues are resolved.
We should also not forget to ask the i18n WG to review the document at some point - probably after the edit for English, to avoid getting many reports of editorial nits.
| <li id="l20200529009">Processing is done in two levels. | ||
| The first level only determines relative positions of ruby annotation and its base. | ||
| Meanwhile, the second level determines inline positions of <a>ruby boxes</a>. | ||
| In other words, relative positions of the ruby annotation and its base text as decided in the first level |
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.
This is a very, very long sentence, and gets a little confusing towards the end. Can it be broken up? For example, we might be able to say:
In other words, the relative positions of the ruby annotation and its base text, as decided in the first level, are not referenced nor modified by the second level. For example, this is not affected by..., except where....
| To summarise, the relative positions decided in the first step are not | ||
| modified by the second step at all.</li> | ||
| <li id="l20200529009">Processing is done in two levels. | ||
| The first level only determines relative positions of ruby annotation and its base. |
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.
suggestion:
...relative positions of each ruby annotation...
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 first level only determines relative positions of ruby annotation and its base. | |
| The first level only determines relative positions of each ruby annotation and its base. |
| <li id="l20200529009">Processing is done in two levels. | ||
| The first level only determines relative positions of ruby annotation and its base. | ||
| Meanwhile, the second level determines inline positions of <a>ruby boxes</a>. | ||
| In other words, relative positions of the ruby annotation and its base text as decided in the first level |
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 think we can drop 'Meanwhile'. Either that or replace it with 'On the other hand' if you want to stress the distinction, though i think having 2 levels already does that.
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 just read the previous version of this sentence, and it seems much clearer. What was the goal in rewriting it?
| which may be used by the second level for removing spacing of the characters preceding or following the <a>ruby box</a>. | ||
| Two levels are processed as following: | ||
| <ol> | ||
| <li id="l20220318001">The first level takes pairs of ruby base and its annotation |
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 numbered list items here seem to just repeat what was already said. Are they useful?
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 phrase " and outputs styled text" seems a little vague. What is styled, and how? Is the meaning simply that it outputs a ruby block that is integrated with the surrounding text?
| modified by the second step at all.</li> | ||
| <li id="l20200529009">Processing is done in two levels. | ||
| The first level only determines relative positions of ruby annotation and its base. | ||
| Meanwhile, the second level determines inline positions of <a>ruby boxes</a>. |
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.
| Meanwhile, the second level determines inline positions of <a>ruby boxes</a>. | |
| The second level determines inline positions of <a>ruby boxes</a>. |
|
If we already have a fix that is reasonable we can go ahead. Otherwise we can process the original issue as not-to-be-fixed. What do you think? |
closes #74, NOTE: conflicts to #75
use
ruby boxandtwo level, with new text from Bin-sensei.still wip.
original Japanese text: https://lists.w3.org/Archives/Public/public-i18n-japanese/2022JanMar/0037.html
but could be updated later.
Preview | Diff