Acute c (ć) not being displayed

14 posts / 0 new
Last post
ewan.hislop
Offline
Last seen: 9 years 1 month ago
Joined: 16.02.2012 - 16:38
Acute c (ć) not being displayed

Hi Support

 

We have a user with an acute c in her name. The apostrophy above the c is not being displayed. I have check with another user who has a é in their name and this works ok. It is just the character ć that is not being displayed. I have logged this before under /content/fw-itefx-thread-subscription-ewanhislop-apostrophized-letter-surname-not-showing but have had no update from my last entry. We have tried running adolsign version 2.2 but this made no difference.

 

Best Regards  

itefix
Offline
Last seen: 28 min 47 sec ago
Joined: 01.05.2008 - 21:33
I have prepared a possible

I have prepared a possible fix for the problem and will send you a download link via your e-mail. You need to start adolsign with --unicode option. Please publish your findings here. Thanks.

mesteve@relats.com
Offline
Last seen: 9 years 1 week ago
Joined: 10.05.2012 - 10:31
We are having the same

We are having the same problem. We have tried to solve it using the --utf8 modifier but still not works. Could you send us the same link to try to solve it?

 

thanks in advance,

M.

itefix
Offline
Last seen: 28 min 47 sec ago
Joined: 01.05.2008 - 21:33
We need to make some

We need to make some adjustments in the test version after feedback we received. We will come with an updated test version shortly.

nicolas
Offline
Last seen: 8 years 3 weeks ago
Joined: 23.01.2013 - 09:40
  Hello, I have this problem

 

Hello,

I have this problem too. I'm french, and there's accutes in our names, or generally, disclaimers texts.

My template htm page is UTF-8 encoded :

<meta content="text/html; charset=UTF-8" http-equiv="content-type">

I noticed the resulting htm page is OK with accutes I set in the template htm page (disclaimer), but accutes in my AD database are not supported.

If I set "ISO-8859-15" (Western Europe with € symbol) in place of "UTF-8", then my AD attributes are OK, but my accutes disclamer' became not supported.

Wich encoding page set to have AD attributes and disclaimer supported, in the same time ?

Thanks

Nicolas

PS : I use ADOLSIGN 2.2.0

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

itefix
Offline
Last seen: 28 min 47 sec ago
Joined: 01.05.2008 - 21:33
Try to save your html

Try to save your html template itself in UTF-8 via Notepad. By default, Windows uses UTF-16 LE (Low Endian) Encoding for its Unicode support. Adolsign expects that everthing is in UTF-8.

nicolas
Offline
Last seen: 8 years 3 weeks ago
Joined: 23.01.2013 - 09:40
I did what you said, but it's

I did what you said, but it's not working. AD attributes aren't weel displayed.

Thanks

 

 

itefix
Offline
Last seen: 28 min 47 sec ago
Joined: 01.05.2008 - 21:33
Hmm. Do you get the same if

Hmm. Do you get the same if you remove the tag <meta content="text/html; charset=UTF-8" http-equiv="content-type"> ?

nicolas
Offline
Last seen: 8 years 3 weeks ago
Joined: 23.01.2013 - 09:40
When I remove this tag, it's

When I remove this tag, it's the same result than when I let this tag with "UTF-8" : my AD attributes are "wrong" but not my disclaimer.

Thanks

 

 

itefix
Offline
Last seen: 28 min 47 sec ago
Joined: 01.05.2008 - 21:33
Thanks. We will try to

Thanks. We will try to reproduce the problem and get back to you when we have a solution.

nicolas
Offline
Last seen: 8 years 3 weeks ago
Joined: 23.01.2013 - 09:40
Thanks a lot

Thanks a lot

itefix
Offline
Last seen: 28 min 47 sec ago
Joined: 01.05.2008 - 21:33
We can not reproduce the

We can not reproduce the problem. We've copied acute c from this post to both templates and to Active directory. And it shows up correctly in Outlook. How did you specify -acute c- in AD ? By keyboard or copying from a web page ? The latter can give better results.

pjameson
Offline
Last seen: 3 years 8 months ago
Joined: 13.03.2014 - 13:51
We have a user with an accent

We have a user with an accent above one of letters in his last name, Treviño, and his signature output is corrupted.  I ran ADOLSIGN on his username and the verbose shows the mapping of his last name different

>  field_lastname -> Trevi±o

We have UTF8 on our sig.htm file and other names with accents were created without problem.

Is the problem with the Treviño's AD attribute creation or the connection between ADOLSIGN and AD?  It seems fine in AD, but I'm not sure how his name was initially created.

pjameson
Offline
Last seen: 3 years 8 months ago
Joined: 13.03.2014 - 13:51
What's odd is in the mean

What's odd is in the mean time, I created a unique sig file for this one person, replaced field_lastname with Treviño and then ran it.  The output is still showing Trevi�o

So does that mean it I don't have UTF8 called out correctly?

I thought I had UTF8 correct when we had a Turkish name finally displaying properly, Özge Güleç İnal