Skip to content
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

[questions/qa-when-lang-neg] Possible typos #390

Closed
xfq opened this issue Jun 7, 2022 · 4 comments · Fixed by #392
Closed

[questions/qa-when-lang-neg] Possible typos #390

xfq opened this issue Jun 7, 2022 · 4 comments · Fixed by #392

Comments

@xfq
Copy link
Member

xfq commented Jun 7, 2022

https://www.w3.org/International/questions/qa-when-lang-neg.en.html

Suppose Sylvia visits www.example.be and gets Flemish (situation 2 or 3). She then clicks on the German control and reads on, no real trouble. But she then clicks on a link to get to an interesting page within the site. Oops, Flemish again! Fortunately, the German control is still there, but after a couple of such detours she's getting understandably frustrated. Can't www.example.be just remember that she can't read Flemish? What is needed here is some stickyness of the explicit language selection.

"stickyness" should probably be "stickiness".

Note however than some measure of cultural adaptation (e.g. changing the currency) does not necessarily make pages non-equivalent

"Note however than" should probably be "Note however that".

@JohnTitor
Copy link
Member

Agree, submitted #392 to fix them.

@r12a
Copy link
Contributor

r12a commented Jun 8, 2022

Whlie i agree that the dictionary form of the word is (nearly always) 'stickiness', i never changed it before because i quite like 'stickyness' in that it makes more obvious the relationship of the word to 'sticky'. If it's felt that we must change it, that's ok, but i'm much less inclined to change the id of the navigation section – otherwise it can break links into the document.

@JohnTitor
Copy link
Member

I don't have a strong preference but if we prefer "stickyness", i.e. a word outside of the dictionary, it'd be great if we have a policy and document it somewhere, so that editors aren't confused and we can avoid the use of various spellings. In light of that, I think preferring dictionary spelling would be a simple way here.
But I totally agree about the ID, dropped the related change from #392.

@r12a
Copy link
Contributor

r12a commented Jun 8, 2022

I'd certainly rather just adopt the dictionary spelling if the alternative involves all those other things.

@r12a r12a closed this as completed in #392 Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants