Sky Culture Menu does not fit New Format

[sushoff]

OTHER QUESTIONS

• in the SC menu, we still have the labels "Abbreviated", "Native" and "Translated". We should rename "Abbreviated" as it really only fits the IAU-nomenclature. Any ideas? (perhaps "technical"?)
• Last week, we had a workshop here at Brown where we presented & group-discussed our ongoing work. The professors pointed out that the variable "pronounce" (which they happened to see in a code snippet) should not appear as such in the menu. As a variable, I like it because it is short - but, perhaps in the menu, we could call it "transliteration", as @gzotti frequently proposes?
• then the future variable "IPA" can only be called "IPA" and that's done

what do you think?

[alex-w]

in the SC menu, we still have the labels "Abbreviated", "Native" and "Translated". We should rename "Abbreviated" as it really only fits the IAU-nomenclature. Any ideas? (perhaps "technical"?)

Not only IAU-nomenclature, it just depending of author of SC - which unique identification he used for constellations. Please see Siberian SC as example.

Last week, we had a workshop here at Brown where we presented & group-discussed our ongoing work. The professors pointed out that the variable "pronounce" (which they happened to see in a code snippet) should not appear as such in the menu. As a variable, I like it because it is short - but, perhaps in the menu, we could call it "transliteration", as @gzotti frequently proposes?

Yes, it should be “Transliteration” in this menu, but at the moment this feature is not implemented yet (using transliteration data as extra data for names). It planned to release 25.2.

then the future variable "IPA" can only be called "IPA" and that's done

I’m not sure that we should show IPA on the screen

[alex-w]

Related PR #4179

[gzotti]

I am afraid the "pronounce" tag in the json is fixed in concrete, to remain compatible with s-web and s-mobile. IMHO it is a misnomer, but I accept the train has left with this one. All we can do is to explain it as clearly as possible that this is actually a Latin-letter based transliteration geared at english pronounciation which can in principle be further Transifex/.po-translated to user language. A different scientific transliteration can be added in "transliteration" tags. (Not yet used. My example: Wylie for Tibetan, which does not help pronounce, so here "pronounce" should show Tibetan-Pinyin... Maybe this second transliteration should not be translatable as it's expert knowledge best known by the original author.)

IPA: Like with so many other things, it depends on whether you know IPA (at least a bit) and want to see it. We need to see data filled by our SC authors (so that it pays off), and in the umpteen combination options of #4179 IPA will be available. What I have not seen yet is whether Noto font by default loads all available subfonts for whatever we want to show, like Sanskrit, Cuneiform or IPA.

Likewise, @10110111 long ago asked about the necessity of the "sky culture language". When we have more display options, this setting could also probably go away, together with the native planet names (which will be switched together with the rest). It is good that these kludges, which were required to circumvent limitations of the old formats, can then go away.

Yes, the 3-option switch will be extended in 25.2 by #4179, but we also need data for this. @10110111 made our first IPA entries days ago. My intention is to have separate "createScreenLabel()" and "createInfostringLabel()" methods which combine the data bits into user-selected combinations. The configurations must be stored SC-dependent, given completeness, data style and users' language skills. Abbreviated shows the shortest possible label. For modern SCs it's the IAU code, for other SCs it is whatever the SC author/last editor has chosen it to be. By pure misfortune, early authors chose to just enumerate them in a time when they were only used as non-displayed IDs. Whoever feels inclined to do so can surely improve that. The only point to be cautious may be when authors make a "single" SC right out of a book, and used book page references or other source links as IDs.

In the current state I see some pinyin with, some without diacritics. This should at some time (within this year I hope?) be harmonized, preferably with diacritics. Some Arab SCs shows Arab letters, but should also show "pronunciation" (i.e. English transliteration) as reading aid. And in general, the descriptions should be more engaging than some are now. I know, many authors are no longer available, but star lists in foreign names without any context are plainly boring. Authors should tell some interesting stories. The icon still shows the campfire...

Now I am trying to solve #4239 still today. After "reload", I still need to load another, then go back to see editing results.

[Atque]

Where are even these "pronounce" tags visible? I can't find them in the main program, despite many skycultures having them in their files.

[sushoff]

Where are even these "pronounce" tags visible? I can't find them in the main program, despite many skycultures having them in their files.

currently not in the desktop version - we're talking about something in the code (currently only an invisible name of a variable) and its display in future releases