There is a minor issue with the German translation of the following text:
<!ENTITY https-everywhere.cancel.he_blocking_explainer "HTTPS Everywhere noticed you were navigating to a non-HTTPS page, and tried to send you to the HTTPS version instead. The HTTPS version is unavailable. Most likely this site does not support HTTPS, but it is also possible that an attacker is blocking the HTTPS version. If you wish to view the unencrypted version of this page, you can still do so by disabling the 'Block all unencrypted requests' option in your HTTPS Everywhere extension. Be aware that disabling this option could make your browser vulnerable to network-based downgrade attacks on websites you visit.">
The relevant part of the German translation reads:
Falls Sie die nicht verschl眉sselte Version dieser Seite ansehen m枚chten, k枚nnen Sie dass immer noch tun, indem Sie die Option "Alle unverschl眉sselten Anforderungen blockieren" in Ihrer HTTPS Everywhere Extension deaktivieren.
The " should actually be quotation marks and _Extensions_ should better be translated with _Erweiterung_:
Falls Sie die nicht verschl眉sselte Version dieser Seite ansehen m枚chten, k枚nnen Sie dass immer noch tun, indem Sie die Option "Alle unverschl眉sselten Anforderungen blockieren" in Ihrer HTTPS Everywhere Erweiterung deaktivieren.
Otherwise thank you very much for your excellent work!
Thanks for reaching out! This was supposed to be fixed already (#16513,#17042). Could you double-check you are running the latest HTTPS Everywhere version and report back please?
The latest version 2018.10.31, which is the one I am using, is from an earlier date. Nevertheles, I have created a fresh profile and installed the extension from addons.mozilla.org shortly before writing this comment: it still reads ".
Oh yes, you're right sorry. The new version is programmed for release in about one week (#17157). It should be fixed then.
~The latest full release was made in late October while the fix (#17042) was merged in early November. So I am afraid the users will have to wait for the January release (#17157) to see this is fixed.~
@Hainish @zoracon Maybe it is worth mentioning this fix in the changelog.
The quotes are displayed correctly with version 2019.1.7. Thank you.
Most helpful comment
Oh yes, you're right sorry. The new version is programmed for release in about one week (#17157). It should be fixed then.