Giter Club home page Giter Club logo

stardroid's Introduction

Sky Map Build Status

Code Quality: Java Total Alerts

This is the source repository for Sky Map. You can find it in the Google Play Store and on F-Droid.

Buy Me A Coffee

Sky Map is free - there is no charge, no ads and we don't sell your data. However, some folks have asked if they can contribute in some small way so if you'd like to you can buy us a coffee by clicking on the above link. This is in no way expected or required but if you insist, I'll take a cappuccino.

Building

You should see the following two directories:

  • app: Application source
  • tools: Source for generating binary data used by the app.

To build SkyMap, you can use Android Developer Studio or Gradle. Begin by creating a local.properties file containing the location of your Android installation:

sdk.dir=<path to your SDK>

Android Developer Studio can create this for you. You can regenerate the datafiles and rebuild everything with the build_skymap.sh script:

./build_skymap.sh

(or its f-droid equivalent).

If you just want to quickly regenerate an apk please see the following instructions (note: assembleRelease won't work because the f-droid flavor needs some tweaking which is done by the shell script - so make sure you build the Gms flavor specifically).

Building a debug apk

From the root directory execute

./gradlew assembleGmsDebug

The apk can be found in app/build/outputs/apk/.

Building a release apk

(Sky Map team only)

Create a file in the app directory called no-checkin.properties with appropriate values for the keys store-pwd= key-pwd= analytics-key=

and overwrite google-services.json with the correct file.

From the root directory execute

./gradlew assembleGms

or

./gradlew assembleGmsRelease

The apk can be found in app/build/outputs/apk/.

Running tests

Unit tests:

./gradlew test

Connected device/emulator required tests:

./gradlew app:connectedAndroidTest

Code and Language Contributions

Yes, we know that Sky Map's code and UX is very dated. It needs a big overhaul.

In general, bug fix contributions are welcome, for example, simple one file fixes or dependency version upgrades. We're particularly grateful for fixed or new translations since as the app is developed we lose the 100% coverage of non-English languages that we once had.

However, please email us (or file a feature request) first before embarking on any major changes or feature additions. We may have a different vision for the direction of the app and it would be a pity to do work that we can't accept and would be wasted.

It is likely we'll be slow to respond to emails and PR requests. Depending on what else is going on it might be days, it might be months. I do apologize for that - life is busy. Sometimes the reply might be simply to point you at this documentation, which will seem very ungrateful and unfriendly. Again, I apologize, but it's the only way to keep up with the emails.

Small, focussed PRs to fix bugs or upgrade dependencies etc are very easy for us to approve. If your PR does too much it might get stalled because even if 90% of it is welcome there might be 10% that we're not happy with. So keep them small if you can. Plus, we'll be able to review them faster.

Thanks for your contributions! They're definitely appreciated even if our slowness to respond might make it seem otherwise.

Coding Style

We follow the Google style guide (or try to). We wrap at 100 chars and we do not use the common Android style of prefixing member variables with a 'm'.

stardroid's People

Contributors

07pepa avatar aayushsingla avatar aga-c avatar alexlitvino avatar argrath avatar barbeau avatar brchiu avatar cymrodor avatar flippinger avatar ftno avatar ftsamis avatar jaydeetay avatar jddeep avatar jonaheschwartz avatar jspricke avatar kevinserafini avatar lukyanov03851 avatar makhanovable avatar mmw125 avatar mouuff avatar shivamarora avatar srcemre avatar szpak avatar tacothedank avatar tricao avatar utkarsh530 avatar vasiliskos avatar vegadark avatar vikaspandey121 avatar xcorail avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

stardroid's Issues

Can't find constellations using English names in translated versions of Sky Map

What steps will reproduce the problem?
1. Install Sky Map on a device where the current language is not English  and 
for which there is a Sky Map translation available (e.g. Dutch)
2. Search for a constellation using its commonly known name (e.g.Sagittarius)
3. You get back 'No results found'

What is the expected output? What do you see instead?

You expect it to find the constellation. If you search for it using its Dutch 
name (Boogschutter), it finds the constellation (and Sagittarius is displayed 
in brackets after Boogschutter!!)

What version of the product are you using? On what operating system?
Google Sky Map version 1.6.4
Android 4.4.4



Original issue reported on code.google.com by [email protected] on 30 Jul 2014 at 11:31

Auto mode stopped working on Moto E, since the March 8 update

Device

OS

Android 5.0.2

Issue description

After today's update the Auto Mode of the application stopped working. On startup an error message appears, informing me that my device is lacking one of the 2 necessary sensors, and when I enter the app I can only use it in Manual Mode.

Expected behaviour

Up until now I was able to use both offered Modes on my device, so I would expect that I would still be able to use Auto Mode.

Assertion failed at testPositions (RaDecTest.java)

When running tests, both on Eclipse or on terminal, the testPositions test at 
RaDecTest.java yields an AssertionFailedError.

Here's the trace:
junit.framework.AssertionFailedError: expected:<173.25> but 
was:<172.99676513671875>
at 
com.google.android.stardroid.test.units.RaDecTest.testPositions(RaDecTest.java:7
7)
at java.lang.reflect.Method.invokeNative(Native Method)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154)
at 
android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:52
0)
at 
android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1447)

