Update document per JLReq TF discussions #17

himorin · 2020-04-27T02:56:59Z

for #16
Japanese version PDF ref. https://lists.w3.org/Archives/Public/public-i18n-japanese/2020AprJun/0155.html

ref. https://lists.w3.org/Archives/Public/public-i18n-japanese/2020AprJun/0155.html

…s original images

himorin · 2020-04-28T18:47:25Z

reorder of sections

new version (5.5) and previous version (3.2) are marked as n.0 (section 0 of new version) or p.0 (section 0 of previous version), in this memo.
subsections (block with heading text but no numbering) are marked with numbers from 1, like "ルビ処理のむつかしさ" in "0 はじめに" of ver 3.2 as p.0.1

part of n.0, comes from p.0.2
- first 2 paragraphs are newly added (one similar from JLReq abstract)
- last 2 paragraphs are from last 2 paragraphs of p.0.2
n.1.1 is from p.0.1 and part of p.0.2
- 1st line is newly added
- last paragraph is from 1st paragraph of p.0.2 (last sentence removed)
n.1.2 is from p.1.1
- 2nd sentense of n.1.2 (1) is newly added
- p.1.1 (2) is removed
- 2nd sentense of n.1.2 (2) is newly added
- n.1.2 (3-5) is almost newly added (or reworded with detail)
n.1.3 is from p.1.2 (the same without figure reference)
n.2.1 is from p.2.1 (the same without figure reference)
n.2.2 is from p.2.2
- 2nd sentense in leading paragraph is newly added
- (1),(2),(3),(5) is (almost) the same
- leading paragraphs in (4) is reworded (newly added)
n.2.3 is from p.2.3
- leading paragraphs are newly added (modified from leading paragraphs of (1),(2) in p.2.3)
- leading paragraph in (1),(2),(3) are simplified to one line
- 1st bullet in p.2.3 (1),(2),(3) is migrated into leading paragraphs (removed)
- adding condition of 'solid setting' to each bullets in (1),(2),(3) - other than these keep the same
- n.2.3 (4),(5) are from p.2.3 (4),(5)
n.2.4 is from p.2.4
- adding one sentense for 2-level method into leading paragraph
- the same for others
n.3 is newly added
p.3 was removed from document

reorder of notes (side note)

numbers are count from 1st one, as n.n1 or p.n1

note n.n1 'Ruby as notes', from p.n3
- newly addrd 3rd and later paragraphs
note n.n2 'Protrusion of ruby from base characters', from p.n1 (all reworded with new figures)
note n.n3 'Protruding over surrounding characters', from p.n6 (kept as the same)
note n.n4 'Wrap opportunities', from p.n2 (kept as the same)
note n.n6 'Wrap opportunities in group-ruby', from p.n7 (kept as the same)
note n.n5 newly added
note n.n7 for section n.3 newly added
note p.n3, p.n4 removed
note p.n8, p.n9, p.n10 for section p.3 removed

figures

figures without integrated description could be copied from Japanese one (no need to translate), and marked as '(ok)' below.

newly added figures are 1-3,23-26
- 1-3 are in https://lists.w3.org/Archives/Public/public-i18n-japanese/2020AprJun/0085.html (ok)
- 23-26 are in https://lists.w3.org/Archives/Public/public-i18n-japanese/2020AprJun/0066.html (ok)
fig 4-22 (except 9) in ver 5.5 are from fig 1-19 (except 6) in ver 3.2
fig 9 in ver 5.5 is from fig 6 in ver 3.2, but new part added
- got updated SVG image from bin-sensei in personal conversation, and replaced (ok)

himorin · 2020-04-28T18:48:53Z

At this point, following are finished (need to be checked)

reorder of (sub-)sections and updating text
replace of figures which are updated
moved notes to updated positions and updating text

https://lists.w3.org/Archives/Public/public-i18n-japanese/2020AprJun/0180.html

https://lists.w3.org/Archives/Public/public-i18n-japanese/2020AprJun/0198.html

xfq · 2020-05-12T05:14:22Z

index.html

+  <p class="checkme">This document describes simple method of processing for Ruby 
+  in Japanese layout realized with technologies like CSS, SVG, and XML-FO, 
+  as references to rendering engine implementors. 


This document describes simple method of processing for Ruby in Japanese layout realized with technologies like CSS, SVG, and XML-FO, as references to rendering engine implementors.

Maybe change it to something like:

This document describes a simple method of ruby composition for Japanese layout realized with technologies like CSS, SVG, and XML-FO, as basic information for implementations.

how about with updated?

I would use lowercase for "ruby", since it is lowercase in HTML, CSS, and many other places like the What is ruby? i18n article.

xfq · 2020-05-12T05:14:45Z

index.html

+  in Japanese layout realized with technologies like CSS, SVG, and XML-FO, 
+  as references to rendering engine implementors. 
+  Unlike 
+  <a href="https://www.w3.org/TR/jlreq/"><abbr title="Requirements for Japanese Text Layout">JLReq</abbr></a>


I'm leaning towards leaving only one link of jlreq here (i.e., only use [[JLREQ]]), but have no strong opinion.

