I've upgraded one of our websites from Umbraco 8 to Umbraco version 13.1.1.
This site is now up and running but I noticed that all double byte characters are being encoded in the source of the page. For example I added "テスト内容" to a textString field and displayed it on the template using @Model.Value("test"). On Umbraco 8 this would have been in the source as "テスト内容" but in 13 it's テスト内容. This is the same for all fields except for RTE's which have Html.Raw() wrapped around them and show the original characters.
E.g. my SEO title field : <title>テスト内容</title>
My concern is that screen readers, SEO bots and anything else that scrapes the screen like social apps and Json LD may get the encoded version as even japanese image file names show as :
Is there any configuration to disable this functionality so it shows unencoded or do I even need to be concerned?
Is this due to .net core or a change in umbraco? From my testing the images still display, the metadata could be read by my SEO extension but I'm not sure if Json LD readers and social sites will see the data in the same way. I tested this in a completely new install of u13.1.1 and a u12.3.7 and seen the same behaviour.
Double byte character encoding in source view
Hi,
I've upgraded one of our websites from Umbraco 8 to Umbraco version 13.1.1.
This site is now up and running but I noticed that all double byte characters are being encoded in the source of the page. For example I added "テスト内容" to a textString field and displayed it on the template using @Model.Value("test"). On Umbraco 8 this would have been in the source as "テスト内容" but in 13 it's
テスト内容. This is the same for all fields except for RTE's which have Html.Raw() wrapped around them and show the original characters. E.g. my SEO title field :<title>テスト内容</title>My concern is that screen readers, SEO bots and anything else that scrapes the screen like social apps and Json LD may get the encoded version as even japanese image file names show as :
Is there any configuration to disable this functionality so it shows unencoded or do I even need to be concerned?
Is this due to .net core or a change in umbraco? From my testing the images still display, the metadata could be read by my SEO extension but I'm not sure if Json LD readers and social sites will see the data in the same way. I tested this in a completely new install of u13.1.1 and a u12.3.7 and seen the same behaviour.
is working on a reply...