Bug 161150 - Rename "phonetic reading"
Summary: Rename "phonetic reading"
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: CJK TableofContents-Indexes l10n-Optimization
  Show dependency treegraph
 
Reported: 2024-05-17 12:42 UTC by Tuomas Hietala
Modified: 2024-06-04 00:18 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tuomas Hietala 2024-05-17 12:42:02 UTC
Description:
The term "phonetic reading" is used in a few places in LO UI. Its meaning is a bit unclear. Such term is does not appear to be generally used in English outside of LO. I assume it could be a mistranslation from another language.

In LO, it appears to be related to the readings of Japanese kanji. In English, the readings of kanji are called just "readings", though:
https://en.wikipedia.org/wiki/Kanji#Readings

I suggest that "phonetic reading" should be changed to "reading", unless it for some reason refers to e.g. on'yomi specifically (as opposed to kun'yomi), in which case it would be better to change it to "on'yomi".

https://en.wikipedia.org/wiki/On'yomi
https://en.wikipedia.org/wiki/Kun%27yomi


Steps to Reproduce:
1. See https://translations.documentfoundation.org/search/libo_ui-master/-/en/?q=phonetic+reading&sort_by=-priority%2Cposition&checksum=


Actual Results:
The unusual and ambiguous term "phonetic reading" is used.

Expected Results:
The UI strings make use of commonly accepted and unambiguous English terms, making them easier to understand and translate.


Reproducible: Always


User Profile Reset: No

Additional Info:
n/a
Comment 1 V Stuart Foote 2024-05-18 14:02:07 UTC
Found in the LO "Asian Phonetic Guide" feature when CJK support is enabled.

Where the usage is as 'Ruby Annotation' aka 'Rubi'
https://www.w3.org/TR/ruby/
https://en.wikipedia.org/wiki/Ruby_character

with some supplement by extension:

https://extensions.libreoffice.org/en/extensions/show/bopomofo-annotate
https://extensions.libreoffice.org/en/extensions/show/kanji-to-phoentic

Would also apply to IPA "phonetic" transcription/annotation if we supported it.

So a change to "reading" provides a context for translation. But not clear "Ruby text/Base text" as a string replacement of "phonetic reading" improves cognition.

But maybe "Ruby/rubi phonetic reading"
Comment 2 Stéphane Guillou (stragu) 2024-06-04 00:18:10 UTC
Looks like it's mostly used for the Index Entry dialog. See:
* source: https://opengrok.libreoffice.org/search?project=core&full=%22phonetic+reading%22&defs=&refs=&path=&hist=&type=&xrd=&nn=1&si=full&si=full
* help page: https://help.libreoffice.org/latest/en-US/text/swriter/01/04120100.html

From help page:

> # Phonetic reading
> Enter the phonetic reading for the corresponding entry. For example, if a
> Japanese Kanji word has more than one pronunciation, enter the correct 
> pronunciation as a Katakana word. The Kanji word is then sorted according to 
> the phonetic reading entry. This option is only available if Asian language 
> support is enabled.

To see it in the UI:
1. Tools > Options > Languages and Locales > Default languages for documents > Asian (ticked)
2. Insert > Table of Contents and Index > Index Entry

I see how some might want to make the wording more consistent with the Asian Phonetic Guide feature, but my understanding is that Rubi characters refer to text annotations and their placement along text, whereas the Index dialog only refers to prononciation for sorting. So maybe the wording needs to remain distinct.

(In reply to Tuomas Hietala from comment #0) 
> In LO, it appears to be related to the readings of Japanese kanji. In
> English, the readings of kanji are called just "readings", though:
> https://en.wikipedia.org/wiki/Kanji#Readings
> I suggest that "phonetic reading" should be changed to "reading", unless it
> for some reason refers to e.g. on'yomi specifically (as opposed to
> kun'yomi), in which case it would be better to change it to "on'yomi".

I'm wondering if it should be kept generic, e.g. using the term "pronunciation", as users might use the feature for other languages than Japanese.

(I have no first-hand knowledge of CJK languages so would refer to the language communities here.)