All Translation Redesign #167

yatil · 2019-06-13T19:58:29Z

First attempt at redesigning the all translations page and also incorporating standards/guidelines

TODO:

Fix nesting
Fix showing HTML :-)
Ask @slhenry if that is what we want to do

@slhenry

…porating standards/guidelines TODO: - [ ] Fix nesting - [ ] Fix showing HTML :-) - [ ] Ask @slhenry if that is what we want to do

shawna-slh · 2019-06-13T20:35:13Z

+1 to DLs and bold DTs = good for skimming in language

I'm mildly thinking:

Not have separate section for "Translated Standards/Guidelines". Possibly add "Standard" after the link (if easy to do)
Don't need to indicate "Authorized".

Happy to discuss!

yatil · 2019-06-14T07:05:20Z

Not have separate section for "Translated Standards/Guidelines". Possibly add "Standard" after the link (if easy to do)

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.)

Don't need to indicate "Authorized".

I can remove it. Are we planning to list unauthorized translations, too?

shawna-slh · 2019-06-14T16:03:11Z

Having them separate is much easier.

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...

Are we planning to list unauthorized translations, too?

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.

yatil · 2019-06-18T15:39:26Z

English Standards/Guidelines if not available

…le in languages

netlify · 2019-06-21T10:37:43Z

Deploy preview for wai-website failed.

Built with commit 5532dc7

https://app.netlify.com/sites/wai-website/deploys/5d11e08658c6c10007cdd48e

yatil · 2019-06-21T10:39:03Z

@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.

shawna-slh · 2019-06-21T22:24:00Z

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 listings

I reviewed all of these and am comfortable linking to them.

To Simplified Chinese listing, under Standards/Guidelines, add: 无障碍创作工具指南(ATAG) 2.0 https://www.w3.org/Translations/ATAG20-zh/
Add Hebrew https://www.isoc.org.il/files/w3c-wai/guidelines.html
Add Hungarian http://www.w3c.hu/forditasok/WCAG20/
Add Japanese https://waic.jp/docs/WCAG20/Overview.html
Add Polish http://fdc.org.pl/wcag2/
Add Spanish http://www.sidar.org/traducciones/wcag20/es/

Language headings

I think "(Greek, Modern)" would be better as just "(Greek)"
I'm not sure about "Català (Catalan; Valencian)". Based on translation I'm thinking it can just be "Català (Catalan)" or even just "Catalan" based on their title: "Traducció catalana autoritzada"? We can ask Martin &/or translators if needed.
In English, best to say "Brazilian Portuguese", "European Portuguese", "Simplified Chinese", "Traditional Chinese". Not sure the best way to handle that in this page – for usability and technically. For English, see how it's done in WCAG 2.o Portuguese listing – with a single row and multiple listings. For this page, I wonder about an {h2} for Portuguese and {h3} for the different ones? Probably good for usability – maybe not easy technically?
. Brazilian Portuguese Authorized Translation is titled "Tradução Autorizada em Português do Brasil"
. European Portuguese Authorized Translation is titled "Tradução Autorizada em Português Europeu"
. W3C Translations list uses "Português-BR (Brazilian Portuguese)"
… I'll ask Reinaldo and Caroline, and will CC you in the e-mail.

?: About the order – is that happening programmatically? (It seems a bit odd, yet probably not worth messing with.)

Other

To the Standards/Guidelines listings, add the LTO or Translator. Can get that from W3C Translations list if that's easiest
Typo – quote(") at then end of: English title: Understanding WCAG 2.0"
when publish, please do link check

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?

yatil · 2019-06-22T08:29:42Z

@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.

yatil · 2019-06-23T06:33:05Z

I reviewed all of these and am comfortable linking to them.
[list of translations]

Is that a task that you will do or that I’m supposed to do?

Language headings

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.

In English, best to say "Brazilian Portuguese", "European Portuguese", "Simplified Chinese", "Traditional Chinese". Not sure the best way to handle that in this page – for usability and technically. For English, see how it's done in WCAG 2.o Portuguese listing – with a single row and multiple listings. For this page, I wonder about an {h2} for Portuguese and {h3} for the different ones? Probably good for usability – maybe not easy technically?

We don’t have any way to do that. The pt and pt-BR are distinct translations.

?: About the order – is that happening programmatically? (It seems a bit odd, yet probably not worth messing with.)

The order does not come out as I wished it would at the moment, unsure why, could improve.

To the Standards/Guidelines listings, add the LTO or Translator. Can get that from W3C Translations list if that's easiest

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?

when publish, please do link check

I am unsure what that means.

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?

Maybe. I’m just thinking of getting this out the door.

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?

No, those will be translated with the pages and not connected to the translations here.

yatil · 2019-06-24T12:24:03Z

(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.)

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.

w3c/wai-website#167

"name":"Portuguese (Brazil)", -> "name":"Brazilian Portuguese", w3c/wai-website#167

w3c/wai-website#167

yatil · 2019-06-24T16:16:20Z

I think I have addressed most of the checks above, but the order/sort issue.

Fix sorting

shawna-slh · 2019-06-24T16:40:09Z

I reviewed all of these and am comfortable linking to them.

Is that a task that you will do or that I’m supposed to do?

I will do.

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.

Let me know which ones you want me to check on.

To the Standards/Guidelines listings, add the LTO or Translator. Can get that from W3C Translations list if that's easiest

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?

That's fine for now. (We can see if anyone balks and wants "Lead translating organization (LTO):")

when publish, please do link check

I am unsure what that means.

Please check that the links work.

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?

Maybe. I’m just thinking of getting this out the door.

+1 to get this iteration published, and defer this to later iteration!

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?

No, those will be translated with the pages and not connected to the translations here.

/me knows not connected to translations here – was just thinking ahead…

yatil · 2019-06-24T16:46:18Z

@slhenry

I reviewed all of these and am comfortable linking to them.

Is that a task that you will do or that I’m supposed to do?

I will do.

Already done in fe76fb8

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.

Let me know which ones you want me to check on.

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.)

