option field and ascii characters

I have ascii characters in the value of my option tag in my datacapture.cfg file.

When I save a DCR, it saves the actual registered trademark symbol in the DCR. I want it to be the ascii that you see in the value of the option field.

Any suggestions?

I have attached my code.

TS 6.5 sp1
Windows 2000

Find more posts tagged with

Comments

Migrateduser

Found a workaround, for now.

I'm using FormAPI to add the option(s) to the form, this lets me get the value into the DCR without it actually placing the symbols into my DCR.

- see attachment

For referenct, I'm actually working with Korean characters in my issue.

ISCBorisB

Found a workaround, for now.

I'm using FormAPI to add the option(s) to the form, this lets me get the value into the DCR without it actually placing the symbols into my DCR.

- see attachment

For referenct, I'm actually working with Korean characters in my issue.

You do not need FormAPI for that. Note that your DCT is not HTML, the fact that you have <option> Tag in both does not mean
they have the same Semantics (or even Syntax)

[html]

공[/html]

Migrateduser

Whoops, that was actually me typing freeform for my example. Guess the html coder in me took over my fingers.

I always use the syntax you indicated in your post.

I tried it that way without FormAPI. It doesn't work, just puts bad the Korean characters into the DCR which causes it to mess up the dcr and any xml that I output from it.

The label isn't the issue, it's the value. It's coming across as the Korean characters and not the ascii that I need. When I save the DCR and try to generate the xml both the DCR and the xml file have the messed up Korean characters and not the ascii value.

ISCBorisB

Whoops, that was actually me typing freeform for my example. Guess the html coder in me took over my fingers.

I always use the syntax you indicated in your post.

I tried it that way without FormAPI. It doesn't work, just puts bad the Korean characters into the DCR which causes it to mess up the dcr and any xml that I output from it.

The label isn't the issue, it's the value. It's coming across as the Korean characters and not the ascii that I need. When I save the DCR and try to generate the xml both the DCR and the xml file have the messed up Korean characters and not the ascii value.

Sorry, but that makes even less sense now...

Syntactically correct or Syntactically wrong, your samples show non-ASCII Value / ASCII Label for DCT and
ASCII Value / non-ASCII Label in FormAPI. Probably another *whoops*. Here is some Publisher's trivia:

HTH

Migrateduser

Take the code you posted, and create a DCT. Then create a tpl file to output an xml file from a DCR that you create with that DCT. You will see that the xml that is generated will not be valid.

ISCBorisB

Take the code you posted, and create a DCT. Then create a tpl file to output an xml file from a DCR that you create with that DCT. You will see that the xml that is generated will not be valid.

If that's your case, you have problems in your Presentation Template.

Think about it. DCR is an XML File. As far as TS is concerned, it's a valid one, you can view it, save it, etc.
Your template takes it and generates some XML output, DCR_XML->Your_PT->Another_XML. That 'Another_XML' is
*not valid* (malformed?). As a developer, where would you start looking?

Migrateduser

Got if figured out now.

Here's my recap.....

The whole root of my issue was that I couldn't see Korean in the title of the website pages that were being generated by TeamSite (using XML for my repository in ATG Dynamo). I had to install the Korean language pack on Window XP and then I was able to see the Korean characters properly.

I am going to abandon using the FormAPI as suggested by ICBoris. Since this really wasn't my causing the issue. Using it just created one more file for me to have to edit. Instead I use an inline command to display the options for my select field. The TeamSite users enter their possible values into a txt file that the inline command reads from, standard stuff.

Another issue was that sometimes I edit my xml files outside of TeamSite (on my webserver for quick testing of content changes. But TextPad doesn't like the Korean characters, so I had to install EditPad lite so that I could save the xml without losing the encoding. In EditPad I changed it to use Western European for the encoding and Arial Unicode MS for the font.

I'm slowwwwwwly beginning to learn this stuff...

Thanks for your help again ISCBorisB