-
Notifications
You must be signed in to change notification settings - Fork 17
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
Turning editors into contributor section #453
base: gh-pages
Are you sure you want to change the base?
Conversation
test material at https://jlreq-old.w3c.himor.in/NOTE-jlreq-20250218/Overview.html |
Three comments:
Update: Please also add Nat McCully to the list of Editors. He made editorial contributions to the English version. |
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.
Just a couple of comments.
Also, the addition of the dates of publication of the previous versions (in the Contributors section) is useful and a good idea. I'll just note that we usually recommend the use of a name for the month (a 3-letter abbreviation is fine) to reduce potential ambiguity — i know that the YMD approach is less ambiguous than other date formats, but it is also less familiar for many readers of English. (Of course, this comment doesn't affect the Japanese translation.) |
Should we keep the affiliation information for the contributors? |
ah, just followed another spec I've working on, but no personal preference,,, e.g. https://www.w3.org/TR/webxr/#ack |
My feeling is that we should also acknowledge that the organisations involved allowed the individuals to work on this, which is the main reason for keeping the affiliation information. |
If so, I would rather keep former format with combination of name and affiliation. |
I'm not sure what you mean by that. I was suggesting that we just add the affiliation (the one currently in the document's front matter) after the name in parens. But it's only a suggestion. If you prefer to leave as is, that's ok too. |
@@ -76,16 +59,16 @@ | |||
<body> | |||
<h1 class="title p-name" id="title">Requirements for Japanese Text Layout <br/><span lang="ja">日本語組版処理の要件(日本語版)</span></h1> | |||
|
|||
<div id="abstract"> | |||
<section id="abstract"> |
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.
If i remember correctly, we used the div markup here to avoid warning messages about using a section with no heading. You might want to check that out.
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 change looks good. Thank you!
company: "Invited Expert", | ||
w3cid: "40266" }, | ||
{ name: "Nathaniel McCully, (<span lang='ja'>第2版</span> 2nd edition)", |
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.
should include this @kidayasuo
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 spotting this.
Yes, please add Nat. He contributed to the English translations as an editor.
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. The change looks good.
memo from 2025-03-11 JL-TF call, @kidayasuo will contact xfq and Richard about how to organize both editor field and contributors section. |
As title, along with URL redirect fix.
@kidayasuo @xfq @r12a see middle part (lines 104-147 in new column). Do we have any other item to be mentioned here?