Graphics

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

Hi Simon,

What am I missing to have the <201A> string replaced with a comma? I've restarted the program with no luck. 

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

Hi Simon,

What am I missing to have the <201A> string replaced with a comma? I've restarted the program with no luck. 

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

Also it looks like you have put your content in description not value 

Hi Simon,

What am I missing to have the <201A> string replaced with a comma? I've restarted the program with no luck. 

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

I've entered the same text in description and value. 

How do I output to a text box that is in an existing scene template? Do I make the connection in the Layout screen or the Visual Logic screen? Apologies for the basic question -- I wasn't able to find clear direction in the help guide. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 14:50
From: Simon Redmile
Subject: Special characters not decoding properly

Also it looks like you have put your content in description not value 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:47
From: Mark K
Subject: Special characters not decoding properly

Hi Simon,

What am I missing to have the <201A> string replaced with a comma? I've restarted the program with no luck. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 12:59
From: Simon Redmile
Subject: Special characters not decoding properly

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 12:48
From: Mark K
Subject: Special characters not decoding properly

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

------------------------------
Mark K
------------------------------

This is a different example but same idea, this is how you get text to the text object. 

This shows a similar thing as the replace but this is adding strings together and the item below that shows how you can connect 2 different text boxes to each other. 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:55
From: Mark K
Subject: Special characters not decoding properly

I've entered the same text in description and value. 

How do I output to a text box that is in an existing scene template? Do I make the connection in the Layout screen or the Visual Logic screen? Apologies for the basic question -- I wasn't able to find clear direction in the help guide. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 14:50
From: Simon Redmile
Subject: Special characters not decoding properly

Also it looks like you have put your content in description not value 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:47
From: Mark K
Subject: Special characters not decoding properly

Hi Simon,

What am I missing to have the <201A> string replaced with a comma? I've restarted the program with no luck. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 12:59
From: Simon Redmile
Subject: Special characters not decoding properly

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 12:48
From: Mark K
Subject: Special characters not decoding properly

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

------------------------------
Mark K
------------------------------

Hi @Simon Redmile,

There are two special characters that I needed to replace. Unfortunately, I was only able to get the replacement working in Visual Logic by using the � symbol (that is displayed in Xpression) as the input text because the code that was coming in via Xpression CII Gateway didn't work.

This meant that I had to change the source text to a custom string of characters because both problem characters displayed as � in Xpression. Is there any way for me to use data coming in to the Xpression CII Gateway in Visual Logic? For example, I want to replace the <201A> in the Xpression CII Gateway before it is converted to the � symbol in Xpression. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 15:05
From: Simon Redmile
Subject: Special characters not decoding properly

This is a different example but same idea, this is how you get text to the text object. 

This shows a similar thing as the replace but this is adding strings together and the item below that shows how you can connect 2 different text boxes to each other. 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:55
From: Mark K
Subject: Special characters not decoding properly

I've entered the same text in description and value. 

How do I output to a text box that is in an existing scene template? Do I make the connection in the Layout screen or the Visual Logic screen? Apologies for the basic question -- I wasn't able to find clear direction in the help guide. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 14:50
From: Simon Redmile
Subject: Special characters not decoding properly

Also it looks like you have put your content in description not value 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:47
From: Mark K
Subject: Special characters not decoding properly

Hi Simon,

What am I missing to have the <201A> string replaced with a comma? I've restarted the program with no luck. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 12:59
From: Simon Redmile
Subject: Special characters not decoding properly

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 12:48
From: Mark K
Subject: Special characters not decoding properly

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

------------------------------
Mark K
------------------------------

Have you check the CII logs it will show what is being sent into it from your software.

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-18-2025 13:21
From: Mark K
Subject: Special characters not decoding properly

Hi @Simon Redmile,

There are two special characters that I needed to replace. Unfortunately, I was only able to get the replacement working in Visual Logic by using the � symbol (that is displayed in Xpression) as the input text because the code that was coming in via Xpression CII Gateway didn't work.

