nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

different encodings for different branches.

nirjari

If I want ISO-8859-1 for press branch and UTF-8 for radio branch, shall I just need to configure it in templating.cfg ? or do I need to do something else too ? Where to configure encoding in templating.cfg ?

thnaks

Find more posts tagged with

Comments

ISCBorisB

If I want ISO-8859-1 for press branch and UTF-8 for radio branch, shall I just need to configure it in templating.cfg ? or do I need to do something else too ? Where to configure encoding in templating.cfg ?

thnaks

DCRs are always encoded in UTF-8. Encoding of the generated components depends on what and how
you generate in your "ptcompiler" code. As long as it's not UTF-8 it is your (the developer) responsibility
to convert the output to whatever encoding you need

nirali

I have a further question on encoding.

Is it possible to use an encoding which is currently not in the list of supported encodings ? Is there a way to configure an encoding in TS6.7.2 or OD currently not supported ?

If yes, how ?

Thanks

ISCBorisB

I have a further question on encoding.

Is it possible to use an encoding which is currently not in the list of supported encodings ? Is there a way to configure an encoding in TS6.7.2 or OD currently not supported ?

If yes, how ?

Thanks

You'd have to provide question context for any meaningful answer. In general:

DCR Encoding is fixed to UTF-8.
Your generated output encoding is up to you, it could be anything at all mix including.
TS GUI is basically UTF-8, primary language depends on the Install Locale.
OD proper is encoding-neutral, it'll happily transport anything.
DD is a special beast. Depending on the DB Vendor and your configuration you may in some cases have to encode/decode your Tuples, etc

ShowOnlyFirstLastLabelChart.rptdesign

nirali

I can use any encoding for generated output. Thats understandable when I am creating HTMl or JSP page by myself and not generating it thru TS672

When I am using TPL to generate output, by default the output will have UTF-8 encoding. If I want to change this encoding to something else, where do I specify it ?

My apologies, if question does not sound any intelligent.

Thanks

ISCBorisB

I can use any encoding for generated output. Thats understandable when I am creating HTMl or JSP page by myself and not generating it thru TS672

When I am using TPL to generate output, by default the output will have UTF-8 encoding. If I want to change this encoding to something else, where do I specify it ?

My apologies, if question does not sound any intelligent.

Thanks

It's not that PT output is UTF-8 by default. DCR Values obtained by PT are UTF-8 by default, the rest is up to you.

You can not just specify desired encoding. You'd have to code. Search Forum for Encoding, I recall few
decent threads. Run "perldoc Encode", consider Package API. Play with the following simple sample, try
to use encoding in templates. It's fairly large and non-trivial topic


use strict; 
use Encode 'from_to'; 

my $source = '012ABC'; 
my $target = $source; 
eval {Encode::from_to($target, 'utf8', 'UTF-16LE', Encode::FB_CROAK);}; 
if ($@) { 
   print "Can Not Convert to UTF-16: $@"; 
} 
print qq(UTF8 -     $source\n); 
print qq(UTF-16LE - $target\n);