hexadecimal value 0x1f is an invalid character - Translation Manager Feedback

Press Ctrl / CMD + C to copy this to your clipboard.

Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

Frans de Jong 548 posts 1840 karma points MVP 4x c-trib

Oct 21, 2022 @ 12:47

0

hexadecimal value 0x1f is an invalid character

I get this error while trying to translate a Dutch text to English. There seems to be a character somewhere that is invalid? What is the fastest way to get this solved?

Copy Link
Kevin Jump 2342 posts 14889 karma points MVP 8x c-trib

Oct 21, 2022 @ 14:01

0

Hi,

Yeah i am not sure 😔 - Its happening quite deep in the Xliff processor, so i don't think we can isolate it by property or anything just yet.

Quick scan and i think its a windows control character that we should probably throw away.

But as to finding it on a current site, best i can suggest it try to send chucks of the site to translation and see if you can narrow it down

Copy Link
mark firth 32 posts 75 karma points

Jun 10, 2023 @ 10:40
0
Hi Kevin, I have a very similar issue. Im using Umbraco 9. On the first run im getting the following error:

'', hexadecimal value 0x03, is an invalid character.

I've tried searching for the character in the database with:
```
SELECT        id, versionId, propertyTypeId, languageId, segment, intValue, decimalValue, dateValue, varcharValue, textValue
FROM            umbracoPropertyData
WHERE        (varcharValue LIKE '%' + CHAR(0x03) + '%') OR
                         (textValue LIKE '%' + CHAR(0x03) + '%')
```
to no avail.

Its bit of show stopper. Do you not think the pluggin should just strip out the control characters? like here: https://seattlesoftware.wordpress.com/tag/hexadecimal-value-0x-is-an-invalid-character/

Cheers Mark
Copy Link
Kevin Jump 2342 posts 14889 karma points MVP 8x c-trib

21 days ago

0

Yeah,

we do clean the xml - but not as comprehensively as that example (and we should!)

We can fix this quickly, but it's worth noting we don't do updates for v9 anymore as it has reached end of life (so when we do fix this, it will be for v10, 13 and 14 but not 9,11 or 12 🙁)

Copy Link
Kevin Jump 2342 posts 14889 karma points MVP 8x c-trib

21 days ago

0

Hi,

we have fixed this for v13 and v10. (v13.1.4 and v10.6.4)

Copy Link
is working on a reply...

Please Sign in or register to post replies