I suppose this part is to have abbr tag for JLreq, so let me keep this as is.

xfq · 2020-05-12T05:15:21Z

index.html

+  Japanese layout. 
+  Points took in consideration are described in 
+  <a href="#matters-considered-by-the-simple-placement-rules"></a>. 
+  Also layout of dual ruby composition is added in this document which is not 


Should "dual ruby" be "double-sided ruby"? (Same below.)

want to get comment from @kidayasuo (and else)...
dual from https://w3c.github.io/jlreq/#n104 (but this uses "dual ruby composition", so might not better to use...)

I feel "double-sided" communicates what it is a bit better than dual (in Japanese "二重").

"double-sided-ruby" or "double-sided ruby"? (might be latter one,,,

I prefer using a compound adjective to modify a noun (i.e., double-sided ruby), instead of creating a compound noun (double-sided-ruby).

updated by b965f3a

index.html

kidayasuo · 2020-05-16T08:19:19Z

"large number of" → "a large number of".

I found it in two places.

(By the way how I refer the html code like @xfq does? (Kakkoi-!) In case of minor corrections which do not need discussions such as adding "a" or "the" it is easier for both if I can just make the change.)

xfq · 2020-05-16T10:14:14Z

(By the way how I refer the html code like @xfq does? (Kakkoi-!) In case of minor corrections which do not need discussions such as adding "a" or "the" it is easier for both if I can just make the change.)

@kidayasuo You can click the "Files changed" tab on the pull request, find index.html[1] and click "Load diff". Hover over the line of code where you'd like to add a comment, and click the blue comment icon. To add a comment on multiple lines, click and drag to select the range of lines, then click the blue comment icon.

In the comment field, type your comment. Optionally, to suggest a specific change to the line or lines, press cmd+g, then edit the text within the suggestion block. The OP can just click "apply suggestion" to apply your suggestion. This is easier than committing to the branch directly.

Footnotes:

[1] You can also mark other files as "viewed" on the right of the header of the files and they will collapse.

index.html

kidayasuo · 2020-05-16T21:37:46Z

index.html

+      Putting line break within ruby string is not allowed for mono-ruby. 
+      In addition, putting line break within ruby base text is not allowed 
+      for group-ruby. 
+      In contrast, interlinear notes may have large number of characters, 


Suggested change

In contrast, interlinear notes may have large number of characters,

In contrast, interlinear notes may have a large number of characters,

changed two parts.

index.html

kidayasuo · 2020-05-16T21:58:47Z

index.html

+      With this method, processing may go smoothly for the case with Kana 
+      characters as both preceding and following of ruby base text, 
+      but there is possible case of unbalanced display, 
+      like a combination of Kana character as preceding of ruby base text 
+      and Kanji character as following of ruby base text


Suggested change

With this method, processing may go smoothly for the case with Kana

characters as both preceding and following of ruby base text,

but there is possible case of unbalanced display,

like a combination of Kana character as preceding of ruby base text

and Kanji character as following of ruby base text

With this method, it can have an unbalanced look when Kana precedes the

ruby base and Kanji follows, or vice versa.

Simplified.

I somehow feel over-simplified on this point,,. How it is unbalanced might be difficult for those who is not familiar with Japanese?

Suggested change

With this method, processing may go smoothly for the case with Kana

characters as both preceding and following of ruby base text,

but there is possible case of unbalanced display,

like a combination of Kana character as preceding of ruby base text

and Kanji character as following of ruby base text

This method works well when characters preceding and following the ruby base are both Kana

or both Kanji. It however can have an unbalanced look when one is Kana and the other is Kanji

and if the ruby text is longer than the ruby base.

I do not think so as it explains that it would lay over Kana but not on Kanji. but I agree it might be over-simplified as it removes a whole sentence of the good case. How about this?

updated by afeab5f

Co-authored-by: Yasuo Kida （木田泰夫） <33173251+kidayasuo@users.noreply.github.com>

himorin · 2020-05-17T05:58:24Z

I tried to smooth out the second paragraph (and third so it connect well with the second):
As the original text is not in a technical writing style, sentences tend to be complex. Breaking them up would make it easier (but often you need supplementing subjects and tweaking).

pushed as 88e2a13, could you check @kidayasuo ?

…a with cl-15

kidayasuo · 2020-05-28T08:47:17Z

Approving the PR (did I already?). The document will be ready for FPWD once minor pending fixes are complete (Shimono-san said he will finish them by next Monday (in a timezone wherever the Monday comes last :)).

The document has a room for polish but the consensus at jlreq is it will be done after the FPWD.

himorin · 2020-05-28T08:52:07Z

Thank you for review. I'll remove all checkme and merge this shortly.

himorin added 8 commits April 27, 2020 09:59

Replaced Japanese version PDF with version 5.5.1

eedd955

ref. https://lists.w3.org/Archives/Public/public-i18n-japanese/2020AprJun/0155.html

added translateme CSS for temporary use

ac74308

reordered and updated/added images

4ee1a8f

reordered main body text and added updated Japanese as translateme

74801d8

reordered note asides, inserted added figures

700498e

adjusted size of SVG images (new ones)

56dc081

fixed issue on min-size of characters (with SVG transform)

5dd0f41

changed color of frame lines for characters from #000000 to #008CD6 a…

2710894

…s original images

himorin added 11 commits April 30, 2020 15:40

updated per files from bin-sensei

986f373

https://lists.w3.org/Archives/Public/public-i18n-japanese/2020AprJun/0180.html

to section 1.1

cde45c9

added checkme

b08570a

to 1.2.3

66e2d2e

to end of section 1

68facea

to end 2.2

05f2d7d

to end of section 2

984c169

JIS4051 -> JISX4051

d638d81

updated figures to SVG_20_05 as:

b9d4588

https://lists.w3.org/Archives/Public/public-i18n-japanese/2020AprJun/0198.html

for 3.1

8ccaa2a

to the end

0cde897

himorin requested review from kidayasuo, r12a and xfq May 11, 2020 08:27

himorin changed the title ~~[WIP] Update document per JLReq TF discussions~~ Update document per JLReq TF discussions May 11, 2020

fixed unchanged translateme

3901073

xfq reviewed May 12, 2020

View reviewed changes

index.html Outdated Show resolved Hide resolved

kidayasuo reviewed May 16, 2020

View reviewed changes

index.html Outdated Show resolved Hide resolved

kidayasuo reviewed May 16, 2020

View reviewed changes

index.html Outdated Show resolved Hide resolved

kidayasuo reviewed May 16, 2020

View reviewed changes

index.html Outdated Show resolved Hide resolved

kidayasuo reviewed May 16, 2020

View reviewed changes

himorin and others added 6 commits May 17, 2020 13:51

Ruby to ruby

f83daa8

"two step" to two-step

c5be235

added "a" to lage number of

09963f4

Update index.html

8b51900

Co-authored-by: Yasuo Kida （木田泰夫） <33173251+kidayasuo@users.noreply.github.com>

Update index.html

a309f3f

Co-authored-by: Yasuo Kida （木田泰夫） <33173251+kidayasuo@users.noreply.github.com>

Update index.html

95abc61

Co-authored-by: Yasuo Kida （木田泰夫） <33173251+kidayasuo@users.noreply.github.com>

himorin added a commit to himorin/simple-ruby that referenced this pull request May 17, 2020

replaced per w3c#17 (comment) by @kidayasuo

591274f

replaced per w3c#17 (comment) by @kidayasuo

88e2a13

himorin force-pushed the 202004-jlreqtf-update branch from 591274f to 88e2a13 Compare May 17, 2020 05:57

himorin added 3 commits May 18, 2020 16:13

replaced dual-ruby with double-sided ruby

b965f3a

Kana characters to Japanese characters, also replace reference to Kan…

1e7a9f2

…a with cl-15

updated per w3c#17 (comment) from @kidayasuo

afeab5f

himorin mentioned this pull request May 19, 2020

Update display for part with "JIS X 4051 [[JISX4051]]" #25

Closed

updated text per w3c#17 (comment)

30f2685

kidayasuo approved these changes May 28, 2020

View reviewed changes

removed all checkme class, added remove for css style (translate/check)

9356aaf

himorin merged commit 526c4be into w3c:gh-pages May 28, 2020

xfq mentioned this pull request Aug 14, 2020

Editorial fixes for https://github.com/w3c/simple-ruby/issues/44 #45

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update document per JLReq TF discussions #17

Update document per JLReq TF discussions #17

himorin commented Apr 27, 2020 •

edited by pr-preview bot

himorin commented Apr 28, 2020

himorin commented Apr 28, 2020

xfq May 12, 2020

himorin May 12, 2020

xfq May 12, 2020

himorin May 17, 2020

xfq May 12, 2020

himorin May 12, 2020

xfq May 12, 2020

himorin May 12, 2020

kidayasuo May 16, 2020

himorin May 17, 2020

xfq May 17, 2020

himorin May 18, 2020

kidayasuo commented May 16, 2020 •

edited

xfq commented May 16, 2020

kidayasuo May 16, 2020

himorin May 17, 2020

kidayasuo May 16, 2020

himorin May 17, 2020

kidayasuo May 17, 2020

kidayasuo May 17, 2020

himorin May 18, 2020

himorin commented May 17, 2020

kidayasuo commented May 28, 2020

himorin commented May 28, 2020

	In contrast, interlinear notes may have large number of characters,
	In contrast, interlinear notes may have a large number of characters,

Update document per JLReq TF discussions #17

Update document per JLReq TF discussions #17

Conversation

himorin commented Apr 27, 2020 • edited by pr-preview bot

himorin commented Apr 28, 2020

himorin commented Apr 28, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kidayasuo commented May 16, 2020 • edited

xfq commented May 16, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

himorin commented May 17, 2020

kidayasuo commented May 28, 2020

himorin commented May 28, 2020

himorin commented Apr 27, 2020 •

edited by pr-preview bot

kidayasuo commented May 16, 2020 •

edited