It would be great to be also able to encode/decode HTML entities. I thought about writing my own extension for this (I already have published 3), but I feel it might complement yours quite well.

There's a node package that could be used for this:
https://www.npmjs.com/package/ent

What do you think? If you want I could also make a PR with this feature ...

I am writing docs and I have to encode HTML for rendering. Now probem is when I convert it to HTML entities all lines are convert in single line.

Original:

<feather-icon class="mr-1" icon="InfoIcon" />
<feather-icon class="mr-1" icon="HomeIcon" />
<feather-icon class="mr-1" icon="UserIcon" />
<feather-icon icon="TwitterIcon" />

Converted:

<feather-icon class="mr-1" icon="InfoIcon" />
<feather-icon class="mr-1" icon="HomeIcon" />
<feather-icon class="mr-1" icon="UserIcon" />
<feather-icon icon="TwitterIcon" />

How can I preserve the new lines(\n).

Please add for conversion between yml/yaml text and json. Since yaml is a superset of json, there should be a straight-forward-least-common-denominator way to make sure there can be bidirectional conversion. Even if yaml back to json may be lossy (i.e. anchors in yaml).

Sir, ask for help.
I need to put a string to decode（ the string is base64 format），and display it by hex format。But your tool conversion differs from the notepad++ conversion。notepad++ is right for me.
egg.
string is 9PUAQCkAAAEB/gEAAGUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHP9Ps=
your tools convert result is (base64 to string)
3F3F004029000001013F010000650000000000000000000000000000000000000000000000000000000000000000013F3F3F
notepad++ is (base64 decode)
F4F500402900000101FE01000065000000000000000000000000000000000000000000000000000000000000000001CFF4FB

Can you say why? thank you

User clicks "Insert File as Base64 Encoded String"

A common Open File Dialog is displayed, allowing user to browser for a file (can be any file)

File content bytes are converted to base64 encoded string and inserted at the cursor

Hello,

This extension uses 1.0.4 version of applicationInsights which monkey patches the require module. This can have unforeseen consequences in the extension host of VS Code.

Please update to using the latest version 1.0.6 of applicationinsights that has the fix to avoid such monkey patches.

For more details, see microsoft/ApplicationInsights-node.js#425

Thanks!

We already have:

hello world === md5 base64 ==> XrY7u+Ae7tCTyyK7j1rNww==

Cloud you add

hello world === md5 hex ==> 5eb63bbbe01eeed093cb22bb8f5acdc3

as the second format is more commonly used.

doesn't work for commas, eg ,

A great feature would be a two-way string / XML conversion. The conversion is a subset of the HTML conversion and would be useful for users who still use (for whatever horrible reason) XML with CDATA tags that contain string-encoded XML.

Some links for reference
https://stackoverflow.com/questions/21758345/what-are-the-official-xml-reserved-characters
https://www.w3.org/TR/xml/#syntax

Whether you can add Unicode to Chinese, Chinese Unicode ？

Hello, terrific extension!
Would be great if you could add Hex encoding and decoding.
Thank you.

I use this plugin to escape html entities in emails, like the smart quotes and the amperstand.

Now, Outlook.com and Outlook app fail to render the Names HTML Entity (’ like ’) but will render fine the Decimal HTML Entity ( ’ like ’).

More info here: http://www.fileformat.info/info/unicode/char/2019/index.htm

Can be added a configuration setting for the extencion to define the encoding type (HTML Entity (decimal), HTML Entity (hex), HTML Entity (named))?

Thanks!!

When writing HTML code that should display HTML code, the only characters that need encoding are < and &. For reasons of symmetry (and maybe "readability"), also > should be encoded. Quotes ' and " do not need to be encoded in plain HTML text content.

I suggest adding a conversion that covers the three mentioned characters but no quotes. There's no difference between HTML and XML for this matter, so the conversion name could be both. Maybe naming it XML would be more appropriate.

Firstly, Thank you for the helpful package.
I use the string to html entities function the most, and I want to bind the ctrl+alt+c to do this string to HTML function only, to avoid the additional step to select the string to html.
How can I do that?

Is it possible to implement an option to encode just special characters (Brazilian Portuguese has a lot of special characters)? That would be a great feature!

Great work there!
I have a suggestion. The extension is called encode/decode which is a suitable name for what it does. However, the execution command "convert selection" is hard to remember.
how about having an execution command that starts with the name of the extension like "encode/decode: convert selection"? This is a very typical pattern that i've seen with vscode extensions.
That way you can promote all the sub options, such that they live at the same level.

I personally find hard to quick find required command while visually scanning all similarly looking "String to xxx" options.
Can we switch to encode/decode notation instead? (probably can be even configurable to not annoy users used to current schema)