To the Standards/Guidelines listings, add the LTO or Translator. Can get that from W3C Translations list if that's easiest

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?

That's fine for now. (We can see if anyone balks and wants "Lead translating organization (LTO):")

Done.

when publish, please do link check

I am unsure what that means.

Please check that the links work.

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.)

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?

Maybe. I’m just thinking of getting this out the door.

+1 to get this iteration published, and defer this to later iteration!

If the wording is set, it takes the translation, otherwise the English fallback. Same for "Translator:".

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?

No, those will be translated with the pages and not connected to the translations here.

/me knows not connected to translations here – was just thinking ahead…

No problem. :-)

#167

shawna-slh · 2019-06-25T08:17:02Z

This is looking great, @yatil!

I would be comfortable publishing it now. (I'm eager to point to this updated version. :-)
When we get replies about the language listings, we can update.
If you want to wait for that or other, that's OK with me.
If you want to publish now, that's OK with me. ;-)

shawna-slh · 2019-06-28T20:25:27Z

I updated Portuguese in the lang file.

I think it would be best if "Simplified Chinese" was sorted by "Chinese" for alphabetical order.

yatil · 2019-06-29T06:52:22Z

@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.)

yatil added 2 commits June 13, 2019 21:50

Tech/Preview update

fd74356

First attempt at redesigning the all translations page and also incor…

48fd92d

…porating standards/guidelines TODO: - [ ] Fix nesting - [ ] Fix showing HTML :-) - [ ] Ask @slhenry if that is what we want to do

yatil added 2 commits June 14, 2019 16:01

Fixed nesting, added spacing

b0516c8

Attempt to fix order, add more data

634eaee

Use English Standards/Guidelines as they are not consistently availab…

5becfc3

…le in languages

yatil requested a review from shawna-slh June 21, 2019 10:39

Update translations.md

1729181

Update externals

53209c6

yatil added 2 commits June 24, 2019 16:19

Fix typo

dbebfac

Expand translation phrase lookup

4d99add

yatil added a commit to w3c/wai-website-data that referenced this pull request Jun 24, 2019

Greek, Modern -> Greek

fdf53cb

w3c/wai-website#167

yatil added a commit to w3c/wai-website-data that referenced this pull request Jun 24, 2019

Catalan; Valencian -> Catalan

5825da9

w3c/wai-website#167

yatil added a commit to w3c/wai-website-data that referenced this pull request Jun 24, 2019

"name":"Portuguese", -> "name":"European Portuguese",

856fa24

"name":"Portuguese (Brazil)", -> "name":"Brazilian Portuguese", w3c/wai-website#167

Update externals

2edea28

yatil added a commit to w3c/wai-website-data that referenced this pull request Jun 24, 2019

"name":"Hebrew (modern)", -> "name":"Hebrew",

15606e6

w3c/wai-website#167

Add contents and translators

fe76fb8

Typo

6389a2d

yatil added 2 commits June 25, 2019 09:14

Add proper sorting

26e9bb1

#167

Update externals

941159a

Update externals

5532dc7

yatil merged commit 5532dc7 into master Jun 25, 2019

yatil deleted the all-translation-redesign branch June 29, 2019 07:46

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

All Translation Redesign #167

All Translation Redesign #167

yatil commented Jun 13, 2019 •

edited

Loading

shawna-slh commented Jun 13, 2019

yatil commented Jun 14, 2019

shawna-slh commented Jun 14, 2019 •

edited

Loading

yatil commented Jun 18, 2019 •

edited

Loading

netlify bot commented Jun 21, 2019 •

edited

Loading

yatil commented Jun 21, 2019

shawna-slh commented Jun 21, 2019 •

edited by yatil

Loading

yatil commented Jun 22, 2019

yatil commented Jun 23, 2019

yatil commented Jun 24, 2019

yatil commented Jun 24, 2019 •

edited

Loading

shawna-slh commented Jun 24, 2019

yatil commented Jun 24, 2019 •

edited

Loading

shawna-slh commented Jun 25, 2019

shawna-slh commented Jun 28, 2019

yatil commented Jun 29, 2019

All Translation Redesign #167

All Translation Redesign #167

Conversation

yatil commented Jun 13, 2019 • edited Loading

shawna-slh commented Jun 13, 2019

yatil commented Jun 14, 2019

shawna-slh commented Jun 14, 2019 • edited Loading

yatil commented Jun 18, 2019 • edited Loading

netlify bot commented Jun 21, 2019 • edited Loading

yatil commented Jun 21, 2019

shawna-slh commented Jun 21, 2019 • edited by yatil Loading

Add listings

Language headings

Other

yatil commented Jun 22, 2019

yatil commented Jun 23, 2019

yatil commented Jun 24, 2019

yatil commented Jun 24, 2019 • edited Loading

shawna-slh commented Jun 24, 2019

yatil commented Jun 24, 2019 • edited Loading

shawna-slh commented Jun 25, 2019

shawna-slh commented Jun 28, 2019

yatil commented Jun 29, 2019

yatil commented Jun 13, 2019 •

edited

Loading

shawna-slh commented Jun 14, 2019 •

edited

Loading

yatil commented Jun 18, 2019 •

edited

Loading

netlify bot commented Jun 21, 2019 •

edited

Loading

shawna-slh commented Jun 21, 2019 •

edited by yatil

Loading

yatil commented Jun 24, 2019 •

edited

Loading

yatil commented Jun 24, 2019 •

edited

Loading