I tried to correct it, but I can't understand what the problem really is, since 
it is related to the planet's position.

Thanks for your help!


Original issue reported on code.google.com by [email protected] on 24 Apr 2013 at 10:11

Inconsistent Certificates

If target device has Google Sky Map installed, ADB will fail to install 
Stardroid APK because of a INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES error.

Workaround is to uninstall Google Sky Map, however the Market will think that 
Google Sky Map is installed once the Stardroid APK is uploaded to the target 
device.

Didn't know if this should be changed in the source tree, or if it should be 
left as an exercise for the user?

Compiling with:
  -IntelliJ IDEA 11.0.1
  -Android 2.3.3 platform
  -JDK 1.6.0_29
  -stardroid-read-only SVN source from 1/20/2012

Original issue reported on code.google.com by [email protected] on 30 Jan 2012 at 4:03

Search icon is almost impossible to see on Sony Xperia m2

User reported.

"No es difícil de ver el simpático botón sencillamente es imposible de ver. Al pulsar donde tu indicas si aparece la opción de búsqueda. Para mi es un fallo que creo deberían subsanar en posteriores actualizaciones.
Agradezco su ayuda.
Saludos cordiales "
oie_lzzfjokhbhyz

Pink boxes

Just upgraded to the 1.8 through Google Play. But I see a lot of pink boxes, I assume wrongly rendered names of constellations.

Nexus 5 (original) with Android 6.0.1

I
screenshot_20160301-095922

The new dialog fragments are causing crashes.

java.lang.RuntimeException: Unable to resume activity {com.google.android.stardroid/com.google.android.stardroid.activities.SplashScreenActivity}: java.lang.IllegalStateException: Fragment already added: EulaDialogFragment{3a6b5321 #0 Eula Dialog}
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3028)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3063)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1361)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5343)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:905)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:700)
Caused by: java.lang.IllegalStateException: Fragment already added: EulaDialogFragment{3a6b5321 #0 Eula Dialog}
at android.app.FragmentManagerImpl.addFragment(FragmentManager.java:1138)
at android.app.BackStackRecord.run(BackStackRecord.java:757)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1454)
at android.app.Activity.performResume(Activity.java:6107)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3011)
... 9 more

Add ISS to list of objects

I would like to be able to track the ISS using this application. Given that the 
moon exits, I take it is possible to add earth-orbiting stellar objects to the 
list of objects in the app.

Original issue reported on code.google.com by [email protected] on 15 Aug 2013 at 7:50

Check position against horizon

Not really an issue, sorry, but you might be able to help anyway.

What i'm trying to achieve is to check whether an object is above or below the 
horizon.

But i'm totally stuck here... How am i supposed to get the "position" of the 
horizon?

Goddchen

Original issue reported on code.google.com by [email protected] on 31 Jan 2012 at 10:08

Wrong search direction when changing date

Hi there,
if I change the date (both in the past or the future), search for a planet, 
then get back to current date, search directions get wrong

To reproduce:
1. Use the time machine to select a date (in the past or the future, it's the 
same outcome)
2. Search for an object (I searched Mars). The directions are right
3. Set back the time to "now"
4. The circle is still present, but following the directions will bring 
nowhere. Additionally, when approaching the supposed target, the arrow changes 
direction.