This meant that I had to change the source text to a custom string of characters because both problem characters displayed as � in Xpression. Is there any way for me to use data coming in to the Xpression CII Gateway in Visual Logic? For example, I want to replace the <201A> in the Xpression CII Gateway before it is converted to the � symbol in Xpression. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 15:05
From: Simon Redmile
Subject: Special characters not decoding properly

This is a different example but same idea, this is how you get text to the text object. 

This shows a similar thing as the replace but this is adding strings together and the item below that shows how you can connect 2 different text boxes to each other. 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:55
From: Mark K
Subject: Special characters not decoding properly

I've entered the same text in description and value. 

How do I output to a text box that is in an existing scene template? Do I make the connection in the Layout screen or the Visual Logic screen? Apologies for the basic question -- I wasn't able to find clear direction in the help guide. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 14:50
From: Simon Redmile
Subject: Special characters not decoding properly

Also it looks like you have put your content in description not value 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:47
From: Mark K
Subject: Special characters not decoding properly

Hi Simon,

What am I missing to have the <201A> string replaced with a comma? I've restarted the program with no luck. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 12:59
From: Simon Redmile
Subject: Special characters not decoding properly

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 12:48
From: Mark K
Subject: Special characters not decoding properly

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

------------------------------
Mark K
------------------------------

The special character ‚ will look like "<E2><20AC><161>" in the XPression CII Gateway log

18-03-25 17:26:59.701: [ Info      ] Incoming (raw): W\1111\45\<E2><20AC><161> words after the character\\
18-03-25 17:26:59.701: [ Info      ] Incoming: write page, source id: 45 target id: 1111
18-03-25 17:26:59.702: [ Info      ] Executed: Created Take Item ID: 1111 from Template ID: 45

Have you check the CII logs it will show what is being sent into it from your software.

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-18-2025 13:21
From: Mark K
Subject: Special characters not decoding properly

Hi @Simon Redmile,

There are two special characters that I needed to replace. Unfortunately, I was only able to get the replacement working in Visual Logic by using the � symbol (that is displayed in Xpression) as the input text because the code that was coming in via Xpression CII Gateway didn't work.

This meant that I had to change the source text to a custom string of characters because both problem characters displayed as � in Xpression. Is there any way for me to use data coming in to the Xpression CII Gateway in Visual Logic? For example, I want to replace the <201A> in the Xpression CII Gateway before it is converted to the � symbol in Xpression. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 15:05
From: Simon Redmile
Subject: Special characters not decoding properly

This is a different example but same idea, this is how you get text to the text object. 

This shows a similar thing as the replace but this is adding strings together and the item below that shows how you can connect 2 different text boxes to each other. 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:55
From: Mark K
Subject: Special characters not decoding properly

I've entered the same text in description and value. 

How do I output to a text box that is in an existing scene template? Do I make the connection in the Layout screen or the Visual Logic screen? Apologies for the basic question -- I wasn't able to find clear direction in the help guide. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 14:50
From: Simon Redmile
Subject: Special characters not decoding properly

Also it looks like you have put your content in description not value 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:47
From: Mark K
Subject: Special characters not decoding properly

Hi Simon,

What am I missing to have the <201A> string replaced with a comma? I've restarted the program with no luck. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 12:59
From: Simon Redmile
Subject: Special characters not decoding properly

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 12:48
From: Mark K
Subject: Special characters not decoding properly

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

------------------------------
Mark K
------------------------------

Have you check the CII logs it will show what is being sent into it from your software.

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-18-2025 13:21
From: Mark K
Subject: Special characters not decoding properly

Hi @Simon Redmile,

There are two special characters that I needed to replace. Unfortunately, I was only able to get the replacement working in Visual Logic by using the � symbol (that is displayed in Xpression) as the input text because the code that was coming in via Xpression CII Gateway didn't work.

This meant that I had to change the source text to a custom string of characters because both problem characters displayed as � in Xpression. Is there any way for me to use data coming in to the Xpression CII Gateway in Visual Logic? For example, I want to replace the <201A> in the Xpression CII Gateway before it is converted to the � symbol in Xpression. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 15:05
From: Simon Redmile
Subject: Special characters not decoding properly

