Tag Encoding for URLS

If you're linking to the a tag page, you can generate the URL via scripting which will also handle the encoding of the tag.

It appears that the encoding used for tags (tags, CFS files, paths) is not exposed directly to scripting. 

For path components (like tags), the encoding replaces non-alphanumeric characters:

• Spaces are replaced with +
• Periods are replaced with -
• Other non-alphanumeric characters are encoded using their unicode bytes as hex values (two hex digits per byte) surrounded with _

This encoding is mostly historic to work around issues with IIS and lossless text encoding. 

I've logged a bug to expose UrlEncodeFileComponent, UrlEncodePathComponent, and UrlDecodePathComponent (UrlDecodeFileComponent already exists) on $core_v2_encoding;

If you're linking to the a tag page, you can generate the URL via scripting which will also handle the encoding of the tag.

It appears that the encoding used for tags (tags, CFS files, paths) is not exposed directly to scripting. 

For path components (like tags), the encoding replaces non-alphanumeric characters:

• Spaces are replaced with +
• Periods are replaced with -
• Other non-alphanumeric characters are encoded using their unicode bytes as hex values (two hex digits per byte) surrounded with _

This encoding is mostly historic to work around issues with IIS and lossless text encoding. 

I've logged a bug to expose UrlEncodeFileComponent, UrlEncodePathComponent, and UrlDecodePathComponent (UrlDecodeFileComponent already exists) on $core_v2_encoding;