-
Notifications
You must be signed in to change notification settings - Fork 120
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
fix punc, spelling, inconsistent labels, etc. #667
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.
There are some overlapping/redundant labels. They were not created by this PR, but after this PR, they don't align exactly, and that makes things look weird and unreadable.
@frivoal — I have no problem changing the partial overlap to be complete, with the new text taking precedence on the latter instance. I would also have no problem deleting one or the other if that makes sense. Oddly, GitHub is not offering me a "commit suggestion" button, so I'll have to manually apply the changes. Doing so now to make the obscuring overlap clear. Will delete whichever instance (if either) is determined to be unnecessary whenever that happens. |
Digging deeper... @fantasai @frivoal — The rendered SVG (now) shows no
Related to this, If you agree with the above, please +1 or similar, and I'll put them all into my PR. If you've partial disagreement, please note that as well, and I'll update what's agreed, and we can continue to discuss what's not agreed. |
This diagram has been reviewed for understandability by screenreaders, so whatever you do, don't break that. |
Maybe the easiest thing to do then is to move back the label by 2px so that it lines up again. |
Yes, I think the 2px nudge is the right answer for the overlaying labels, because these labels actually do apply to two pathways, so for screenreaders, they should be present twice. I am also changing all the |
@fantasai — You're not in the GitHub reviewer list, so I can't ask for that as such ... but here's a free-text request for your review. :-) |
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.
Mmmm, I'm not sure you wanted my review. :] Here's my full review:
- If you're intending to obsess over punctuation, I'm going to require you to use curly quotes properly. :)
- I would remove the “such as” clause for republishing WD, it's wordy and doesn't seem helpful.
- I would change “returned for further review” to “returned for further work” on X -> WD
- It's not clear whether the “such as” clause for PR->CRS is attached to both or to Team Decision only, and I'm not sure it's helping, so I would remove it also.
- Team Decision after AC Review should be “W3C Decision”.
- CRS->PR needs a WG Decision in addition to Team Approval.
- Need to be consistent in labeling the WG Decision + Team Approval bits. Some of them have an “and”, some of them don't. I suggest using a plus sign throughout, like in the old version. (This is a diagram, not free text.)
(I also think your extended “such as” clauses are too wordy for a diagram, but I can live with it.)
@fantasai — Keeping in mind that I did not create the diagram, only cleaned up a number of existing inconsistencies and (to my eye) errors, I think several of your bullets are not really appropriate to a review of my cleanup PR. Note: You can see exactly what I changed (vs. what I was changing and/or left alone) by viewing the files changed by the PR and clicking the In more detail —
My tools don't insert curly quotes unless I force them to. I generally avoid "smart" curly quotes because many automated tools choke on them in varying ways. They also tend to be used inconsistently and varyingly by international authors and editors, while straight quotes are usually consistently used. If curly quotes are to be used, I strongly advise using the HTML or other relevant escapes for those characters, because the characters themselves are often misread and mistreated by subsequent editors — variously leading to pairs of left-quotes, pairs of right-quotes, reversed left- and right-quotes, mixes of curly and straight quotes, and other offenses against correct punctuation. Also note that the W3C Manual of Style says to Use quotation marks rather than grave accents and apostrophes to quote text (e.g., ``value'' should read "value"). Note that this example itself uses straight quotes, suggesting (though not stating) that straight quotes are W3C style.
Unless the thing(s) following any "such as" instance are a full list of things that might be put there, something like
Please note that "further review" was the existing text. I am happy to make this change, but perhaps it should be in a different PR?
I changed an "e.g." into "such as", so again, I'm not sure dropping that clause should be done via this PR. Upon re-reading the whole diagram, I wonder whether the "AC Review and/or W3C Decision" on this vector (which had used
To be clear, this is on the PR->REC vector? (I wonder if that should change to "AC Review and W3C Decision", as it seems that both are required?)
Again, not my text. Happy to apply this, if confirmed appropriate for this PR.
This is indeed a diagram. Still, it will pass through text readers and other accessibility tools, and they will treat |
@TallTed, I pushed a set of changes to this branch that I think address all the relevant concerns with this diagram afaict. I think this now correctly represents the decision pathways. I did remove the “such as” clauses, because they're a bit much for the diagram given how many other things are going on here. (And also they weren't particularly accurate anyway.) Let me know what you think. |
The Revising W3C Process CG just discussed
The full IRC log of that discussion<fantasai> Subtopic: Improvements to REC track diagram<fantasai> github: https://github.com//pull/667 <fantasai> florian: Back and forth between TallTed and fantasai <fantasai> ... to improve the diagram and align it with current text <fantasai> ... afaict it is now pretty correct <cwilso> +1 <fantasai> plh: Any objections to approve? <fantasai> RESOLVED: Merge #667 to improve REC track diagram |
fixes #661