How to handle special characters on Builder

Ricardo_Cartaxo

How to handle special characters on Builder

 

Hello,

 

We are having some issues handling special characters on Builder, especially when this characters have to be showed on Livelink interface.

 

For instance we have a custom module which adds new webcommands to certain nodes, and the fName that we want to show on livelink interface has special characters like ‘ç’ or ‘ã’. This characters are replaced with ‘?’

 

We are using xlates to save this string and when we define the value of this xlate and introduce this special characters builder saves the string on the properties files and replaces the special character with \u123, which seems that he is taking care of the encoding. But when they appear on the livelink interface they are always replaced with ‘?’.

 

Anyone can help on the best way to address this situation.

 

 Thanks in advanced.

 Best regards

enconding.png

Hans Stoop

Which version of CS do you use and is it a UTF-8 version of CS?

 

Hans

 

From: eLink Entry: Content Server Builder Forum [mailto:componentbuilder@elinkkc.opentext.com]
Sent: Freitag, 26. Oktober 2012 12:06
To: eLink Recipient
Subject: How to handle special characters on Builder

 

[Attachments exceeded pre-set size limits. Use the links provided to access]

How to handle special characters on Builder

Posted byricardo.cartaxo@novabase.pt (Cartaxo, Ricardo) On 10-26-2012 06:01

 

How to handle special characters on Builder   Hello,   We are having some issues handling special characters on Builder, especially when this characters have to be showed on Livelink interface.   For instance we have a custom module which adds new webcommands to certain nodes, and the fName that we want to show on livelink interface has special characters like ‘ç’ or ‘ã’. This characters are replaced with ‘?’   We are using xlates to save this string and when we define the value of this xlate and introduce this special characters builder saves the string on the properties files and replaces the special character with \u123, which seems that he is taking care of the encoding. But when they appear on the livelink interface they are always replaced with ‘?’.   Anyone can help on the best way to addre! ss this situation.    Thanks in advanced.  Best regards

 

Attachment Links:

enconding.png (185 KB)

---

[To post a comment, use the normal reply function]
Forum:	Content Server Builder Forum
Content Server:	Knowledge Center