Special character issue in tpl file

Hi All,

I have a situation where my client requirement is to have special character in tpl as mentioned below:

<iw_value name='xyz'/><bold>Monégasque</bold>

When I try to preview or generate the DCR, it display me the below error message:

"An error occurred during PT compiling. Please see more details in log files."

Could anyone please provide me the suggestions and workaround to resolve this issue?

Current environment: TS6.7.1, OD6.1, Solaris9

Regards,
Ace

Find more posts tagged with

Comments

shwetha

You can try modifying "iwpt_compile.ipl " file to support the encoding of special characters you are trying to display on the page.

acezone

You can try modifying "iwpt_compile.ipl " file to support the encoding of special characters you are trying to display on the page.

Hi Shwetha,

iwpt_compile.ipl is used to basically compile the file with output file. Also my problem here is with special character not properly working at tpl level. so anyways I will be getting the error even if I compile.

Query is basically to know the way of handling the special character in tpl without modifying the content in hash code or HTML code?

Regards,
Ace

kaalraa

Hi All,

I have a situation where my client requirement is to have special character in tpl as mentioned below:

Monégasque

When I try to preview or generate the DCR, it display me the below error message:

"An error occurred during PT compiling. Please see more details in log files."

Could anyone please provide me the suggestions and workaround to resolve this issue?

Current environment: TS6.7.1, OD6.1, Solaris9

Regards,
Ace

It is better to use ASCII codes for special chars like ® ( & # 174 ; )

acezone

I am not expecting any modification to be done for special character in tpl (neither hash codes nor html code nor ASCII code). By doing this I would then first have to get the ASCII code conversion content via VFE or other medium. This is not my requirement.

ISCBorisB

Hi All,

I have a situation where my client requirement is to have special character in tpl as mentioned below:

<iw_value name='xyz'/><bold>Monégasque</bold>

When I try to preview or generate the DCR, it display me the below error message:

"An error occurred during PT compiling. Please see more details in log files."

Could anyone please provide me the suggestions and workaround to resolve this issue?

Current environment: TS6.7.1, OD6.1, Solaris9

Regards,
Ace

What is the intended Target Encoding? In other words, what should be the encoding of the Assets you are generating using this PT?

ISCBorisB

You can try modifying "iwpt_compile.ipl " file to support the encoding of special characters you are trying to display on the page.

It's already there - and has been for years. Read about iwpt_compile -oenc Flag

moonkhanna

I am not expecting any modification to be done for special character in tpl (neither hash codes nor html code nor ASCII code). By doing this I would then first have to get the ASCII code conversion content via VFE or other medium. This is not my requirement.

Since you are hardcoding this value, it does not require you a VFE.. If you are getting this value from a text field in your DCR, then yes, you need to use -oenc as Bo stated.

If that also does not work, in your PT, use regex to replace this special character with its friendly value...

acezone

Let me summarise the issue again:

My client requirement is that whatever the content is written in TPL should be any special character languages (Arabic, French, German, Spanish etc.). Now if I write the special character content in TPL it basically throws an error message on preview or generation of the DCR.

I have suggested him to use ASCII code or hash code to maintain the content in CMS, though at times he will be updating the language content himself, so he does not wants to play around with

1. copy the content in VFE to generate the hash code or ASCII code.
2. it will be time consuming for him to enter the data.

So he wants to have the flexibility in TS so that it can support special character in TPL and should not throw error messages on preview or generation of DCR.

Hope this scenario will help you understanding my situation and clients requirement.

Regards,
Ace

moonkhanna

Let me summarise the issue again:

My client requirement is that whatever the content is written in TPL should be any special character languages (Arabic, French, German, Spanish etc.). Now if I write the special character content in TPL it basically throws an error message on preview or generation of the DCR.

I have suggested him to use ASCII code or hash code to maintain the content in CMS, though at times he will be updating the language content himself, so he does not wants to play around with

1. copy the content in VFE to generate the hash code or ASCII code.
2. it will be time consuming for him to enter the data.

So he wants to have the flexibility in TS so that it can support special character in TPL and should not throw error messages on preview or generation of DCR.

Hope this scenario will help you understanding my situation and clients requirement.

Regards,
Ace

Does putting the special characters in CDATA Tag not help your purpose.. I feel, it should help..

acezone

I even tried that but no success.

ISCBorisB

I even tried that but no success.

See if encoding may help, like [post=103379]here[/post]. Note that this thread is about inline, in your case you may want to try it from iw_perl Tag.

acezone

See if encoding may help, like [post=103379]here[/post]. Note that this thread is about inline, in your case you may want to try it from iw_perl Tag.

Hi Bo,

I used the below mentioned snippet to make this working:

<iw_perl>
     <![CDATA[
          my $var="Monégasque";
          iwpt_output("$var");
     ]]>
</iw_perl>

But still no success...

Please suggest if I need to make any other changes/workaround to make it working.

Regards,
Ace

ISCBorisB

Hi Bo,

I used the below mentioned snippet to make this working [...] But still no success...

What is the exact problem manifestation? In other words, what exactly "still no success" means?
Is it PT compilation error, broken encoding in the generated Page, garbage Symbols somewhere, or perhaps
something else?

acezone

Hi All,

It is PT compilation error. I tried using iw_pt tag as

<iw_pt encoding="ISO-8859-1" />

which actually provided me the flexibility of using the special charater in template without any hash code or ASCII code and giving result in desired format.

I am now closing this thread considering it as resolved.

Thanks for all your valuable comments and suggestions.

Regards,
Ace

ISCBorisB

Hi All,

It is PT compilation error. I tried using iw_pt tag as

<iw_pt encoding="ISO-8859-1" />

which actually provided me the flexibility of using the special charater in template without any hash code or ASCII code and giving result in desired format.

I am now closing this thread considering it as resolved.

Thanks for all your valuable comments and suggestions.

Regards,
Ace

The best way to solve this sort of issues is to avoid them in the first place. Use non-XML Presentation Templates

acezone

Use non-XML Templates

Hi Bo,

Could you please help me in understanding, what do you mean by "Use non-XML Templates"?

Regards,
Ace

ISCBorisB

Hi Bo,

Could you please help me in understanding, what do you mean by "Use non-XML Templates"?

Regards,
Ace

There are actually two PT Coding modes, XML and non-XML.

In non-XML mode you either start your PT with the closed iw_pt Tag (my personal preference) or drop iw_pt Tag altogether.
You can still use IWOV Tags, the difference is in parsing. Your PT no longer has to be well-formed, CDATA is no longer
needed, etc,

Take a look at the following help Page for some details:
http: //Your_TS_Server/iw/help/tst/pt/TeamSite__PT__iw_pt.html

acezone

There are actually two PT Coding modes, XML and non-XML.

In non-XML mode you either start your PT with the closed iw_pt Tag (my personal preference) or drop iw_pt Tag altogether.
You can still use IWOV Tags, the difference is in parsing. Your PT no longer has to be well-formed, CDATA is no longer
needed, etc,

Take a look at the following help Page for some details:
http: //Your_TS_Server/iw/help/tst/pt/TeamSite__PT__iw_pt.html

Bo,

Thanks for clarifying my doubts. I will keep this in mind and will implement the same in my further projects.

Regards,
Ace