I'm running version 1.6.4 on a HTC Desire S phone

Original issue reported on code.google.com by ilpelle on 29 Feb 2012 at 9:53

Missing constellation names

https://github.com/sky-map-team/stardroid/blame/master/tools/data/constellation_names_and_lines.kml

There are a lot more constellation names here than we write into the app. Probably a regression from 1.6.4 as some users are reporting it.

The original file imported to github also had limited constellation names:
https://github.com/sky-map-team/stardroid/blob/e3226379853880830b988508f0287f9bf043453f/tools/src/com/google/android/stardroid/data/constellations_R.ascii

but there's no telling what was actually in the 1.6.4 binary.

Improve Location setting dialog

It's currently a confusing mess. If you enter a place name AND a lat long, which wins? What happens when there's no network (answer: geocoding fails and you have to use numeric lat/long). Why Pisa? (A: it was a reference to Galileo - surely we can do better now).

Would be nice to show where it thinks you are on a map and maybe even offer the user the chance to move the pin if they don't happen to know their lat long off by heart.

Also...if the GPS is present we should just use it.

View is not smooth (but shaking left and right)

What steps will reproduce the problem?
1. Enable auto mode to use compass and accelerometer
2. Position the phone to point directly east (or west)
3. Slowly move the phone straightly up toward Zenith (you can also put it on a 
table in landscape mode when moving to make sure your hands are not shaking)

What is the expected output? What do you see instead?

I expect to see smooth upward moving of the map. Instead of that I am getting 
upward movement + some small left and right shaking. 
The issue is not present if I am doing the same thing while looking north or 
south.

What version of the product are you using? On what operating system?

I am using the latest version from the source repository, revision 7.

Please provide any additional information below.

The current location does not seem to matter, I tried to manually set 0 
latitude and 0 longitude and the issue is still present. 
The issue also reproduces if you are looking east (or west) an go down towards 
Nadir in a straight line. But is OK with north and south.

Any idea were this shaking might come from?

I was able to reproduce this on a HTC Nexus One and a Samsung Galaxy S1.

Best regards,
Cristian

Original issue reported on code.google.com by [email protected] on 16 Aug 2012 at 3:16

Use Gyroscope when available

This is more of an enhancement request :) It would be nice if somebody could 
work on improving tracking by using the gyroscope in devices where it's 
available or a more complicated predictive filter (Kalman?)


Original issue reported on code.google.com by [email protected] on 24 Jan 2012 at 4:40

Option to disable sensor-tracking

On my tablet the (north-south-) orientation sensor does not seem to work very 
well, independent from the direction I move the tablet to, the displayed star 
map does not change. Moving it up and down works. Means I always look to north, 
also when I rotate the tablet.

So I'd like to see an option where the sensor can be disabled completely and 
the user is able to move the displayed star map by dragging it manually.

Beside the effect that the ap could be used with some devices that have 
problems with the sensor, it would be easier to just to deposit the table 
without losing the current view (useful when one wants to have a look into the 
telescope in between).

Original issue reported on code.google.com by [email protected] on 26 May 2015 at 6:34

Someone's been using vim

In the provider/ephemeris folder there's file called :wq
Just mentioning it to keep things tidy.

Regards

Original issue reported on code.google.com by [email protected] on 21 Jan 2012 at 12:36

Transition project to Git/Github

I believe two major issues are holding back the advancement of this app by 
others in the community:

1.  SVN versioning - not very friendly to collaborative work.  Patch submission 
review process is time consuming.
2.  Lack of social integration / loose coupling with various forks of the 
project - again, not easy to review / merge patches upstream given SVN and the 
current hosting on Google Code.  Also, not easy for one fork to merge 
changes/improvements from other forks, both because of SVN, and because if 
someone transitioned the project to Git, the repos aren't likely to have the 
same history.  As a result everyone starts from scratch when trying to update 
this project.

I think transitioning to Git and hosting the project on Github would help solve 
both of the above problems.  It would give the community a solid root project 
to fork and expand upon, and would also make it simpler (for both the current 
project maintainers and contributors) to submit improvements back upstream to 
this main project, and for one fork to merge improvements from other forks.

