search

w3c / jlreq

Text Layout Requirements for Japanese
https://w3c.github.io/jlreq/
Other
100 stars 16 forks source link

Updating JL-TF charter #259

Closed himorin closed 3 years ago

himorin commented 3 years ago

@kidayasuo as placeholder for discussion.

As for now, PR has a text with just added 2yrs to end date from the current charter.

possible consideration points (as in chats):

kidayasuo commented 3 years ago

Thank you @himorin san for creating the gh issue. Could you add the url of the current charter to your opening comment so people can easily find the current one? (thanks)

Probably we can generalize the first two points you raised. What we are doing is redefining jlreq for internationalized software architecture (vs the current JLReq is based on printing architecture). By stating like this simplification of ruby can be seen as a part of it.

Of course we will continue updating the current JLReq document for fixing errors or usability. So, probably we will keep the original sentence also.

Update the Japanese Layout Requirements document to fix errata, or improve the accessibility and user-friendliness of the document.

(One of the important task here by the way would be to improve the usability of the two-language-in-one document. I still look at the old document because the new one is hard to use)

The first (gap analysis) and the last paragraph (other possible tasks) can probably be as is?

(In the gap analysis area one thing we found is that for some characters the behavior that Unicode defines do not match with requirements from JLReq/JIS X 4051. This clearly is a gap and probably we should create a document.)

Are there other parts of the charter document that benefit from updating? What do you think @r12a san?

I suspect that the need for updating xxReq for internationalized software architecture, and possible gaps between what xxReq expects what is defined in unicode, especially in the area of punctuations, might apply to some other languages.

xfq commented 3 years ago

Link to the charter: https://w3c.github.io/jlreq/charter/

xfq commented 3 years ago

Are there other parts of the charter document that benefit from updating?

A few small nits for your consideration:

xfq commented 3 years ago

And we should add Atsushi to the list of team contacts.

r12a commented 3 years ago

The above all sound good to me. I don't think this should turn into a major exercise, though. It should just be a succinct summary of current directions and setup, and we shouldn't spend a great deal of time on it unless there are controversial aspects.

I'm concerned about Kida-san struggling to use the dual language version, and would like to better understand why (maybe in a separate GH issue).

kidayasuo commented 3 years ago

I'm concerned about Kida-san struggling to use the dual language version, and would like to better understand why (maybe in a separate GH issue).

It is effectively #126. #236 is also related. The page opens with the mixture of text you want to read and chunks of text you do not need (that typically you can't read). To limit it to a language you want to read you need to click the language switching button. The order version opens clean without you having to do anything. Another issue that might not have been captured in gh is that if you jumped to a section you want to read first and then you click on the language button, the page refreshes to a different part of the document. This is annoying too. The new format is a good improvement in terms of the maintenance-ability but at this point it is a regression in the usability for our end users, which is true even for myself.

himorin commented 3 years ago

Updated minor points pointed above. (no change on JLReq document)

Also, recently, we seems to reach into some mutual understanding(s) on the next edition, like https://github.com/w3c/jlreq/issues/281, which could also be included.

r12a commented 3 years ago

LGTM. Ok to merge.

himorin commented 3 years ago

merged, all comment resolved.