xlateStrMap not working in 6.1.2?

This topic has 1 reply, 1 voice, and was last updated 7 years, 5 months ago by Mike Keys.

Creator

Topic
March 30, 2017 at 7:22 pm #55346

Mike Keys
Participant

I’m trying to replace a “en dash” character (hex 96) with a regular dash (2D).

I’m using a copy statement with the xlateStrMap function. In the Content window I have the following:

xlateStrMap {x96 -}

Is this correct?
Creator

Topic

Viewing 0 reply threads

Author

Replies
- March 31, 2017 at 5:44 pm #85042
  
  Mike Keys
  Participant
  
  So, found out that when using Cloverleaf 5.7 this isn’t an issue. Testing in this environment with the string map function works as expected.
  
  What I had to eventually do was change the encoding on the outbound thread to ISO-8859-1 in conjunction with the string map call.
  
  I opened a ticket with Infor and this was what they said:
  
  “Beginning with 5.8 we merged the regular cloverleaf with the multi-byte cloverleaf which is probably why you see the difference and need to specify the encoding for it to handle properly.”
Author

Replies

Viewing 0 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.