I've helped transition a few projects from SVN to Git/Github (including 
retaining the history), and I'd be willing to help with this process if needed.

Original issue reported on code.google.com by [email protected] on 23 Jan 2015 at 10:59

Wrong search box size

What steps will reproduce the problem?
1. Click on the search option
2. Start to type what you want to search

What is the expected output? What do you see instead?

A search box with a reasonable size and results that we could be possible to 
read.

What I see is a really small search box (where nothing that I type can be 
viewed) and a very small suggestion list below (that I also can't read).
See the attached screenshot for a search after typing "es"

What version of the product are you using? On what operating system?

Version 1.6.4
Android version is 4.0.4

Original issue reported on code.google.com by [email protected] on 2 Sep 2012 at 8:15

Attachments:

Enhancement request: Fixing horizon during manual-mode time travel

(This is my first post to code.google - please let me know if there is a better 
place to talk about these)

During time-travel in manual-mode, it is useful to fix the horizon and let the 
stars (and others) move in the background. This gives me an idea of what to 
expect(over time)in a certain section of the sky from where I am currently 
stationed.

I have made a very small change - locally - to AstronomerModelImpl for this 
feature and is working neatly. Also added a toggle for this feature in the 
menus.

P.S: I have a few other such code changes and enhancement requests - but I am 
not sure what the exact process is for getting these changes reviewed and 
submitting them. Could the project owners or someone else provide some 
direction?

Thanks!

Original issue reported on code.google.com by [email protected] on 1 Feb 2012 at 4:29

Map layer does not show on some devices

User reported. Map appears and then vanishes. Regular widgets show normally.

Phone: Droid RAZR HD
Android version: 4.2.2
Skymap version: 1.8.0

Perhaps related to the map not showing on the emulator?

Weird app/res/values/strings.xml issue

With the current code, everything works after building with ant clean debug.

But if I make two additions to app/res/values/strings.xml, something gets 
weirdly corrupted.

Specifically, I added license and license_title test strings close to the 
beginning as follows:


    <string name="app_name" translation_description="Application Title">Sky Map</string>
    <string name="license_title">This is a
quick test</string>
    <string name="license">This is a quick test
license</string>
    <string name="menu_settings">Settings</string>


Then some of the app data gets corrupted.  One example problem can be seen as 
follows: Menu | Gallery | Omega Centauri | Find in sky.  Result: not found!  
(In other testing, I had other results, such as its showing Omega Centauri in 
the wrong part of the sky, near the Big Dipper.)


I don't know if it's some subtle bug somewhere in the code, or something wrong 
with my build environment.

Original issue reported on code.google.com by arpruss on 22 Jan 2012 at 7:07

Attachments:

Constants are being modified

When ApplicationConstants.INITIAL_SOUTH and INITIAL_DOWN are being assigned to 
variables, this leads to these constants getting modified by the code.  
Wherever the constants are assigned to variables, there needs to be a .copy().

Original issue reported on code.google.com by arpruss on 23 Oct 2013 at 11:25

Declare android:required="false" for android.hardware.location.gps feature

This is a feature request from an OEM who ships non-GPS Android device.

Sky Map uses ACCESS_FINE_LOCATION permission and it implies 
android.hardware.location.gps feature.
Thus this app is not shown in Android Market on their device because of Market 
feature filtering.
http://developer.android.com/guide/topics/manifest/uses-feature-element.html#per
missions

They want us to set android:required="false" so user can download the app from 
Android Market.

Original issue reported on code.google.com by [email protected] on 24 Jan 2012 at 12:29

Feature request: add option for devices without compass

I really love SkyMap. Thanks to the developers for developing such a nice app.

This is no bug but a feature request. At the moment SkyMap can be used on 
devices without compass only in manual mode. In auto mode changing the back 
azimuth is not possible.

Still the acceleration sensor should provide enough information to align the 
screen to the pointing direction, even without compass. It just has to be 
aligned once which could be done in the manual mode. It would be nice if there 
was an option to enable such a feature. This option could also be automatically 
enabled if no compass is detected.

If you think this is not feasible feel free to close the request.

Original issue reported on code.google.com by [email protected] on 23 Oct 2013 at 1:31

Occasional crashes on the touch screen on Galaxy phones

java.lang.IllegalArgumentException: pointerIndex out of range
at android.view.MotionEvent.nativeGetAxisValue(Native Method)
at android.view.MotionEvent.getX(MotionEvent.java:2179)
at com.google.android.stardroid.touch.DragRotateZoomGestureDetector.onTouchEvent(DragRotateZoomGestureDetector.java:109)
at com.google.android.stardroid.activities.DynamicStarMapActivity.onTouchEvent(DynamicStarMapActivity.java:539)
at android.app.Activity.dispatchTouchEvent(Activity.java:2997)
at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:2708)
at android.view.View.dispatchPointerEvent(View.java:9358)
at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:5043)
at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:4873)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4336)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:4389)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:4355)
at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:4481)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:4363)
at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:4538)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4336)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:4389)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:4355)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:4363)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4336)
at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:6939)
at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:6812)
at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:6783)
at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:7029)
at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:185)
at android.view.InputEventReceiver.nativeConsumeBatchedInputEvents(Native Method)
at android.view.InputEventReceiver.consumeBatchedInputEvents(InputEventReceiver.java:176)
at android.view.ViewRootImpl.doConsumeBatchedInput(ViewRootImpl.java:7000)
at android.view.ViewRootImpl$ConsumeBatchedInputRunnable.run(ViewRootImpl.java:7052)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:777)
at android.view.Choreographer.doCallbacks(Choreographer.java:590)
at android.view.Choreographer.doFrame(Choreographer.java:558)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:763)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:6897)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1404)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1199)

Missing possibility to listen to onClick events

Basically i am missing any helper functions that will map a touch event's 
coordinates to an actual object.
Or am i just missing something?

The best place to go for it should be DynamicStarMapActivity.onTouchEvent(...) 
to get the click coordinates and then find which object maps to the touch event 
coordinates in the skyView GLSurfaceView. But i'm just unable to find any 
functions that might help here.

Any ideas?

Greets

Original issue reported on code.google.com by [email protected] on 23 Jan 2012 at 10:03

Feature request: Telescope Interface

It would be great to have an interface to computerized telescopes such as Meade 
Autostar. Just long press an object and the telescope will slew like in 
Stellarium.

Is it possible? If yes:

Connection will be made via Bluetooth Serial-Port-Profile.

I'm new to Android-development and java in general, so i don't know exactly 
where to implement this feature, but I can test/debug with my telescope.

Original issue reported on code.google.com by [email protected] on 28 Feb 2012 at 5:05

No class "com.google.android.stardroid.R" in current source ?

What steps will reproduce the problem?
1.  Error when trying to build the source projet
2.  Message error "The import com.google.android.stardroid.R cannot be resolved"

What is the expected output? What do you see instead?
When trying to build the source project I got a message error when trying to 
import the class "com.google.android.stardroid.R"

What version of the product are you using? On what operating system?
android:versionCode="1112" android:versionName="1.6.4"

Please provide any additional information below.
I search through the project libraries and I didn't find the class 
"com.google.android.stardroid.R"

Original issue reported on code.google.com by [email protected] on 19 Nov 2012 at 9:32

Build fails - no-checkin.properties can't be found

If you clone this repo, and then try to run gradlew assembleDebug or gradlew clean, you'll get this error:

FAILURE: Build failed with an exception.

* Where:
Build file 'C:\Android_Studio\stardroid\app\build.gradle' line: 20

* What went wrong:
A problem occurred evaluating project ':app'.
> C:\Android_Studio\stardroid\app\no-checkin.properties (The system cannot find the file specified)

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

I'll submit a potential fix for this shortly.

Rigel in Centaurus should be Riger Kenttaurus

What steps will reproduce the problem?
1. Menu > Search > Centaurus
2. Go to Centaurus, you will find Rigel in Centaurus
3.

What is the expected output? What do you see instead?
The Rigel should be Riger Kenttaurus or Alpha Centauri

What version of the product are you using? On what operating system?
1.6.4

Please provide any additional information below.
The Chinese name is "南门二"

Original issue reported on code.google.com by [email protected] on 19 Sep 2012 at 9:08

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.