Beschreibung

Obtain seamless and in-line currency conversion to your own configured currency from every web page you visit.

Configurable:1) Your own currency, to which the page values will be converted into2) Sites subject to extension intervention: all, only white listed, all but black listed3) Display appearance4) Exchange rate update interval

Known Issues:1) When the same text node has several currencies, only the first one is converted.

NOTES: a) Not tested in every web page. Some might work fully, some partially, some not at all. I will try to keep compatibility at all relevant pages whenever personally noticed or appointed to me.b) Not extensively tested with all combinations of pages, currencies, visualization options, refresh rates, etc. This is made available as is, and I will try to fix it whenever personally noticed or appointed to me.c) Exchange rates are acquired using Bloomberg's public information. Exchange rates are subject to the accurateness and update rates made available by it, and should therefore the results shown by this extension should serve only as an indicating result, and not a binding value, not replacing the eventual conversion rates used by each site.d) Only Euro (€), Pound (£), US Dollar ($) and Yen (¥) will be converted to your local currency.

Änderungsprotokoll

= v2.6 =a) Improved currency conversion in some situations where html code was not helpful.b) Fixed the drop-down list that was keeping the last currency match, instead of the one you actually chose (@joshjnz).c) White/Black list now support true wildcards (e.g.: *.com) addresses (@joshjnz).

= v2.5.1 = a) Small update to value fetching, which was not considering nodes whose text began with a line break.

= v2.2.1 =a) Fixed a regression introduced in the previous version that breaks the correction performed in =v2.0=d).

= v2.2 =a) Fixed an issue where some currency representation that would use different decimal separator would cause misread and faulty conversion (@crocuz)b) Changed decimal separator for JPY currency representationc) Changed JPY detection pattern for some more tolerance

= v2.1 =a) Now allows recognition of the currencies that have their symbol after the value, instead of before only (e.g. €50 and 50€).b) Changed currency detection patterns, fixing a common issue where only a part of the value would be fetched for conversion (@Vlad Shumkin, @Burov Dmitry, @lordkiller).c) Fixed an error where JPY currency symbol (￥) would show up with a code instead.d) Removed decimal part for when converting to JPY.e) Changed curency naming in options page for better reading.f) Extension is now more tolerant to currency representation that don't follow the defined pattern for decimal separator (e.g. €20.00 vs €20,00).g) Changed how thousands' groups are displayed. 10000 is now 10.000, for instance, for easier reading.h) Fixed some extension nomenclature.

= v2.0 =a) MAJOR: Changed currency provider from Google to Bloomberg, as many people could not find their own currency in the initial list. Over 200 worldwide currencies now available.b) Fixed a situation where the script would not work if the page loaded faster than the rates messages would travel internally inside the extension.c) Fixed an issue in pages where the DOMContentLoaded event would not be fired, it would not tigger the page parsing.d) Fixed mistakenly parsed foreign currencies that also used the $ for display, which were not USD, like the Brazilian's Real, R$. (@lordkiller)

= v1.2.1 =a) MAJOR: fixed the currency detector, namely for EURO currency, more flexible to allow different dispositions for display used by some sites, which was causing bad value fetching in previous versions.b) Fixed encoding for the options page, which was causing special characters to appear mistaken (@ilidiomartins).c) Fixed the description tag in the options page which showed too much unintended information.

Hello!Thanks for your comment.Rates are collected periodically from bloomberg (at http://www.bloomberg.com/js/calculators/currdata.js), so a "delay" or a "deviation" can be different depending on the source you are comparing with and its own "refresh" rate.

As far as I could research, the code for the "Deutsche Mark" is in fact DEM and not DM, which is its abbreviation. The euro is in place, so it should not matter that much.Positioning of the symbol is the todo list. Thank you!

Von fluidum:

14. April 2013

Nobody uses DEM though, all people use DM. Just add a different entry being called "German Mark (DM)" then everyone can choose.

Turkish lira is completely broken ($899.99 (TRL 1.630.367.547,10) is simply not true). Also, please don't show the abbreviations (or at least add the option to remove) of currencies which doesn't have symbols as it takes up unnecessary space and looks ugly.

Please, make a button, that would allow1) move current site (full domain match) to whitelist2) move current root site to white list (say, for domain xxx.yyyy.com -> *.yyy.com; for xxx.yyyy.co.uk -> *.yyy.co.uk)

I am personally against a button, since too many can clutter the button bar and become annoying... :) But maybe I can make it opt-in, which would make it acceptable.Then your points 1-4 become doable quickly. 5 seems less likely, and somewhat doable with 2 and 4. 6 would be doable with just a right click. I have some ideas that I would like to turn into extensions before fixing issues with old ones. But when I return to this, i'll actively consider your suggestion.Thank you!

Von the-arioch:

15. Juni 2012

About the bar, true. Opera cloned the Chrome for it. And while there were solutions how to move it to Status-bar for example, Opera did not do it. Pity.

Personally i think that bar should have perpendicular trays, so that icons whould be in 2D structure. MAybe one day we would see it.

But there should be some control, not just "somehting changed my page", that is i believe more important than cluttering (Afterall there are collapse/expend buttons for extensions bar)

