Skip to content

Conversation

@himorin
Copy link
Contributor

@himorin himorin commented Mar 18, 2022

closes #74, NOTE: conflicts to #75

use ruby box and two 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

Copy link

@murata2makoto murata2makoto left a 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.

@murata2makoto
Copy link

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?

@himorin
Copy link
Contributor Author

himorin commented Mar 22, 2022

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..

@himorin
Copy link
Contributor Author

himorin commented Apr 18, 2022

drafting back and forth for a while,,, how about something like below?

  • two-level processing specific terms are not clearly defined
  • align with provided text
<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 
    are not modified by the second level such as in light of any characters or line edge preceding and following the <a>ruby box</a>.
    Two levels are processed as following:
    <ol>
    <li id="l20220318001">The first level takes pairs of ruby annotation and its base text 
        and parameters required for procesing such as available space in inline direction in the current line, 
        but does not take any preceding or following characters. 
        The first level outputs one or more untransparent <a>ruby boxes</a>, which have relative position of ruby annotation to its base.</li>
    <li id="l20220318002">The second level takes a size of untransparent <a>ruby box</a> and its preceding and following text, 
        and outputs styled text.</li>
    </ol>
</li>

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
Copy link
Contributor

@r12a r12a Aug 5, 2022

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.

Copy link
Contributor

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).

Copy link
Contributor Author

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...

Copy link
Contributor Author

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
@himorin
Copy link
Contributor Author

himorin commented Feb 7, 2023

drafting back and forth for a while,,, how about something like below?

After several offline conversations and discussions,,, how about as following: @murata2makoto @kidayasuo ?

<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
     are not referenced nor modified by the second level such as in light of any characters or line edge preceding and 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
         including parameters needed for processing, such as available space in the inline direction of the current line,
         but excluding any preceding or following characters to the ruby base.
         The first level outputs one or more <a>ruby boxes</a>, that indicate the outside size of <a>ruby boxes</a>
         and the position of the ruby annotation with respect to its base.</li>
     <li id="l20220318002">The second level looks at the outside size of <a>ruby box</a> and its surrounding text,
         and outputs styled text.</li>
     </ol>
</li>

Copy link
Contributor

@kidayasuo kidayasuo left a 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!

@himorin himorin changed the title [WIP] replaced two-step processing part replaced two-step processing part Apr 20, 2023
@kidayasuo
Copy link
Contributor

kidayasuo commented Apr 28, 2023

Is the only change adding the PDF after my approval?

@himorin
Copy link
Contributor Author

himorin commented Apr 30, 2023

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

Copy link
Contributor

@kidayasuo kidayasuo left a 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!

Copy link
Contributor

@r12a r12a left a 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
Copy link
Contributor

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.
Copy link
Contributor

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...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Suggested change
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
Copy link
Contributor

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.

Copy link
Contributor

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
Copy link
Contributor

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?

Copy link
Contributor

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>.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Suggested change
Meanwhile, the second level determines inline positions of <a>ruby boxes</a>.
The second level determines inline positions of <a>ruby boxes</a>.

@kidayasuo
Copy link
Contributor

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?

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.

two-step processing method to two-level processing method?

4 participants