#85 Character escape sequences gets corrupted by the parser.

[Daniel Estermann]

For example this selector

.v-ie .base .v-inline-datefield-button:after {
  content: "\200B";
}

turns into this after parsing:

.v-ie .base .v-inline-datefield-button:after {
  content:"​"
}

The resulting character is not printable with the font in this view, but can be printed in the edit mode. It is represented by three bytes 0xE2 0x80 0x8B. I expect however the escaped sequence to be preserved.

[Daniel Estermann]

Related: https://sourceforge.net/p/cssparser/bugs/63/

[RBRi]

Have added a new format option ' useSourceStringValues'. Use the latest snapshot build and check if this works for you.

InputSource source = new InputSource(new StringReader("div:after{content:'css\\200Bparser'}"));
CSSOMParser parser = new CSSOMParser(new SACParserCSS3());
CSSStyleSheetImpl sheet = (CSSStyleSheetImpl) parser.parseStyleSheet(source, null, null);

Assert.assertEquals("div:after { content: \"css\u200Bparser\" }", sheet.getCssText());

Assert.assertEquals("div:after { content: \"css\\200Bparser\" }", sheet.getCssText(new CSSFormat().setUseSourceStringValues(true)));

[Daniel Estermann]

I tested it for me and it looks good. When can you make a release?

[RBRi]

The plan is to do it this weekend - ok or do you need it earlier?

[Daniel Estermann]

No need to hurry, this weekend is perfect. Thank you in advance!