Von the-arioch:

15. Juni 2012

5 is doable if to extend 1-4 to page-level granularity, but thatis an overkill.Frankly, i don't know what would make 5 undoable with direct naive approach.

You can use "New Romanian Leu (RON)".I will however plan to remove the "Romanian Leu (ROL)" and leave "New Romanian Leu (RON)" with the "New" removed. Would that be acceptable?Thank your for your feedback!

Von licaon:

10. Mai 2012

Oh, my bad, i did not see that you already had the New one in. Yes the old one is no longer in use for some time and it should be removed. 10q

Von licaon:

10. Mai 2012

And another thing can you move the code, see $X=XXRON so the RON is after the sum and not before like $ and the pound signs are used. 10x

Von pedralm:

10. Mai 2012

Ok, I will add it to the next release. Thank you.

Von licaon:

11. Mai 2012

And another thing, looks like the spacing is not kept on replace, say you have "....blahbla $250 mooofoobar" ends up as "....blahblaRON 767 mooofoobar", also it's by design to only replace the entries separated by spaces? like "...Priced At $200-$250" ends up as "Priced AtRON 679,82-$250"

Von licaon:

11. Mai 2012

Also on http://is.gd/pWmF2q in the Specification section in "MSRP $699 / £550 (inc VAT)" only the second value is replaced "$699 / RON 3.033,81 (inc VAT)". 10x

Hi!Thanks for your report!It is not working there because the currency symbol ($) is separated, in the page source, in another node that is not the node with the actual value. So the analyser is not able to see them as a whole "value".I am however thinking on an update that will allow you to select the value from a page and have the conversion pop out, which should work towards problems as these. Thank you!

Von the-arioch:

15. Juni 2012

yeah, some per-page adaptation, different aggressiveness of search may be nice to have.

BTW, remove link to "support page" - there in ur blog comments are disabled for quite a while

Hello, pedralm!Your extension is great, but there is a small problem with me. I'm from Vietnam. In Vietnam and some other countries, we use Arabic numerals with decimal comma. The point symbol "." is using for grouping the digit. You can check here for more details: http://en.wikipedia.org/wiki/Decimal_markSo the problem is when a vietnamese website wrote "1.000 USD" that means one thousand dollars, but the extension understand that is one dollar.Here is a screenshot http://www.megapix.com/?p=51B4C1JJ.jpg

I understand your problem.But the extension uses the basic representation for each currency.In USD (which uses the US numeration system), the decimal separator is always the dot, not the comma (used in metric system). The correct representation of one thousand USD is in fact 1,000. 1.000 would be the metric. This is valid for all "target" pages, which should respect that.If you convert using google converter, you can see that 1,000 U.S. dollars = 698.763189 Euros1.000 U.S. dollar = 0.698763189 EurosWhat you say is that for the Vietnamese, the Vietnamese currency itself would use the dot decimal separator, but the USD would remain using the comma, because it's its own method of representation.one thousand VND = 1.000one thousand USD = 1,000I can't escape from this or else all sites would be a mess do decipher.I am, however, open to suggestions to work around the problem.Thanks!

Hiya, great extension.But, I notice a problem for webpages that are written for my own country and consequently have the values listed in New Zealand dollars.The extension assumes the $ to be USA dollars. So they get converted when they don't need to be!Maybe this is happening for other countries that use the $ sign for their currency?Hopefully a fix is possible.Thanks for your hard work.

Thank you for your feedback!Regarding your issue, I have a couple options.

a) Add the troubling site(s) to the Black Site list, supported by the extension alreadyb) The extension should not parse (now in version 2.2.1) currencies that have prefixes before the $, which for the case of the Australian Dollar, means like "AUS$35", I suppose? Unless there is a space, like "AUS $34", which would not (at the moment), work. If it is let alone as "$34" it is impossible to recognize as being USD or AUS, unless pages that end with ".au" are ignored.

If you know of alternatives, I could attempt to include them in the next version, should they work.

Thank you!

Von pedralm:

13. April 2011

Where it says AUS, should be NZD! Sorry for the big mistake!

Von kiwi2b3:

14. April 2011

Thanks for the quick reply.Yep, I could do a blocklist, most are predictable, but little ol' NZ does have a fair few websites. ;-) What about making the conversion subject to 'hovering' in some way, maybe with an optional tooltip, or a show in the status bar?I like the auto nature of the extension, but maybe a voluntary decision by the user to make the conversion would help avoid unwanted conversions on local pages.Best regards.

Hello and thank you for the comment.The version I am working with (2.0) is converting that value into euros normally. Could you provide more information? Does it behave like that for all currencies being coverted? For only one page? Every time?Thank you.

Von pedralm:

31. März 2011

Even better, the page where that happens! That would be most helpful!Thanks.

Von achij:

1. April 2011

After the upgrade, expansion did not work at any site with any currency. Updated on 2 laptops. Today, everything works on both.Excellent extension! You are well done, thank you))))

Von pedralm:

1. April 2011

I am glad it was only a sidestep! Let me know if anything similar happens again!