izzy / d3coder Goto Github PK

See #24

See #24

See #24

See #24

See #24

See #24

See #24

See #24

See #24

See #24

The native notification output isn't working anymore. Since most users didn't seem to notice this or didn't care it would probably be best to remove the feature all together and have less permissions that need to be requested.

See #24

From the Chrome Webstore:

Hi! I'd like to see something that can decode "AB CD EF"-style hex. Thanks!

See #24

Some languages translated use RTL instead of the western standard LTR text direction. This probably needs some changes in the CSS code to actually work properly with these languages.

I assume the styles/menu.css will need at least some additional styling. There is documentation available on how to use the predefined messages with the i18n API: https://developer.chrome.com/extensions/i18n#overview-predefined

See #24

See #24

See #24

See #24

When parsing a binary string that contains spaces/newlines like the following:

01001000 01100101 01101100 01101100 
01101111 00100000 01110111 01101111 
01110010 01101100 01100100 

The function returns the following string:

H²Û-�|�ïoÜ­�@

Instead of:

Hello world

#24

See #24

From the Extension Support page:

I want to use this inside devtools so I can right click some items in the network section and decode them right on the spot instead of copying to another application.

Any chance you can manipulate the devtools context menu to include other than 'copy' the 'encode' function as well?

This could be possible through defining a devtools_page.

On the d3coder Menu options page, both Base64 options are labelled "encode", as shown below:

Although the options function correctly (one encodes, one decodes), I would suggest relabeling the second checkbox to reflect that it controls Base64 decoding instead.

Is there any option to be able to scroll through the decode types to see what the output would be without having to click on each type? Maybe in the console or something?

Describe the bug
Some (ja, kn) translation files are named message.json instead of messages.json

See #24

See #24

It works in a lot of cases, but I've just noticed while working with quoted-printable text that it doesn't do that very well. For example, the string "=E2=80=94" should decode to "—", but this extension shows "â��". Also, "=E2=80=99" should decode to "’", but it gave "â��" again. This seems to be a problem with Unicode support.

It doesn't handle the "=" linebreaks correctly, either. The decoded text includes a lot of equal signs in them.

PS: I'd submitted this issue report in the Chrome webstore as a review, then a support issue, but then I realized this repo is probably the place you'd be most likely to notice this report. My apologies for the duplication and I hope it doesn't overload you.

See https://developer.chrome.com/extensions/optionsV2

Relates to #24

• ClipboardRead needs to be in there for conversion from the clipboard
• ClipboardWrite is needed for copy-to-clipboard
• tabs isn't needed afaics and what I could see from testing(see https://developer.chrome.com/extensions/tabs)
• contextMenus is needed for self explanatory reasons
• permissive :///* is needed to be able to act on all sites
• storage is needed to be able to save settings

See #24

See #24

Relates to #24

Should be a breeze, not a lot to do apart from replacing a lot of text and changing one or two JS functions

See

• https://developer.chrome.com/extensions/i18n
• https://developer.chrome.com/webstore/i18n

List of Locales:

• https://developer.chrome.com/webstore/i18n#localeTable

Will do English & German first as a PoC, more can follow after that, focus should be on those languages with the most users. This might help the growing userbase of Spanish users as well as the plethora of Asian language users.

See #24

See #24

Add dutch translations. Relates to #24

See #24

See #24

See #24

See #24

See #24

See http://www.gta.ufrj.br/ensino/eel878/sockets/inet_ntoaman.html

See #24

Since #23 added the capabilities of translating the extension it would be great to have more translations available for those who aren't native English speakers.

The translations need a folder with the language code in the _locales folder and a messages.json in that sub-folder. The easiest way to get all the messages is to copy the English folder(_locales/en/) and go from there.

Some translations might not need all the fields if e.g. the text is understandable in your language and might only need a translation in languages that use non-latin characters and have their own words/phrases for messages that are otherwise not translated. Messages that aren't translated will take their text from the English translation - see German as an example for that.

A list of possible translations is available at https://developer.chrome.com/webstore/i18n#localeTable

I'll list translations that are done and won't be needing a translation as checked here. Those currently being worked on or free as unchecked. If it's not on the list but in the possible translation list - see link above - just write a comment under this issue, otherwise write in the linked issue so I can assign you:

• ar - Arabic #39
• am - Amharic #72
• bg - Bulgarian #45
• bn - Bengali - #73
• ca - Catalan #46
• cs - Czech #47
• da - Danish #48
• de - German
• el - Greek
• en - English
• es - Spanish
• et - Estonian #49
• fa - Persian #74
• fi - Finnish #50
• fil - Filipino #51
• fr - French
• gu - Gujarati #88
• he - Hebrew #52
• hi - Hindi #53
• hr - Croatian #54
• hu - Hungarian #55
• id - Indonesian #56
• it - Italian #57
• ja - Japanese #58
• kn - Kannada #75
• ko - Korean #59
• lt - Lithuanian #89
• lv - Latvian #90
• ml - Malayalam #91
• mr - Marathi #92
• ms - Malay #93
• nl - Dutch
• no - Norwegian #94
• pl - Polish
• pt_BR - Portuguese (Brazil)
• pt_PT - Portuguese (Portugal) #95
• ro - Romanian #96
• ru - Russian
• sk - Slovak #97
• th - Thai
• tr - Turkish
• uk - Ukrainian #77
• zh_CN - Chinese (China) #60
• zh_TW - Chinese (Taiwan) #61

Add Brazilian Portuguese translations

With the test text

a:2:{i:0;s:4:"pleh";i:1;a:2:{i:0;s:4:"pleh";i:1;R:3;}}

The unserialize function will throw the following exception

Error in event handler for contextMenus: SyntaxError: Unknown / Unhandled data type(s): r
at error (chrome-extension://gncnbkghencmkfgeepfaonmegemakcol/js/D3.js:1000:61)
at _unserialize (chrome-extension://gncnbkghencmkfgeepfaonmegemakcol/js/D3.js:1109:18)
at _unserialize (chrome-extension://gncnbkghencmkfgeepfaonmegemakcol/js/D3.js:1098:35)
at _unserialize (chrome-extension://gncnbkghencmkfgeepfaonmegemakcol/js/D3.js:1098:35)
at D3.unserialize (chrome-extension://gncnbkghencmkfgeepfaonmegemakcol/js/D3.js:1115:25)
at menu.onclick (chrome-extension://gncnbkghencmkfgeepfaonmegemakcol/js/D3.js:1256:54)

This exception should be handled and at least known types should be printed. "R" (for recursion) could be printed as simple text like "recursion pointer".