Encoding name normalization does not remove year suffix
See original GitHub issueThis line is supposed to normalize encoding names by removing non-alphanumeric characters and stripping an appended year. The year is not being stripped with the current regex, causing encoding names with years to not match.
Example:
Input: iso_8859-5:1988
Output: iso885951988
Expected output: iso88595
I think the reason the current regex does not work is that the colon character is matched in the first part as a non-alphanumeric character, therefore causing the following year part to not match.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
FAQ - Normalization - Unicode
Q: What is normalization? Unicode encodes some text elements both as precomposed forms and as combining character sequences. The precomposed form has a ......
Read more >Alma Normalization Rule Examples
Remove the last comma in 500 subfield a and do not touch the other commas. (it uses a temporary string with the comma...
Read more >What is normalized UTF-8 all about? - Stack Overflow
Normalization is an attempt at dealing with that. Normalizing assures (or at least tries to) that all the characters are encoded the same...
Read more >encoding/xml: empty namespace prefix definitions should be ...
It says "The attribute's normalized value MUST be either a URI reference — the namespace name identifying the namespace — or an empty...
Read more >RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
This specification does not define a generative grammar for URIs; ... Generic Syntax Each URI begins with a scheme name, as defined in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks guys, I think you’re right, I’ll add a fix soon.
– Alexander Shtuchkin
On Wed, Jul 5, 2017 at 11:26 AM, Erik Kemperman notifications@github.com wrote:
Thanks!