- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Jun 2021 00:01:18 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Informal spellings in specifications`, and agreed to the following: * `RESOLVED: We consider informal spellins to be typos to be fixed when found and avoided if possible` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Informal spellings in specifications<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/5850<br> <TabAtkins> i write all nite tho<br> <dael> florian: Keeps coming up and never had cnetral discussion. Mostly manifests in TabAtkins using spellins he believes is appropiate but many don't recognize.<br> <dael> florian: Double question. Are they appropriate and, given they're not recognized, as should specs stick with mainstream?<br> <dael> florian: I suspect would liek spec to stick to mainstream<br> <TabAtkins> q+ re my "goals"<br> <dael> florian: As a non-native speaker I didn't find them confusing but given my exposure to standards is a large part of how I learn English what I see in specs I assume to be normal. I think it's unpleasent for non-native speakers to assume thigns are mainstream when they are not.<br> <iank_> fwiw "thru" is very common in australian english<br> <astearns> ack TabAtkins<br> <Zakim> TabAtkins, you wanted to discuss my "goals"<br> <dael> florian: When you're a non-native speaker people look at you weird and think you don't speak properly. Probably not the goal of this, but a risk<br> <dael> TabAtkins: There has been speculation as to waht my goals are. I don't have any and that's how I write. It's not easy for me to train my fingers. Happy if people want to run spell check. We don't do it in general.<br> <dael> TabAtkins: This is just how my fingers spell the words. It was intentional on my part, but not a drive on my part ot make changes to English.<br> <dael> astearns: So you say TabAtkins you are fine with corrections. If people point out descrepencies will you make edits?<br> <dael> TabAtkins: I suspect if I say yes someone will go through and tell me to make changes and I'd rather they put in a PR<br> <iank_> q+<br> <dael> astearns: Oh yes. But I think I have seen I have this PR, please give review, and some comments are a misspell, I would appriciate if you made those changes<br> <dael> TabAtkins: Sure. It's fine.<br> <astearns> ack iank_<br> <dael> iank_: I wanted to quickly say I somewhat worry if we have a hard and fast rule about the type of English will be a barrier for people writing spec. Specifically non-US-English speakers<br> <dael> TabAtkins: There is a W3C rule that we write in Amreican English, but that's the whole rule<br> <smfr> q+<br> <dael> astearns: Fine for spec writers to use the skills they have and if a typo is pointed out we can fix<br> <astearns> ack smfr<br> <dael> fantasai: Should make an effort not to make typos<br> <dael> smfr: I think we spec undergo transition is a good time to do editorial pass and make sure spec is generally American English. Just like a privacy and security review<br> <dael> astearns: Makes sense<br> <dael> fantasai: Sounds like converging that non-standard spellins are typos and should be handled as such<br> <dael> astearns: Yep<br> <dael> florian: Works for me. Wanted to avoid having the discussion 23 times and do it once centrally<br> <dael> astearns: Prop: We consider informal spellins to be typos to be fixed when found and avoided if possible<br> <TabAtkins> fwiw: https://www.merriam-webster.com/dictionary/tho<br> <dael> RESOLVED: We consider informal spellins to be typos to be fixed when found and avoided if possible<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5850#issuecomment-853458238 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 June 2021 00:01:58 UTC