-
Notifications
You must be signed in to change notification settings - Fork 17
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
Make the Japanese and English termref consistent #396
Conversation
@kidayasuo agenda+ for 6 Feb. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the line 397, I see two spaces between "called" and "solid" in both original and updated text. Is this intentional?
@@ -394,9 +394,9 @@ <h4 id="principles_of_arrangement_of_kanji_and_kana_characters"> | |||
<span its-locale-filter-list="ja" lang="ja">漢字及び仮名の配置の原則</span> | |||
</h4> | |||
<p its-locale-filter-list="en" lang="en">In principle, when composing a line with <a class="characterClass" href="#cl-19">ideographic (cl-19)</a>, <a class="characterClass" href="#cl-15">hiragana (cl-15)</a> and <a class="characterClass" href="#cl-16">katakana (cl-16)</a> characters no extra spacing appears between their <a href="#term.character-frame" class="termref">character frame</a>. | |||
This is called solid setting | |||
This is called <a href="#term.solid-setting" class="termref">solid setting</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is called <a href="#term.solid-setting" class="termref">solid setting</a> | |
This is called <a href="#term.solid-setting" class="termref">solid setting</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approving.
merging this. |
The termref for "character frame" is not in Japanese and "ベタ組" is not in English.
💥 Error: 500 Internal Server Error 💥
PR Preview failed to build. (Last tried on Jan 29, 2024, 5:53 AM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Spec Generator - Spec Generator is the web service used to build specs that rely on ReSpec.
🔗 Related URL
If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.