Converter - cosmopolitans of the world, unite!
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.5.5
Newer version: 0.6.1

New features in Converter 0.6.0

This version features several improvements over the previous one, and a few relatively important bug fixes.

Type Feature Example Comment
improvement Busy cursor n/a

The cursor is now changed to the system "busy" cursor (usually an hourglass) during full page conversions.

As a result, if the Converter breaks during a full page conversion, you'll end up with a perpetual hourglass cursor. If that ever happens after a full page conversion, please make sure to give me some feedback!

For some unknown reason, converting this entire page just after installing or upgrading to version 0.6.0 is known to sometimes result in a permanent "busy" cursor as described above. Restarting Firefox and trying exactly the same thing again on this same page works as expected, and all further conversions also work as expected.

feature Status bar icon n/a

Any page can now be converted by clicking the Converter icon in the status bar.


  1. The Converter doesn't feature two icons ("page not converted" and "page already converted") because of Firefox's limitations in handling tabs (it would be feasible and reliable for distinct browser windows, but switching tabs doesn't trigger any code execution).
    Of course, that's limited to my knowledge right now.
  2. Clicking on the Converter icon multiple times does not result in multiple page conversions — unfortunately there's no visual cue to that effect, on account of the previous point.
capability Timezone conversions
  • 10:30 GMT
  • 10:30 CET
  • 10:30 AM PDT
  • 10:30 +0800
Timezones are now converted, as long as they are specified explicitly in any of the formats shown in the examples. There are a few important things to remember about timezone conversions:
  1. THIS FIRST POINT IS PARTICULARLY SIGNIFICANT if you intend to rely on the Converter for important timezone conversions!

    Daylight saving time (DST) is taken at face value. This may not be always desirable, but the Converter has no choice.

    For instance, if you're looking at the schedule of a repetitive event — say, the time when people come to work in an Austrian company — you might encounter "9:00 AM CET". But if Austria is on DST at the time when you're reading that information, you would assume that the employees come in at 9:00 AM CEST instead of CET — i.e. the local 9:00 AM in Austria. The Converter does not make that assumption — it converts 9:00 AM CET to your current local time, regardless of whether Austria is or you are using DST locally right now.

    In other words, the Converter takes your current DST into consideration, but discards the DST or lack thereof in the remote timezone at the time of the conversion — it just uses whatever remote timezone it sees on the page being converted, and converts it to your current local time.

    Please note that all timezone conversions are accurate to the best of my knowledge — this caveat is related to expectations and assumptions, not to inaccuracies in the conversion per se.

  2. The format is pretty rigid — no conversion will be performed if the time is formatted like this for instance: 10:30 (UTC+2). I do intend to address this, but I need your feedback — please use the Feedback page when you want to suggest new formats.
  3. Your local timezone is read from your system settings. If you didn't set it properly, the conversion will be inaccurate.
  4. When converting 1:00 AM GMT to any American timezone, the resulting time will fall in the previous day. The Converter represents that by showing the resulting time in the following format: "hh:mm/-1". Similarly, times which end on the next day are converted like this: "hh:mm/+1". Obviously, all timezone combinations which result in converted times falling in another day employ the same format.
  5. No timezone conversion is performed for timezones which match your own. If that's the case, only 12h/24h conversions are made (for more on the 12h/24h conversion preferences, see the relevant section below).
feature Preferences system n/a

The preferences system has finally been implemented. In this version, the only preference you can set is whether you like times to be shown as 12h or 24h (1:00 PM vs. 13:00). The default is 24h (13:00), for a single reason: that's my personal preference. :-)

There are two advantages to be had with this new feature:

  1. No conversion is performed if the time is already formatted to your preference.
  2. Timezone conversions are always made in your preferred format, regardless of what the original format was.
bug fix Fixed false negatives
  • <10 °C>
  • 10 °F-quite something
  • >10 °C<
  • 10 °F: quite something
All measurements followed by the punctuation signs in the example were not properly converted in version 0.5.5 — they are now.
improvement Major performance optimization n/a Full-page conversions are now performed much, much faster.
bug fix Notifications in tabs n/a

The old installation/upgrade notification dialogs led to the project's homepage in the main window of the browser. That was the least intrusive way I could find1. Unfortunately that didn't work for everyone, for unknown reasons2, and my decision to avoid opening new tabs ended up harming this extension's user rating on a site that matters3.

1: I tried my best to find a way of ensuring that users see the page they want to while avoiding to open new windows or tabs. As far as I know, there is no reliable way of doing that in Firefox.

2: I know that it didn't work for some people, but I don't know why — that's because nobody files any bug reports, you people just complain passively, withot giving me any option to follow up. By all means, do prove me wrong by using the feedback form on the homepage when you encounter bugs!


capability New formats supported
  • 10° C
  • 10° F
  • 10º C
  • 10º F
The first two examples show new formats (XX[degrees][space][C/F]); the last two examples show a new character for "degrees" (yes, they are different from the first two examples, believe it or not!)
improvement Time supports seconds
  • 13:33:33
  • 1:33:33 PM
  • 13:33:33 UTC
  • 1:33:33 PM UTC
  • 13:33:33 PST
  • 1:33:33 PM PST
  • 13:33:33 +1100
  • 1:33:33 PM +1100
  • 13:33:33 -1100
  • 1:33:33 PM -1100
All time formats for all conversions support seconds, as per the example.