-
-
Notifications
You must be signed in to change notification settings - Fork 875
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
Use real native Chinese names in SC index.json #4196
Conversation
updated "pronounce" variable in the remaining half - needs to be filled with characters
@sunshuwei You may want to review this too. |
Great PR! Please pay attention to the following items before merging: Files matching
This is an automatically generated QA checklist based on modified files. |
b1687a8
to
81c3d3d
Compare
Not being an expert on pinyin. Do we have diacritics in one, and non-diacritics in the other SC, or do we have unhealthy mixes now? |
We have diacritics in some names of the same SC (DSO, stars) and no diacritics in others (constellations, planets). So I'd call it an unhealthy mix. |
The diacritical mark is used to distinguish tones. In the Pinyin standard, as a transliterated vocabulary, it does not have diacritical marks, but as a strict phonetic notation, it has diacritical marks. |
This would be great. Yes, the project and data options have grown a lot. Ruslan and Fabien started using JSON with Stellarium-mobile years ago and added the "pronounce" key, while I had expected or preferred a "transliteration" key, while for "pronounce" I would have expected IPA annotation. There are other cases where both transliteration and pronounce and even IPA would be great. I know for Tibetan, scientists use Wylie which is not really a pronunciation help, and there is a pinyin for Tibetan as well. So, in the end we may fill tags "pronunciation" (for Chinese: "pinyin with diacritics"), transliteration (pinyin without), and "IPA" for international phonetic alphabet, if anyone can add that correctly. But these tags will not be used in 25.1 now. If you can later help filling the gaps, it would be welcome. |
What about |
Yes, sure. native=Chinese glyphs, pronunciate=pinyin (cannot say which flavour is best, but please consistent), english=translation. I understand there are less glyphs in use, but this is for SC authors to fill. |
{"english": "Tiāndàjiāngjūn zēng V", "references": [1], "translators_comments": "Pinyin transliteration"}], | ||
"HIP 9589": [{"english": "Circular Celestial Granary Added IV", "references": [1]}, | ||
"HIP 9589": [{"english": "Circular Celestial Granary Added IV", "native": "天囷增四", "references": [1]}, | ||
{"english": "Tiānqūn zēng IV", "references": [1], "translators_comments": "Pinyin transliteration"}], |
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.
Just any random pick here: The "english" entry should be the translated only. The other "english" entry which is now filled with pinyin should be renamed "pronounce".
"M 44": [{"english": "Jishiqi / Cumulative Corpse Gas"}], | ||
"M 45": [{"english": "Maotou / Ancient Flag with Yak's Tail"}], | ||
"M 7": [{"english": "Yu / Fish"}], | ||
"HIP 746": [{"english": "Wangliang/Wang Liang", "native": "王良"}, |
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 this list, obviously, the pronounce entries in pinyin are missing.
@10110111 What happens if there are two english entries in a star entry? One is the translation, the other pinyin. (should be renamed to pronounce, obviously) Random pick, or are they combined, or does the second overwrite the first? |
It's not portable, lets note this first. Qt doesn't seem to document its own behavior on which entry it picks either. This only works for our comments because we never pick them. |
OK, I have fixed the medieval. The Chinese has over 3000 star entries like
that need to be reformatted into
A few stars have double naming. Sorry, I am not touching this file. Experts please! @sunshuwei ? |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
2aa6213
to
3a3e181
Compare
Conflicts have been resolved. A maintainer will review the pull request shortly. |
This is a result of fetching all the constellation names from
constellation_names.zh_CN.fab
intoindex.json
, yielding native names made of hieroglyphs and "pronounce" entries made of (diacriticless) pinyin.