This is a different example but same idea, this is how you get text to the text object. 

This shows a similar thing as the replace but this is adding strings together and the item below that shows how you can connect 2 different text boxes to each other. 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:55
From: Mark K
Subject: Special characters not decoding properly

I've entered the same text in description and value. 

How do I output to a text box that is in an existing scene template? Do I make the connection in the Layout screen or the Visual Logic screen? Apologies for the basic question -- I wasn't able to find clear direction in the help guide. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 14:50
From: Simon Redmile
Subject: Special characters not decoding properly

Also it looks like you have put your content in description not value 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:47
From: Mark K
Subject: Special characters not decoding properly

Hi Simon,

What am I missing to have the <201A> string replaced with a comma? I've restarted the program with no luck. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 12:59
From: Simon Redmile
Subject: Special characters not decoding properly

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 12:48
From: Mark K
Subject: Special characters not decoding properly

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

------------------------------
Mark K
------------------------------

@Simon Redmile @Garner Millward

The comma comes through the Xpression CII Gateway as  <201A>. For example:

John Smith

President<201A> Tech Enterprises Ltd.

I understand this might be an issue with Crestron, but I want to see if there's away to make the correction in Xpression. Xpression is receiving <201A> and turning it into �, so there must be a way to correct this replacement. 

Have you check the CII logs it will show what is being sent into it from your software.

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-18-2025 13:21
From: Mark K
Subject: Special characters not decoding properly

Hi @Simon Redmile,

There are two special characters that I needed to replace. Unfortunately, I was only able to get the replacement working in Visual Logic by using the � symbol (that is displayed in Xpression) as the input text because the code that was coming in via Xpression CII Gateway didn't work.

This meant that I had to change the source text to a custom string of characters because both problem characters displayed as � in Xpression. Is there any way for me to use data coming in to the Xpression CII Gateway in Visual Logic? For example, I want to replace the <201A> in the Xpression CII Gateway before it is converted to the � symbol in Xpression. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 15:05
From: Simon Redmile
Subject: Special characters not decoding properly

This is a different example but same idea, this is how you get text to the text object. 

This shows a similar thing as the replace but this is adding strings together and the item below that shows how you can connect 2 different text boxes to each other. 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:55
From: Mark K
Subject: Special characters not decoding properly

I've entered the same text in description and value. 

How do I output to a text box that is in an existing scene template? Do I make the connection in the Layout screen or the Visual Logic screen? Apologies for the basic question -- I wasn't able to find clear direction in the help guide. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 14:50
From: Simon Redmile
Subject: Special characters not decoding properly

Also it looks like you have put your content in description not value 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 14:47
From: Mark K
Subject: Special characters not decoding properly

Hi Simon,

What am I missing to have the <201A> string replaced with a comma? I've restarted the program with no luck. 

------------------------------
Mark K

Original Message:
Sent: 03-17-2025 12:59
From: Simon Redmile
Subject: Special characters not decoding properly

Are they all unique codes because you could use replace, you can't use a replace script which would be the easiest because you have prime but you do have visual logic. 

The downside to VL is that you can only check 1 value at a time versus script that can do multiple checks in one go so you have to loop it like this; 

------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom

Original Message:
Sent: 03-17-2025 12:48
From: Mark K
Subject: Special characters not decoding properly

Bit of a long story, but the studio I work at feeds lower-third graphics to Ross Xpression via a Crestron touch panel. Unfortunately, special characters entered into Crestron do not translate over to Xpression. Whenever a special character is used, it shows up as � in the Xpression program and as □ on the video output.

When I send data from Crestron to Xpression, I see the special characters come in with < > brackets via the Xpression CII Gateway. For example, a lower comma (special character) comes in as <201A>.

I know this has to do with encoding/decoding. Changing the Crestron's encoding is not an option, so is there any way for Xpression to properly interpret data, like <201A>? Or is there another special character code I could use in Crestron that would be interpreted by Xpression correctly?

One thing of note, the font I am using in Xpression does support special characters. I am on Xpression Prime V7. 

------------------------------
Mark K
------------------------------