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.

Sign up for GitHub

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

Allow Ruby use in non-CJKM languages #145

Open
wants to merge 2 commits into
base: gh-pages
Choose a base branch
from
+1 −1
Open

Allow Ruby use in non-CJKM languages #145

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
713307c
Say that it's ok to use Ruby in non-Asian languages.
jyasskin Oct 22, 2024
be31052
Be less specific about the kinds of annotations, per Elika's advice.
jyasskin Oct 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3794,7 +3794,7 @@ <h3>Ruby text annotations</h3>
<p class="advisement">Ruby implementations should allow annotations to appear on either or both sides of the base text.</p>
</div>
<div class="req" id="ruby_cjk">
<p class="advisement">Ruby markup in HTML is designed specifically for Chinese, Japanese, Korean, and Mongolian requirements, and should not be used as a general glossing mechanism.</p>
<p class="advisement">Ruby markup in HTML is designed primarily for Chinese, <a data-cite="jlreq#usage_of_ruby">Japanese</a>, Korean, and Mongolian requirements, and the needs of those languages should be prioritized in any use of the Ruby elements in other specifications. Within that constraint, Ruby may be used to associate annotations with a base string of text.</p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The I18N WG discussed this in our 2024-10-31 teleconference. We don't quite agree with the changes proposed here. This is not because other annotation uses for Ruby do not exist in the wild, but that they are rare, usually can be better handled using other markup mechanisms, and because novel uses of Ruby conflict with their intended use. In addition, bear in mind that this document is guidance to specification authors and we seek to guide the audience the best we can.

Perhaps consider a modification like the following?

Suggested change
<p class="advisement">Ruby markup in HTML is designed primarily for Chinese, <a data-cite="jlreq#usage_of_ruby">Japanese</a>, Korean, and Mongolian requirements, and the needs of those languages should be prioritized in any use of the Ruby elements in other specifications. Within that constraint, Ruby may be used to associate annotations with a base string of text.</p>
<p class="advisement">Ruby markup in HTML is designed primarily for Chinese, Japanese, Korean, and Mongolian requirements. Annotation in other languages SHOULD use other mechanisms. Specifications SHOULD avoid proposing new uses for Ruby markup.</p>
<p class="note">For examples of other types of annotation markup available in HTML, see <a href="https://r12a.github.io/blog/201708.html#20190304">post on Richard Ishida's blog </a>.</p>

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@r12a @xfq for visibility

</div>
</section>

Expand Down