Converter - cosmopolitans of the world, unite!
Twitter
Converter: Home Installation Feedback Release notes Examples Premium version

ConvertMyCurrency: Home News
Commercial support for Converter was discontinued; this is now an open-source project. If you're a developer, and you're interested to join this project, please hop over to the project's GitHub repository.
We can check your plugins and stuff

New features

WARNING! Do not convert this page until you've read what you're interested in—most of the explanations will be messed up and they will become very hard to follow!

Version browser
Older version: 0.8.6
Newer version: 0.9.3

New features in Converter 0.9.0

This release contains several improvements, mostly by popular demand, plus some fixes of all kinds.

Type Feature Example Comment
bug fix Fixed number parsing for currency conversions
  • £16.01
  • £17.95
  • HKD 10,369,668
The examples were improperly converted (various problems related to the values themselves). Thank you LD, Ndi, and indyhsu for reporting these bugs.
improvement hardening n/a The Converter used to process fractions by evaluating them as JavaScript code. This was a minor security risk, since the evaluated string was already matched against regular expressions. But even filtered, evaluating untrusted strings in JavaScript is potentially dangerous, so I decided to switch to a safer approach: the Converter is now 100% eval()-free. Thank you AMO team for highlighting this issue (they implement an automated tool which tests for this a while back).
new preference One way conversion
  • 1 cm
  • 1 inch
The measurements in the example would both have been converted in previous versions of the Converter, regardless of your preferences. Now only the one in unfamiliar units will be converted (i.e. if you prefer Imperial, only "1 cm" will be converted; if you prefer metric, only "1 inch" will be converted). You can disable this feature from the preferences, by unchecking "Only convert unfamiliar units". This was requested by several people.
new preference Hide measurement confirmations 1/10 cm By default, full page conversion of the measurement in the example would result in "1/10 cm (0.1 cm = 0.0394 in)". Starting with this version you can enable preference "Don't confirm the value being converted" in order to hide Converter's confirmation of the measurement -- the example would be converted like this: "1/10 cm (0.0394 in)".

The next feature is related.

While I don't think this is a good idea because of known limitations of any contextual converter, I have implemented it because of popular demand. You will also be warned within the preferences window itself upon enabling this preference.

new preference Hide original measurement 1/10 cm By default, full page conversion of the measurement in the example would result in "1/10 cm (0.1 cm = 0.0394 in)". Starting with this version you can enable preference "Replace original text" in order to hide the original measurement -- the example would be converted like this: "0.1 cm = 0.0394 in".

By enabling both this preference and the one above you end up with blind conversions, which simply replace the original text with the converted value.

While I don't think this is a good idea because of known limitations of any contextual converter, I have implemented it because of popular demand. You will also be warned within the preferences window itself upon enabling this preference.

UI improvement Contextual info messages in preferences n/a Some of the preferences are inter-dependent, and some are unsafe, so I added a contextual information system in order to warn users about these issues as they experiment with the preferences.
bug fix Fixed adjusters for negative values
  • -10 metres
  • -10 feet

For some strange reason, nobody noticed that many negative measurements were being adjusted in a completely nonsensical manner: -10 metres was converted to -394 mil, and -10 feet to -3,048,000 metres.

This was caused by such a rookie programming mistake that I feel quite silly now that I admitted it. I was simply testing if the values were low enough to adjust them to smaller units – e.g. if a value in metres is smaller than 0.1, convert it to centimetres, and so on. Obviously, negative values are always smaller than 0.1, no matter how big they are in the negative. Yes, quite a silly one indeed. Anyway, now it's fixed.

bug fix Fixed page restore bug
  • 1 m
  • 2 m
Some very specific conditions (replicated in this example) used to cause the Converter to fail restoring certain elements in a page when that was requested. In this example, the "1 m" conversion would have been restored, but the "2 m" conversion wouldn't have been. Repeatedly converting and restoring a page containing such elements used to result in horrendously repetitive conversions; pure ugliness ensued. Not any more.
capability New format
  • 2008-11-04 17:41:51 (UTC+0)
  • 17:41:51 (UTC+2)
  • 17:41:51 UTC+5
  • 17:41:51 (GMT+8)
  • 17:41:51 (GMT-10)

None of these formats were recognized by previous versions of the Converter. Now they are.

This "only" took one year to implement, thanks justmyview for reporting it.

minor capability Currency support 200 RSD Serbian dinars now converted to/from. Thanks Marko for pointing this out.
minor improvement minor internal streamlining n/a Further streamlined a couple of features in the Converter. This doesn't affect end users in any significant way, it's mostly related only to code internals.
compatibility tested with Firefox 3.6b2 n/a As such, bumped compatibility to FF 3.6.* (the Converter contains a lot of logic, but features virtually no fanciness, so it only depends on a few core features in Firefox; those are quite unlikely to change during the 3.6 series).