Skip to content
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

TrackMate number parsing #22

Merged
merged 3 commits into from Jun 13, 2013
Merged

TrackMate number parsing #22

merged 3 commits into from Jun 13, 2013

Conversation

ctrueden
Copy link
Member

This branch is an attempted fix for an issue reported on fiji-devel.

It also fixes some dependency problems with TrackMate's POM.

Could someone with a non-US locale please test? Ideally, someone who uses commas as the decimal separator for numbers... Thanks!

This class allows for worldwide parsing of numbers by respecting the
current Locale, unlike Integer.parseInt, Double.parseDouble, etc.

For details, see e.g.:
http://www.ibm.com/developerworks/java/library/j-numberformat/
Many of these worked by accident. The version of other sc.fiji projects
should be ${project.parent.version}, while the version of ImgLib2
dependencies should be ${imglib2.version}. Using ${imagej.version}
happened to work for now, since it is also at 2.0.0-SNAPSHOT here, but
the latest pom-scijava fixes version properties to release versions, and
the version numbers will inevitably diverge over time.
This makes number parsing sensitive to the current locale, which should
allow numbers written with the expected local format to be parsed.
tinevez added a commit that referenced this pull request Jun 13, 2013
TrackMate number parsing
This merge result will be then uploaded to the update site, and left there for testing.
@tinevez tinevez merged commit c134da2 into master Jun 13, 2013
@ctrueden ctrueden deleted the number-parsing branch November 27, 2013 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants