-
-
Notifications
You must be signed in to change notification settings - Fork 919
Allow elongation dependent cultural names #4371
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
Conversation
Great PR! Please pay attention to the following items before merging: Files matching
Files matching
Files matching
This is an automatically generated QA checklist based on modified files. |
Hello @gzotti! Thank you for proposing of the feature. |
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.
Good idea, but I don't like using identical code in 2 places without re-use (computation the elongation along ecliptic) - IMHO this code should be moved in separate method and use in getInfoStringEloPhase() and getCultureLabels() methods.
The second problem - what will see observer on the Moon or on the Mars?
+1 on code reuse. (There are many other places to do that...) |
"visible":"morning"|"evening" is best IMHO |
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.
Thanks! It’s OK for me, but please check list of names for inner planets in SC
I am just about to change/add a few entries, but some are incomplete/inconsistent. |
And grmbl, Notepad++ fails to delete parts of Arab (RTL) strings properly. |
- name Morning Star and Evening Star
b1008ff
to
8128443
Compare
…e existing descriptions - not sure about anutan.
8128443
to
1347031
Compare
I know, you merged it already, I like the new feature Question:
I'm just asking - either way, it should be mentioned/ explained in the SUG (to be reworked later as you state above). |
The actual names are written in index.json. Venus is clear. For Mercury, I am not aware about a dedicated name currently usable for the modern SC, but I can imagine other SCs could have it, so the technology is here. Elongation-dependent (actually, only separating east/west) names can actually be added to any planet, but won't make much sense. Not sure about other criteria, e.g. is a bright Mars in opposition, rivaling Jupiter, named different from a dimmer Mars anywhere? Such things could still be added later. People pointing at Jupiter and naming it Evening Star should be instructed to not doing so. "The Evening Star" is Venus, and nothing else. A balloon is no airplane either, despite being "up there". The SUG instructs SC authors what to specify in the index.json. Maybe, in total, some more words can be provided about SC2.0 in the "Astronomical Concepts" chapter. But as you frequently say, who reads the dedicated Guide? |
Hello @gzotti! Please check the fresh version (development snapshot) of Stellarium: |
LOL aaha, good to know ... of course, I did that several times in astronomy lectures. Here, I referred to historical observations. If an ancient Babylonian wrote sth like this on a clay tablet, modern Assyriologists would think "ah, the term xxx can refer to both Venus and/or Jupiter".
|
You could just add some byname for |
Hello @gzotti! Please check the latest stable version of Stellarium: |
Name the Morning Star and Evening Star only if visible as such.
Description
This little branch provides an extension of the CulturalName, introducing the first "special" constants. More might come as needed.
The index.json NAME entry for planets can now be extended with an "elongation" tag which can be eastern or western.
In gthe code, this is translated to the Special constants Morning or Evening. I am not sure this is meaningful, maybe they should bear equal names. But also not sure which of the two is the better. opinions?
Fixes #4326
Screenshots (if appropriate):
Type of change
How Has This Been Tested?
Test Configuration:
Checklist: