Thread: [Celestia-developers] Multiple names for solar system bodies
Real-time 3D visualization of space
Status: Beta
Brought to you by:
cjlaurel
From: Chris L. <cl...@gm...> - 2008-07-16 23:44:31
|
The following patch will allow you to specify multiple names for solar system bodies in an ssc file: http://www.shatters.net/~claurel/celestia/files/patches/multiname/multiname.patch As for stars and deep sky objects, the names are separated by colons. For example: "Makemake:2005 FY9" { ... } As suggested by my example, one important use for multiple names is to allow listing both the provisional and official designations of an object. This can prevent cel: URLs referring to an object from becoming out of date when an official designation is assigned. Another usage is giving allowing minor planets to be identified by a name prefixed with a minor planet number: "4 Vesta:Vesta" { ... } The first name in the list is treated somewhat specially: - It is the only name that will be localized (is this a problem?) - It is the name that is shown in the solar system browser - The label shown for the object in the 3D window will always be the first name It is not possible to change the names of an object with Replace and Modify. The name list given in the first definition of the object is permanent. I don't see this as a significant restriction, and it avoids forcing the user to supply a complete name list when an object is Replaced or Modified. I think it is important to establish some conventions for minor planet names. One approach is to list the names in the order # name, name, provisional designation: "136472 Makemake:Makemake:2005 FY9" I've also seen the "(#) name" form used, but the parenthesis to me seem like just extra typing and clutter for the user. Any other suggestions for a standard minor planet naming scheme? Are there other considerations for multiple names that I've overlooked? --Chris |
From: Chris L. <cl...@gm...> - 2008-07-17 00:12:39
|
Thinking about this further... Maybe it's better to add a new field for ssc objects called MinorPlanetNumber: "Makemake:2005 FY9" { MinorPlanetNumber 136472 } Then, the SSC loader can automatically add the "# name" form as an alias for the object. It's more explicit, and gets around some minor i18n headaches, like the need to supply localized versions of both 'Ceres' and '1 Ceres'. --Chris On Wed, Jul 16, 2008 at 4:44 PM, Chris Laurel <cl...@gm...> wrote: > The following patch will allow you to specify multiple names for solar > system bodies in an ssc file: > http://www.shatters.net/~claurel/celestia/files/patches/multiname/multiname.patch > > As for stars and deep sky objects, the names are separated by colons. > For example: > > "Makemake:2005 FY9" > { > ... > } > > As suggested by my example, one important use for multiple names is to > allow listing both the provisional and official designations of an > object. This can prevent cel: URLs referring to an object from > becoming out of date when an official designation is assigned. Another > usage is giving allowing minor planets to be identified by a name > prefixed with a minor planet number: > > "4 Vesta:Vesta" > { > ... > } > > The first name in the list is treated somewhat specially: > - It is the only name that will be localized (is this a problem?) > - It is the name that is shown in the solar system browser > - The label shown for the object in the 3D window will always be the first name > > It is not possible to change the names of an object with Replace and > Modify. The name list given in the first definition of the object is > permanent. I don't see this as a significant restriction, and it > avoids forcing the user to supply a complete name list when an object > is Replaced or Modified. > > I think it is important to establish some conventions for minor planet > names. One approach is to list the names in the order # name, name, > provisional designation: > > "136472 Makemake:Makemake:2005 FY9" > > I've also seen the "(#) name" form used, but the parenthesis to me > seem like just extra typing and clutter for the user. Any other > suggestions for a standard minor planet naming scheme? Are there other > considerations for multiple names that I've overlooked? > > --Chris > |