• Encode to Base64
• Decode from Base64
• Encode to JSON Byte Array
• Encode Base64 to JSON Byte Array
• Encode to MD5 Hash (as Base64 or Hex)
• Encode to HTML Entities
• Decode HTML Entities
• Encode to XML Entities
• Decode XML Entities
• Encode to Unicode
• Decode Unicode
• Encode Url
• Decode Url
• Encode Url Component
• Decode Url Component
• Encode Url Component (All Characters)

Convert numbers to a different base. ie hex -> decimal
decimal -> binary.
https://en.wikipedia.org/wiki/Hexadecimal

VSCode version: 1.67.2
ecde version: 1.7.0

Don't know starting from which version, only see the command extension.subtleConvertSelection's Convert Selection, but no extension.convertSelection's Encode/Decode: Convert Selection on the VSCode's Command Palette, as shown in the sreenshot below.

It does not encode quotes correctly.

e.g.
“ > “
‘ > ‘

They should be:
‘ > ‘
’ > ’
“ > “
” > ”

Please add url encode/decode functionality.

Update:
I see there is already functionality using encodeURIComponent (not documented, BTW).
Maybe you can split this into 2 cases:

• String to Encoded Url: will use encodeURI()
• String to Encoded Url Component: will use encodeURIComponent()

1. Select some base64 code.
2. invoke "encode/decode" command
3. in second menu, convert to string
4. edit the string (although this is not necessary, but is the usual workflow)
5. invoke "encode/decode" command

No second menu appears. Cannot convert.

If I do "developer > reload window" then I can run the command again.

This has been a bug for a long time, so not dependent on the current version of VSCode, although I am on Version: 1.39.0-insider.

Please add ability like MD5 for Sha1, sha256 and/or sha512.
Thanks!

Hi, thanks for the useful plugin.

I find that on a Mac, when I encode a chunk of HTML into HTML entities all newlines are replaced by 
. In years of coding I have never found situation where I may need that (if anything, multiple &nbsps may be more useful, although I woudln't want that by default either). Do you think there is a chance to make that configurable on the settings?

Thanks.

I've been working a lot with pieroxy's LZ-String Base64 compressed stuff and would appreciate ECDC eventually getting a release with support for decompressing it so I don't have to rely on external programs. There's no other extension on the marketplace for any variety of encoding/compression of it at the time of this writing.

I see no reason why characters like ö should be converted to ö. I'm successfully using Unicode for my websites for 20 years now. This has resolved all such issues and none of the non-ASCII characters need to be encoded anymore. Encoding invisible characters like   might be useful, but most entities are obsolete.

I love ECDC, but I would really love it if you could possibly add full support for the right click context menu as it's a little tedious having to go to the command palette. I know there is a "Convert Selection" option already there, however it would be great to have that implemented as a fully operational sub-menu. As a last resort I'm currently trying to code my own extension to push the functionality of ECDC into a menu.

Thanks much for the great extension.

Jay

This seemed like a great tool. But then when I want to encode a string for XML, it encodes things like the em-dash “—” with a character reference. That doesn't break anything but it's pointless. It's 2020, and all our fonts and editors can handle em dash glyphs just fine.

This encoding should only encode things absolutely necessary for XML, such as &, <, and >. In fact I'd like a way to turn off encoding " and '. (In fact ' wasn't even officially supported in HTML 4.)

I know this is the XML encoding, not the HTML encoding, but I'd still like to configure which things get converted, and these arbitrary extra characters shouldn't be encoded just because they aren't ASCII. (It might have been appropriate in the 1990s.)

Feature Request:
What I need at the moment is JSON Byte array to string.

[104,101,108,108,111,32,119,111,114,108,100] --> hello world

I believe it should be ’

contributes.menus
https://code.visualstudio.com/docs/extensionAPI/extension-points#_contributesmenus

Currently extension writers can to contribute to:
The Explorer context menu - explorer/context
The editor context menu - editor/context
The editor title menu - editor/title

If the select text contains spaces, the spaces are not converted into html entities.
Even if I select a single space, it won't be translated into a html entity.
It's possible that this is the intended behavior but sometimes you just want the spaces to be converted.

Maybe it could be possible to let uses decided if they want the spaces converted or not.

When Polish (Programmers) keyboard layout is used, Ctrl+Alt+C is used to type ć character.
Unfortunately, ecdc extension overrides that binding, what interrupts normal typing.

(node:3996) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

I really prefer extensions to have a category, and so do the Microsoft devs:

https://code.visualstudio.com/api/references/contribution-points#contributes.commands