nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Copy text from other document/browser to DCT

Amit_LnT

Hi,
I am facing an issue with the special characters. The special characters like ' and ©. It is inserted as different characters (' to â€™), in the database after deployment. Strange thing is that the same character is repeated, but it is showing problem at few places.
A word, Maker's it is showing properly. But in another word company's, it shows as companyâ€™s in the database.
This text may have been copied from some document or any other browser. I have to get that confirmation from user.
But I was wondering, the text looks fine on DCT, also the XML is saving the content in UTF 8 format, then how is it not getting those contents properly in database?
If I edit the DCR and type in those special character, it inserts it correctly.
Any help is appreciated..

Thanks,
Amit

Find more posts tagged with

Comments

cesarecastro

Our users have faced this issue when copying from a MS OFFICE doc (word, excel, etc) and pasting into a DCR. The caused, and I am guessing here, is that the char set in MS OFFICE is not UTF 8 or not encoded correctly. It may show ok on the DCR but when generating a file with it or deploying to a database the special chars will display erroneously.

The solution that we have in place is for users not to cut and past from word docs. but if they do they must edit special chars like ' by retyping them in.

Now this may not be the best solution but it is the easiest to implement as you figured out your self.

Has anyone figure how to get around this issue some other way?

ISCBorisB

The solution [...] is for users not to cut and past from word docs. but if they do they must edit special chars like ' by retyping them in

So you basically tell your Contributors "Fix it yourself, not our problem!". This is not a solution.
This is a welfare check your developers have issued to themselves.

[thread=21410]This[/thread] thread has a discussion for the Server side "Office pasting" processing - PTs, Scripts and the like.
[post=107666]Here[/post] Adam shows a mechanism to repair pasted entries right in DCR using FormAPI.

cesarecastro

That's a very good post. I had not seen it. Seem like we will be using it.

I need to check how much more we will need to add to support the 30 some languages we handle.