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

Review language specific issues for v2.0 of Content Usable #310

Open
rainbreaw opened this issue Nov 16, 2021 · 3 comments
Open

Review language specific issues for v2.0 of Content Usable #310

rainbreaw opened this issue Nov 16, 2021 · 3 comments
Assignees
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. review for next version

Comments

@rainbreaw
Copy link
Contributor

Moving the original issue, #248 , into a new issue so we can effectively track it for version 2.0 of Content Usable.

We missed the ability to add the note requested in the original ticket due to timing within the process. At this time, we are closing the older issue so as not to add confusion, and putting all of the open points in here in order to make sure that we can address it better in the next version.

Original issue from @xfq:

There are some related issues that only exist in some languages. Here are some examples:

Chinese, Japanese, and Thai text do not use space as word dividers, but some people who have dyslexia have difficulty reading those text without spaces, so preparing a type of document that can be rendered with space is very useful for them. CSS has a mechanism for this use case.

Some languages use ruby to provide phonetic transcriptions of obscure and little known characters, but sometimes ruby is difficult to read for some people with cognitive or learning disabilities, because they think ruby is a part of the character and can't separate ruby and base character. Therefore, some people would like to hide ruby, others would like to use different colors for ruby or widen the gap between ruby and base text.

Many East Asian scripts can be written horizontally or vertically, but some people have difficulty reading vertical text and would like to switch to horizontal text instead.

Please see if these examples are useful for personas in your document.

(This is i18n WG action 1003.)

Additional critical comment from @r12a just before Content Usable v1 was published:

The i18n WG asked me to request that, if it's too late to add a new persona, you add a brief note, explaining that different cultures may have different or additional needs (perhaps using Fuqiao's examples) and that you intend to address that in more detail in the next version. We will be happy to review that text for you. Then we would be ok with closing our tracker. Thanks.

@rainbreaw rainbreaw added i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. review for next version labels Nov 16, 2021
This was referenced Nov 16, 2021
@xfq xfq added i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. and removed i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. labels Nov 17, 2021
@julierawe
Copy link

Adding a reminder for myself to ask Roy for help reassigning this to me and/or tagging me on this ticket.

@julierawe
Copy link

Also adding a reminder to create a separate issue about creating a new persona.

@ruoxiran ruoxiran assigned julierawe and unassigned rainbreaw Dec 12, 2023
@murata2makoto
Copy link

Writing direction is another language-dependent issue. Both horizontal writing and vertical writing can be used for CJK text. The same text can be rendered in both directions (although some text chunks do not work well for vertical writing). Some people have problems with vertical writing, Others have problems with horizontal writing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. review for next version
Projects
None yet
Development

No branches or pull requests

5 participants