-
Notifications
You must be signed in to change notification settings - Fork 215
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
All Translation Redesign #167
Conversation
…porating standards/guidelines TODO: - [ ] Fix nesting - [ ] Fix showing HTML :-) - [ ] Ask @slhenry if that is what we want to do
+1 to DLs and bold DTs = good for skimming in language I'm mildly thinking:
Happy to discuss! |
Hm. I would need to shuffle the standards and guidelines into the other resources so that they can be found alphabetically. Having them separate is much easier. (I think it might also be easier for users to find them.)
I can remove it. Are we planning to list unauthorized translations, too? |
OK. Don't need "Translated Standards/Guidelines" -- just "Standards/Guidelines" -- and we already have the translation for that in the yml -- just need to get the ones we don't have...
um... good question... I was thinking that we would... however they're not on our site so some issues with it... however, W3C links to them... /me will open separate issue (later) to get more feedback... I guess for now, not. |
|
Deploy preview for wai-website failed. Built with commit 5532dc7 https://app.netlify.com/sites/wai-website/deploys/5d11e08658c6c10007cdd48e |
@slhenry I have now used “Standards/Guidelines” in English by default, we don’t have translations for that at the moment. Let me know if OK to publish. |
Yeah! [insert cheering emoji here] I updated the intro text. (I see that you put it in a box titled "Summary" – but it's not quite a summary – since it has info that's not elsewhere on the page. I guess it's not a big deal.) A few things: Add listingsI reviewed all of these and am comfortable linking to them.
Language headings
?: About the order – is that happening programmatically? (It seems a bit odd, yet probably not worth messing with.) Other
I guess we want to add to the yml file "Standards/Guidelines", and solicit translations of that, and then use the translated term when we have enough? And, while we're at it, we should also add to the yml file the other words in the main nav , so we have them when those pages are translated? |
@slhenry okay so we WANT to add unauthorized translations. That changes the scope and needs more work. I’ll work on the things I need to know to make it happen so we can talk about them on Tuesday and I can implement them eventually. |
Is that a task that you will do or that I’m supposed to do?
They can be changed in the wai-website-data repository: https://github.com/w3c/wai-website-data/blob/master/lang.json I’m not comfortable to make some of those changes as I don’t speak these languages and therefore don’t know how to address them properly.
We don’t have any way to do that. The
The order does not come out as I wished it would at the moment, unsure why, could improve.
What would that be described as? “Translating Organization”? We would need to get translations for that for all languages. Or do we go with just “Translator:” where we already have translations?
I am unsure what that means.
Maybe. I’m just thinking of getting this out the door.
No, those will be translated with the pages and not connected to the translations here. |
I’m happy to change the text of “Summary”, I just wanted some resemblance of the other pages and as we are starting almost every page with a box, I added it here, too. |
"name":"Portuguese (Brazil)", -> "name":"Brazilian Portuguese", w3c/wai-website#167
I think I have addressed most of the checks above, but the order/sort issue.
|
I will do.
Let me know which ones you want me to check on.
That's fine for now. (We can see if anyone balks and wants "Lead translating organization (LTO):")
Please check that the links work.
+1 to get this iteration published, and defer this to later iteration!
/me knows not connected to translations here – was just thinking ahead… |
Already done in fe76fb8
Basically all the descriptions for languages in the language file: https://github.com/w3c/wai-website-data/blob/master/lang.json (I made the changes above, but I’m not sure about removing Valencian. Also, the Brazilian Portuguese/European Portuguese needs to be addressed. I could imagine some strong feelings by people from Portugal.)
Done.
I copied the links from W3.org and so I guess they all work, most of them I clicked on. (SiteImprove has a link checker that we can use.)
If the wording is set, it takes the translation, otherwise the English fallback. Same for "Translator:".
No problem. :-) |
This is looking great, @yatil! I would be comfortable publishing it now. (I'm eager to point to this updated version. :-) |
I updated Portuguese in the lang file. I think it would be best if "Simplified Chinese" was sorted by "Chinese" for alphabetical order. |
@slhenry It is sorted by the abbreviation (zh-hans). We can sort by the name (Simplified Chinese) instead. Or we introduce a sort-by Attribute in the languages file that we use for sorting. While the last one is possible, it would complicate programming and take significant effort. If we want to do that, please open a new issue with a feature request. (Commenting on closed issues or PRs risks losing them and we don’t want to re-open merges PRs when possible.) |
First attempt at redesigning the all translations page and also incorporating standards/guidelines
TODO: