Closed 0xE1 closed 2 years ago
Hey, this is still an issue, please update your closure dependencies or make sure unicode escaped strings are not converted into unicode characters.
If your expert has
goog.i18n.bidi.rtlChars_ = "֑-ۯۺ-߿יִ-﷿ﹰ-ﻼ"
instead of
goog.i18n.bidi.rtlChars_ = '\u0591-\u06EF\u06FA-\u08FF\u200F\uD802-\uD803\uD83A-\uD83B\uFB1D-\uFDFF\uFE70-\uFEFC'
then issue is still there
This was fixed in latest version
It seems that due to issues related to Closure compiler https://github.com/google/closure-compiler/issues/1704 dymo.connect.framework.js cannot be loaded as Chrome part of Chrome Extension.
I did check file itself and it is utf-8 encoded.
Maybe it can be compiled with :closure-output-charset "US-ASCII" as a workaround?