Accented characters in tagged text

I normally write copy in a text editor (TextPad), paste into InDesign, and format in the Story Editor. Now I want to format in TextPad and import tagged text. But I am finding that accented characters from the numeric keypad as well as other more frequently used characters - €, £ - are being misinterpreted. For instance R$8·25 million (about €3 million) comes in as R$8Â·25 million (about â‚¬3 million) and Fundação de Amparo à Pesquisa do Estado de São Paulo is rendered as FundaÃ§Ã£o de Amparo Ã Pesquisa do Estado de SÃ£o Paulo.
I have the options to format the text file as ANSI or DOS, and I have used the headers <ASCII-WIN> and <ANSI-WIN>, but there seems to be no combination that brings the text in cleanly.
Substituting Unicode values for these characters gives me what I want and I can build a library of them to add in TextPad, but this is counter to my aim of more productivity.
Can anyone give me a the formatting options to enable me to use the numeric keypad to generate the extended character set in a form that will import as tagged text?
k

Yes, sorry, it had to be somewhere from InDesign to InDesign. What I actually meant was that your tagged text started life in InDesign. My tagged text is starting life in TextPad.
TextPad can save text in DOS (I guess that means ASCII), ANSI and UTF-8. It's possible that the text in the file I was importing wasn't actually in ANSI. I've restructured it now and it is importing accented characters correctly except, bizarrely, for the Euro symbol (yes, there is a € in the font - Myriad Pro). If I use Alt0128 to create the symbol - or the keyboard AltGr4 - import stops at the last complete line before the € would be encountered, and nothing more is imported. If I use <0x20AC> the symbol imports properly and the whole file is placed.
I also worked with two identical (except for the substitution of some Unicode characters) versions of the same file. Both were ANSI, and both were headed with <ANSI-WIN> and no other definition information. One file picked up the definitions from the InDesign decument and rendered correctly, the other ignored all the paragraph styles and simply imported text at the default paragraph style.
So please accept some points for your collection Ken for leading me to re-check the actual code set in the document.
If you have any ideas about the € problem or why one version of the file would not pick up style definitions I would be intrigued to hear.
k
As an afterthought, I've attached a chunk of each file to show one that picks up definitions and one that doesn't. My initial thought was that the one that does pick up definitions would bleat about them being missing, while the other wouldn't. But if I place them in a blank file, both complain that the definitions are missing. However, If I make an appropriately named definition to match one in the file, the version that picks up definitions will match it and only bleat about the other missing definitions. The file that isn't picking up definitions will fail to honour the paragraph style, and will complain that the remainder are missing.

Similar Messages

Accented characters do not display correctly if there is a variable beside it

Hello,
We are experiencing a problem when we have text with accented characters an a variable beside it within the same text box.
The problem is that the accented characters in the text do not display correctly in the preview or publised course to Flash9
These characters display correctly in Captivate in edit mode.
This is the process we have followed:
Export to XML
Translated
Import XML
Publish to Flash9
Captivate version: 4
OS: Windows Vista SP2
We have tried to work with locale in Spanish with no luck, the only solution we have found is to put the text and the variable in different text boxes
I have pasted an image of the preview and also of the text in Captivate edit mode.
Any help will be very welcomed !
Tess

Hi there
I agree with Lilybiri that you should definitely file a Bug Report.
However, a thought occurs here. Have you tried placing the accented text in a User Defined variable?
Assuming this is a workaround, my thought is that you could then just have a caption with two variables. The User Defined variable containing the accented text followed immediately by the system variable providing the Project Name.
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

How to exclude accent characters in Text components

How can I exclude accent characters in Text components. I
just want the keystroke do nothing for accent characters.

I assume you mean TextInput.
Easiest way? You may want to do something like this, it
restricts input to only the provided characters, so you'd have to
add any others that you DO want:
restrict="ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz"
Harder way? Extend TextInput (but it only stops `):

Pages breaks words using "Justify text" on certain accented characters

I'm working on a document in Hungarian, and it seems that when I use the "justified text" setting, this puts extra white space around certain accented characters.
Please see these screenshots:
http://www.kkovacs.hu/~kkovacs/Pages-bug-with-accented-words.jpg
In this case, "időszak" should be a single word, and it is, when I write it as "Idõszak" (using õ instead of ő, but this is not the character that is needed there). The problem seems independent of the font that I use (Big Caslon, in the example above).
Is there a way to work around this?
Thanks in advance,
Kristóf

Hello
My old eyes fooled me.
I saw a "lowercase o with a tilde" when it was a "lowercase o with double acute"
With your font which is a bit more recent than mine, the missing glyph is grabbed from an other font (I didn't search which one it is).
I didn't got what was in your original screenshot.
I just get a character with a fully different drawing.
It's funny because it's the kind of problem RC-R and me where exchanging about in:
http://discussions.apple.com/thread.jspa?threadID=1644259&tstart=0
Given what I get, I will not call that a bug but a feature that many users (most of them ?) are unaware of.
The operating system does its best to display the character we are asking for even if it is not built in the used font.
This trickery has PROs and CONs.
For your use, I'm afraid that CONs are the most important and that you will have to search for a font embedding the needed characters.
To scan the contents of a font, I uses the free Linotype FontExplorer which displays the defined glyphs in black and the missing ones in red so, it's easy to see if a font fit our needs.
Yvan KOENIG (from FRANCE mardi 5 août 2008 16:01:46)

Problem with base64 encoding an xml file with accented characters

Oracle 10.2.0.1.0 Enterprise Edition running under windows 2003 server
DB Characterset UTF-8
I have a routine which takes an xml file and base64 encodes it, and the base64encoded text is stored in a clob column of a table.
The xml file is stored in UTF-8 format.
The routine works correctly, except when there are accented characters.
I am using dbms_lob.loadclobfrom file to load the file.
DBMS_LOB.OPEN(src_clob, DBMS_LOB.LOB_READONLY);
 DBMS_LOB.LoadCLOBFromFile(
 DEST_LOB => dest_clob
 , SRC_BFILE => src_clob
 , AMOUNT => DBMS_LOB.GETLENGTH(src_clob)
 , DEST_OFFSET => dst_offset
 , SRC_OFFSET => src_offset
 , BFILE_CSID =>dbms_lob.default_csid
 , LANG_CONTEXT => lang_ctx
 , WARNING => warning
 DBMS_LOB.CLOSE(src_clob);base 64 encoded xml with accented character -- incorrect
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjxncDpBcHBs
aWNhdGlvblByb2ZpbGUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAx
L1hNTFNjaGVtYS1pbnN0YW5jZSINCiAgICB4c2k6c2NoZW1hTG9jYXRpb249Imh0
dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2Zp
bGVzLzEuMS4wIGh0dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9z
eXN0ZW1zLXByb2ZpbGVzLzEuMS4wL0dQLnN5c3RlbXMucHJvZmlsZXMuMS4xLjAu
QXBwbGljYXRpb25Qcm9maWxlLnhzZCINCiAgICB4bWxuczpncD0iaHR0cDovL25h
bWVzcGFjZXMuZ2xvYmFscGxhdGZvcm0ub3JnL3N5c3RlbXMtcHJvZmlsZXMvMS4x
LjAiDQogICAgVW5pcXVlSUQ9Ik1FIiBQcm9maWxlVmVyc2lvbj0iMS4xLjAiIEVy
cmF0YVZlcnNpb249IjAiPg0KICAgIDxncDpEZXNjcmlwdGlvbj5Gb3J1bSBUZXN0
PC9ncDpEZXNjcmlwdGlvbj4NCiAgICA8Z3A6RGF0YUVsZW1lbnQgTmFtZT0iw6Fj
Y2VudCIgRXh0ZXJuYWw9InRydWUiIFR5cGU9IkJ5dGVTdHJpbmciIEVuY29kaW5n
PSJIRVgiIEZpeGVkTGVuZ3RoPSJmYWxzZSIgTGVuZ3RoPSIxNiIgUmVhZFdyaXRl
PSJ0cnVlIiBVcGRhdGU9InRydWUiIE9wdGlvbmFsPSJ0cnVlIiAvPiAgICANCjwv
Z3A6QXBwbGljYXRpb25Qcm9maWxlPg0Kbase 64 encoded xml without accented character -- correct
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjxncDpBcHBs
aWNhdGlvblByb2ZpbGUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAx
L1hNTFNjaGVtYS1pbnN0YW5jZSINCiAgICB4c2k6c2NoZW1hTG9jYXRpb249Imh0
dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2Zp
bGVzLzEuMS4wIGh0dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9z
eXN0ZW1zLXByb2ZpbGVzLzEuMS4wL0dQLnN5c3RlbXMucHJvZmlsZXMuMS4xLjAu
QXBwbGljYXRpb25Qcm9maWxlLnhzZCINCiAgICB4bWxuczpncD0iaHR0cDovL25h
bWVzcGFjZXMuZ2xvYmFscGxhdGZvcm0ub3JnL3N5c3RlbXMtcHJvZmlsZXMvMS4x
LjAiDQogICAgVW5pcXVlSUQ9Ik1FIiBQcm9maWxlVmVyc2lvbj0iMS4xLjAiIEVy
cmF0YVZlcnNpb249IjAiPg0KICAgIDxncDpEZXNjcmlwdGlvbj5Gb3J1bSBUZXN0
PC9ncDpEZXNjcmlwdGlvbj4NCiAgICA8Z3A6RGF0YUVsZW1lbnQgTmFtZT0iYWNj
ZW50IiBFeHRlcm5hbD0idHJ1ZSIgVHlwZT0iQnl0ZVN0cmluZyIgRW5jb2Rpbmc9
IkhFWCIgRml4ZWRMZW5ndGg9ImZhbHNlIiBMZW5ndGg9IjE2IiBSZWFkV3JpdGU9
InRydWUiIFVwZGF0ZT0idHJ1ZSIgT3B0aW9uYWw9InRydWUiIC8+ICAgIA0KPC9n
cDpBcHBsaWNhdGlvblByb2ZpbGU+DQo=the xml file in use is
<?xml version="1.0" encoding="UTF-8"?>
<gp:ApplicationProfile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://namespaces.globalplatform.org/systems-profiles/1.1.0 http://namespaces.globalplatform.org/systems-profiles/1.1.0/GP.systems.profiles.1.1.0.ApplicationProfile.xsd"
 xmlns:gp="http://namespaces.globalplatform.org/systems-profiles/1.1.0"
 UniqueID="ME" ProfileVersion="1.1.0" ErrataVersion="0">
 <gp:Description>Forum Test</gp:Description>
 <gp:DataElement Name="áccent" External="true" Type="ByteString" Encoding="HEX" FixedLength="false" Length="16" ReadWrite="true" Update="true" Optional="true" />
</gp:ApplicationProfile>The file is being loaded from a windows xp professional 32 bit system.
If I just convert the xml text of the file using
select utl_raw.cast_to_varchar2(
utl_encode.base64_encode(
utl_raw.cast_to_raw(
'<?xml version="1.0" encoding="UTF-8"?>
<gp:ApplicationProfile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://namespaces.globalplatform.org/systems-profiles/1.1.0 http://namespaces.globalplatform.org/systems-profiles/1.1.0/GP.systems.profiles.1.1.0.ApplicationProfile.xsd"
 xmlns:gp="http://namespaces.globalplatform.org/systems-profiles/1.1.0"
 UniqueID="ME" ProfileVersion="1.1.0" ErrataVersion="0">
 <gp:Description>Forum Test</gp:Description>
 <gp:DataElement Name="áccent" External="true" Type="ByteString" Encoding="HEX" FixedLength="false" Length="16" ReadWrite="true" Update="true" Optional="true" />
</gp:applicationprofile>'
))) from dual;I get the following
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPGdwOkFwcGxp
Y2F0aW9uUHJvZmlsZSB4bWxuczp4c2k9Imh0dHA6Ly93d3cudzMub3JnLzIwMDEv
WE1MU2NoZW1hLWluc3RhbmNlIgogICAgeHNpOnNjaGVtYUxvY2F0aW9uPSJodHRw
Oi8vbmFtZXNwYWNlcy5nbG9iYWxwbGF0Zm9ybS5vcmcvc3lzdGVtcy1wcm9maWxl
cy8xLjEuMCBodHRwOi8vbmFtZXNwYWNlcy5nbG9iYWxwbGF0Zm9ybS5vcmcvc3lz
dGVtcy1wcm9maWxlcy8xLjEuMC9HUC5zeXN0ZW1zLnByb2ZpbGVzLjEuMS4wLkFw
cGxpY2F0aW9uUHJvZmlsZS54c2QiCiAgICB4bWxuczpncD0iaHR0cDovL25hbWVz
cGFjZXMuZ2xvYmFscGxhdGZvcm0ub3JnL3N5c3RlbXMtcHJvZmlsZXMvMS4xLjAi
CiAgICBVbmlxdWVJRD0iTUUiIFByb2ZpbGVWZXJzaW9uPSIxLjEuMCIgRXJyYXRh
VmVyc2lvbj0iMCI+CiAgICA8Z3A6RGVzY3JpcHRpb24+Rm9ydW0gVGVzdDwvZ3A6
RGVzY3JpcHRpb24+CiAgICA8Z3A6RGF0YUVsZW1lbnQgTmFtZT0iw6FjY2VudCIg
RXh0ZXJuYWw9InRydWUiIFR5cGU9IkJ5dGVTdHJpbmciIEVuY29kaW5nPSJIRVgi
IEZpeGVkTGVuZ3RoPSJmYWxzZSIgTGVuZ3RoPSIxNiIgUmVhZFdyaXRlPSJ0cnVl
IiBVcGRhdGU9InRydWUiIE9wdGlvbmFsPSJ0cnVlIiAvPiAgICAKPC9ncDphcHBs
aWNhdGlvbnByb2ZpbGU+Edited by: Keith Jamieson on Jul 13, 2012 9:59 AM
added code tag for last base64 encoded object

Not sure if utl_i18n is already there in version prior to 11.2.0.2.
But on above mentioned version I can do the simplified method
SQL> SELECT utl_i18n.raw_to_char (
 utl_encode.base64_encode (
 xmltype (
 '<?xml version="1.0" encoding="UTF-8"?>
<gp:ApplicationProfile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://namespaces.globalplatform.org/systems-profiles/1.1.0 http://namespaces.globalplatform.org/systems-profiles/1.1.0/GP.systems.profiles.1.1.0.ApplicationProfile.xsd"
 xmlns:gp="http://namespaces.globalplatform.org/systems-profiles/1.1.0"
 UniqueID="ME" ProfileVersion="1.1.0" ErrataVersion="0">
 <gp:Description>Forum Test</gp:Description>
 <gp:DataElement Name="áccent" External="true" Type="ByteString" Encoding="HEX" FixedLength="false" Length="16" ReadWrite="true" Update="true" Optional="true" />
</gp:ApplicationProfile>').getblobval (
 NLS_CHARSET_ID ('utf8'))),
 'utf8')
 x
FROM DUAL
X
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPGdwOkFwcGxp
Y2F0aW9uUHJvZmlsZSB4bWxuczp4c2k9Imh0dHA6Ly93d3cudzMub3JnLzIwMDEv
WE1MU2NoZW1hLWluc3RhbmNlIiB4c2k6c2NoZW1hTG9jYXRpb249Imh0dHA6Ly9u
YW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2ZpbGVzLzEu
MS4wIGh0dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1z
LXByb2ZpbGVzLzEuMS4wL0dQLnN5c3RlbXMucHJvZmlsZXMuMS4xLjAuQXBwbGlj
YXRpb25Qcm9maWxlLnhzZCIgeG1sbnM6Z3A9Imh0dHA6Ly9uYW1lc3BhY2VzLmds
b2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2ZpbGVzLzEuMS4wIiBVbmlxdWVJ
RD0iTUUiIFByb2ZpbGVWZXJzaW9uPSIxLjEuMCIgRXJyYXRhVmVyc2lvbj0iMCI+
CiAgPGdwOkRlc2NyaXB0aW9uPkZvcnVtIFRlc3Q8L2dwOkRlc2NyaXB0aW9uPgog
IDxncDpEYXRhRWxlbWVudCBOYW1lPSLDoWNjZW50IiBFeHRlcm5hbD0idHJ1ZSIg
VHlwZT0iQnl0ZVN0cmluZyIgRW5jb2Rpbmc9IkhFWCIgRml4ZWRMZW5ndGg9ImZh
bHNlIiBMZW5ndGg9IjE2IiBSZWFkV3JpdGU9InRydWUiIFVwZGF0ZT0idHJ1ZSIg
T3B0aW9uYWw9InRydWUiLz4KPC9ncDpBcHBsaWNhdGlvblByb2ZpbGU+Cg==
1 row selected.which encodes and decodes properly on my system even with accented characters.

Converting XML to Spreadsheet - Problem with Accented Characters

I have a program that uses an external program to gathers user account information from Active Directory. The external program is .Net, and I execute it from my Java app, which then collects the XML output and saves it in a String variable. So far so good.
Next it parses the XML and retrieves the values for each field for each user 'record' and stores these values in a String member inside of a class I created called "User".
At the end of the process, the User class data is written to a file in XML format. Still, so far so good. However, using a text editor, any user names that have accented characters in them have an extra space character after the accented character. E.g. accented "e" becomes "e ". At least that is how it appears in the Textpad editor app that I use.
Next I have a class called "XMLToExcel", that creates a spreadsheet using Apache's POI library, reads in the XML records , and writes the values for each field into a cell. Here the name with an accented character gives the message "[Fatal Error] <file name>:2617:23: Invalid byte 1 of 1-byte UTF-8 sequence."
I'm not sure what I can to do fix this, or even where to fix it. I wouldn't mind losing the accented characted and replacing it with an un-accented one.
Any ideas? I can provide code snippets if that would help.
-John Gooch

The text looks the same in Notepad and Textpad. However, I manually added the "encoding" tag with the value of "ISO-8859-1", and the converter no longer complains about invalid characters.
I added the encoding tag to my application's output file, so the converter should not complain about it on the next run. Unfortunately, the names have been fixed in Active Directory ( the special character was there by mistake ), so I cannot do a live test to be sure that it is fix.
Thanks for the help, Duke points incoming!

Reading characters from a text file into a multidimensional array?

I have an array, maze[][] that is to be filled with characters from a text file. I've got most of the program worked out (i think) but can't test it because I am reading my file incorrectly. However, I'm running into major headaches with this part of the program.
The text file looks like this: (It is meant to be a maze, 19 is the size of the maze(assumed to be square). is free space, # is block, s is start, x is finish)
This didn't paste evenly, but thats not a big deal. Just giving an idea.
19
5..................
And my constructor looks like follows, I've tried zillions of things with the input.hasNext() and hasNextLine() to no avail.
Code:
//Scanner to read file
Scanner input = null;
try{
input = new Scanner(fileName);
}catch(RuntimeException e) {
System.err.println("Couldn't find the file");
System.exit(0);
//Set the size of the maze
while(input.hasNextInt())
size = input.nextInt();
//Set Limits on coordinates
Coordinates.setLimits(size);
//Set the maze[][] array equal to this size
maze = new char[size][size];
//Fill the Array with maze values
for(int i = 0; i < maze.length; i++)
for(int x = 0; x < maze.length; x++)
if(input.hasNextLine())
String insert = input.nextLine();
maze[i][x] = insert.charAt(x);
Any advice would be loved =D

Code-tags sometimes cause wonders, I replaced # with *, as the code tags interprets # as comment, which looks odd:
******...*.........To your code: Did you test it step by step, to find out about what is read? You could either use a debugger (e.g., if you have an IDE) or system outs to get a clue. First thing to check would be, if the maze size is read correctly. Further, the following loops look odd:for(int i = 0; i < maze.length; i++) {
 for(int x = 0; x < maze.length; x++) {
 if (input.hasNextLine()) {
 String insert = input.nextLine();
 maze[x] = insert.charAt(x);
}Shouldn't the nextLine test and assignment be in the outer loop? And assignment be to each maze's inner array? Like so:for(int i = 0; i < maze.length; i++) {
 if (input.hasNextLine()) {
 String insert = input.nextLine();
 for(int x = 0; x < insert.size(); x++) {
 maze[i][x] = insert.charAt(x);
}Otherwise, only one character per line is read and storing a character actually should fail.

Tagged text unexpected results

I'm having trouble with InDesign 6 tagged text. Here is the tagged text file I'm importing into a series of linked boxes on an InDesign Page.
<ASCII-MAC>
<pstyle:title>Access to Health
<pstyle:author>Donatelle
<pstyle:sku_k>14173278
<pstyle:bc_k>µ14173278CÄ
<pstyle:sku_spot>14173279
<pstyle:bc_spot>µ14173279KÄ
When I import this, the lines with the extended character set fail (µ and Ä). There is no error message.
If I strip out those two characters the file imports correctly.
I've tried changing the encoding to UNICODE-MAC and ANSI-MAC but neither of those choices worked.
What should I do to get this to work. I need the special charactes because they are part of a barcode.
Oh, one more thing. If I have this open in a text editor and copy and paste the data (minus the paragraph style indicators), it works fine. It's just the import that fails.
Thanks in advance.
Dennis
(frustrated in Chicago)

In reply to my own question, here's what I've discovered.
Saving a TextWrangler file as Unicode failed. In fact, InDesign imported the file as straight text so I even saw the tags.
What finally worked for me as this.
I left the encoding at <ASCII-MAC> and, using TextWranger, I saved it in (Western (Mac OS Roman)) encoding. Now the file imports correctly.
Thanks, Jongware, for pointing me in the right direction.
Dennis

Tagged text import issues

I have had some issues with importing tagged text. In my workflow i get some data converted to tagged text, no problems, special characters are also converted to ASCII entities.
Everything works on my machine, but as soon as it is imported on another machine, the special characters are gone.
I have located the issue, that my entities are lowercase (e.g. ë = <0x00eb>), and by making it uppercase (<0x00EB>) it works.
What can be the difference on the machines? Is it an InDesign thing, or is it a CPU thing? The only difference on the machines are that mine is a Mac with intel processor, and the other is a G5.

Oops -- the smiley face in the code should be changed to semicolon close angle (greater than sign). Jim

Align on comma tabs with tagged text in ID CS2

We have a problem generating tabs aligned on comma with tagged text in CS2. It works for other characters (like dot for example). Any attempt until now leads to an Indesign CS2 crash at import. The problem seems to be that the comma is also the separator for the parameters of the pTabRuler tag. In order to find a suitable syntax we have tried the following (without success) : 1) use the syntax from the documentation (tagged text user guide) 2) do some roundtripping (ie export and place the same tagged text. This works in CS3, but the CS3 syntax is version 5 while CS2 is version 4) 3) use an hexa definition of the comma <0x002C> similar to the "Indesign tags for special characters 4) upgrade to the last CS2 update (4.0.5) Of course one could say we just have to upgrade to CS3 and case is solved. As we have a lot of scripting to convert between CS2 and CS3, we had like to know first if there is a solution for CS2. b Here is a sample of the tagged text we cannot import in CS2: <ASCII-WIN> <Version:4><FeatureSet:InDesign-Roman><ColorTable:=<Black:COLOR:CMYK:Process:0,0,0,1>> <DefineParaStyle:NormalParagraphStyle=<Nextstyle:NormalParagraphStyle>> <ParaStyle:NormalParagraphStyle><pTabRuler:113.38582677165356\,Char\,\,\,0\,\ ;> 1,23 12,3 <pTabRuler:><ParaStyle:NormalParagraphStyle><pTabRuler:113.38582677165356\,Char\,\,\,0\ ,\ ;> 123<pTabRuler:> b Here is the export of the same in CS3 that works in roundtripping: <ASCII-WIN> <Version:5><FeatureSet:InDesign-Roman><ColorTable:=<Black:COLOR:CMYK:Process:0,0,0,1>> <DefineParaStyle:NormalParagraphStyle=<Nextstyle:NormalParagraphStyle>> <ParaStyle:NormalParagraphStyle><pTabRuler:100\,Char\,\\\,\,0\,\ ;> 1,23<0x000A> 12,3 <pTabRuler:><ParaStyle:NormalParagraphStyle><pTabRuler:100\,Char\,\\\,\,0\,\;> 123<pTabRuler:> Note : tab align on comma is the way it should be in continental europe for displaying prices for example. Any hint would be very appreciated. Emmanuel

We have a problem generating tabs aligned on comma with tagged text in CS2. It works for other characters (like dot for example). Any attempt until now leads to an Indesign CS2 crash at import. The problem seems to be that the comma is also the separator for the parameters of the pTabRuler tag. In order to find a suitable syntax we have tried the following (without success) : 1) use the syntax from the documentation (tagged text user guide) 2) do some roundtripping (ie export and place the same tagged text. This works in CS3, but the CS3 syntax is version 5 while CS2 is version 4) 3) use an hexa definition of the comma <0x002C> similar to the "Indesign tags for special characters 4) upgrade to the last CS2 update (4.0.5) Of course one could say we just have to upgrade to CS3 and case is solved. As we have a lot of scripting to convert between CS2 and CS3, we had like to know first if there is a solution for CS2. b Here is a sample of the tagged text we cannot import in CS2: <ASCII-WIN> <Version:4><FeatureSet:InDesign-Roman><ColorTable:=<Black:COLOR:CMYK:Process:0,0,0,1>> <DefineParaStyle:NormalParagraphStyle=<Nextstyle:NormalParagraphStyle>> <ParaStyle:NormalParagraphStyle><pTabRuler:113.38582677165356\,Char\,\,\,0\,\ ;> 1,23 12,3 <pTabRuler:><ParaStyle:NormalParagraphStyle><pTabRuler:113.38582677165356\,Char\,\,\,0\ ,\ ;> 123<pTabRuler:> b Here is the export of the same in CS3 that works in roundtripping: <ASCII-WIN> <Version:5><FeatureSet:InDesign-Roman><ColorTable:=<Black:COLOR:CMYK:Process:0,0,0,1>> <DefineParaStyle:NormalParagraphStyle=<Nextstyle:NormalParagraphStyle>> <ParaStyle:NormalParagraphStyle><pTabRuler:100\,Char\,\\\,\,0\,\ ;> 1,23<0x000A> 12,3 <pTabRuler:><ParaStyle:NormalParagraphStyle><pTabRuler:100\,Char\,\\\,\,0\,\;> 123<pTabRuler:> Note : tab align on comma is the way it should be in continental europe for displaying prices for example. Any hint would be very appreciated. Emmanuel

Soft Returns in Tagged Text

Our Pindar AgilityCMS content managment system flows text to an InDesign page using a special PlugIn.
Some characters are stored natively (store an "a", get an "a" on the page), while other special characters are stored using Tagged Text or Unicode. A return can be either <0x000D> or \u000D. This is especially useful because we can output through one of four "channels".... InDesign, Quark, HTML or as entered in the content manager. The return can now be \p in Quark or in HTML. A non-breaking space, for example, can be \u00A0 in the InDesign channel,   in HTML or <\!s> in Quark. When we insert the "special character" in the Data Editor of our content system, it might be displayed as [sp], but it will resolve correctly regardless of which channel we publish to.
The problem is that unlike Quark, Adobe does not provide for a "soft return" or forced line break. Sure, you can type one from the keyboard with shift+return, and purists will argue that you'd never want to store a soft (discretionary) return in any type of tagged text or a content management system. However, all our text is set flush left, ragged right, and we frequently want to force line breaks for readability, and do so consistently.
Instead of:
On Sale Now Buy One, Get
One Free
we always want
On Sale Now
Buy One, Get One Free
Again, this is a problem whether you store your data in simple tagged text files, or if you bring it in via a complex PlugIn, as we do.
There are many, many threads on this site and elsewhere that discuss this shortcoming. Does Adobe plan to support Soft Returns in Tagged Text with some kind of special tag?

Your question is predicated on some false assumptions, and I'm afraid Peter, Peter, and Stix didn't quite pick that up in their replies. (This gives me pause since normally they're all very detail-oriented).
As I told you when you posted in the thread from 2009, "InDesign Tagged Text supports forced line breaks just fine."
You write:
Does Adobe plan to support Soft Returns in Tagged Text with some kind of special tag?
Adobe's import mechanism does indeed support soft returns. There's no need to speculate on Adobe's plans, which is the direction the other replies went to.
With that in mind, let's move to your actual question:
Our Pindar AgilityCMS content managment system flows text to an InDesign page using a special PlugIn.
Some characters are stored natively (store an "a", get an "a" on the page), while other special characters are stored using Tagged Text or Unicode. A return can be either <0x000D> or \u000D. This is especially useful because we can output through one of four "channels".... InDesign, Quark, HTML or as entered in the content manager. The return can now be \p in Quark or in HTML. A non-breaking space, for example, can be \u00A0 in the InDesign channel,   in HTML or <\!s> in Quark. When we insert the "special character" in the Data Editor of our content system, it might be displayed as [sp], but it will resolve correctly regardless of which channel we publish to.
I think you need to address this question to your support channel for Pindar AgilityCMS. Indeed, in IDTT <000A> represents a shift-return. Here's a screenshot of a test textframe:
and when exported to InDesign Tagged Text, it produces:
<ASCII-MAC>
<Version:7><FeatureSet:InDesign-Roman><ColorTable:=<Black:COLOR:CMYK:Process:0,0,0,1>>
<DefineParaStyle:NormalParagraphStyle=<Nextstyle:NormalParagraphStyle>>
<ParaStyle:NormalParagraphStyle>Paragraph one
<ParaStyle:NormalParagraphStyle>Paragraph two<0x000A>P2/Line two
I presume you have tried <0x000A> as discussed in the prior thread.
I suppose it's remotely possible this is a Mac/PC issue, because the two operating systems do you different line break characters.
Anyhow, once again, your criticism of InDesign and Adobe is false and unfair. And if you have a problem with a 3rd party plugin, those are really the people you need to talk to.
Still, it might be wise to get it working with plain File > Place. Try testing my above IDTT file. Or exporting your own from a sample textframe like the one I used.

MojikumiElement Tagged Text export junk in InDesign CS6

Hello,
Our InDesign Tagged Text exports have suddenly been infested with large amounts of the following code, repeating over and over. We've managed to munge it out on the other side of the process, but can't figure out how it got there in the first place. It's making the files take much longer to process, but otherwise seems to have no effect whatsoever. My understanding is that I shouldn't be seeing anything Mojikumi related unless I'm using the Japanese version of ID/CS, or embedding Japanese characters.
Any ideas why this is happening and how to make it stop?
<snip>
<ASCII-MAC>
<Version:8><FeatureSet:InDesign-Roman><ColorTable:=<Black:COLOR:CMYK:Process:0,0,0,1>>
<DefineMojikumiStyle:kMojikumiDefaultName1=<MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><M ojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiEl ement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0 ,0,0,0><MojikumiElement:0,0,0,0,0><MojikumiElement:0,0,0,0,0>>
</snip>
TIA and much appreciated

Hi Steve,
I created a book in InDesign for traditional print. Now I need to convert it
to a epub file for use on a Kindle¹.
So my workflow is just in InDesign CS6, then I create a new document in the
book¹ format. Then I import the InDesign docs into the book¹ dialogue
window. You can choose the preflight book¹ option in the book¹ dialogue
box and choose to see the errors as a PDF, which is what I¹ve been doing. I
have errors on every page of the proposed epub¹ file.
If I then drag that epub file to my Kindle preveiwer, it immediately says
that it failed to compile the book file¹, and there is nothing shown.
Thanks,
Nick.

Importing Adobe Tagged Text

Hello,
So here's what's happening…
I've installed a Wordpress plugin that exports posts as Adobe Tagged Text.
When I import, the text still shows up marked up with tags, just as it looks in the .txt file:
<ANSI-MAC>
<DefineParaStyle:NormalParagraphStyle=<Nextstyle:NormalParagraphStyle><cColor:Registration ><cSize:10><cLeading:11><pFirstLineIndent:12><cFont:Times New Roman>>
<ParaStyle:NormalParagraphStyle>This <cTypeface:Italic>is<cTypeface:> a <cTypeface:Bold>test<cTypeface:>
<ParaStyle:NormalParagraphStyle>Test paragraph
<ParaStyle:NormalParagraphStyle>Testing this out
Does it have something to do with the first line of code, <ANSI-MAC>?
Regards,
Eric

You're using a very old InDesign workflow which I've never used. But it's referenced in Olav Kvern's and David Blatner's excellent "Real World InDesign" (I'm looking at the CS4 edition).
On page 235, it reads, "The first characters in a tagged text file must state the character encoding (ASCII, ANSI, UNICODE, BIG5, or SJIS), followed by the platform (MAC or WIN). So the typical Windows tagged text begins with <ASCII-WIN> , and the Macintosh version begins with <ASCII-MAC> ."
It looks to me like it should work. Have you tried exporting some tagged text from InDesign to see how it looks? File > Export > Adobe InDesign Tagged Text.

Need help with creating text anchors with tagged text.

Can anyone tell me how to determine the correct value for a "Hyperlink Dest Index" value?
I have a script which creates a tagged text file that specifies about about 280 pages of tables (thank heavens for autoflow) , and would like to add live links between different parts. I can create a text anchor and a hyperlink to it in InDesign. The tagged text definition for the link source is simple and in-line and exports and imports nicely as tagged text. However, I see that all the link destinations, aka text anchors, are all exported at the very end of the tagged text files as global definitions, and thier location iin the document is specified by the property HyperlinkDestIndex. However, I can't figure out how to set this value progammatically. I've spent over an hour exporting links, and it sure isn't anything as obvious as character index in the story.
Any advice appreciated,
Read Roberts

Read, I'm not sure the following is going to help you. It works for external hyperlinks, but you want internal links, right? Anyway, it might give you some clues.
A funny thing: I was reviewing some script where I got links to work, and I spotted a tiny coding error. Links seemed to be defined by two separate identifiers: a "link name", which is what appears in Edit Hyperlink dialog, and a "Dest Key", which seems to be a simple increasing number. However, due to aformentioned coding error, the dest keys between the actual link and its definition were off by '1', so there was no way that ought to have matched. But it still worked! So "Dest Key" is a red herring ...
As far as I understand, it works like this (for hyperlinks): in your text, you have
HplName -- this is actually the 'title' that appears in the Hyperlink palette
HplDest -- this is the 'internal name'
DestKey. Hm. Perhaps you could omit this, per above obsvn.
CharStyleRef, the name of the auto-applied style
Hid -- seems to be always '0'
HplOff: the "offset" from this entire command to the start of the hyperlink, in InDesign characters.
HplLen: the "length" from the hyperlinked text, in InDesign characters.
and in the list of 'proper' definitions, those that appear at the very end of your file:
HplDestDfn -- the internal name again
DestKey -- see above
HplDestUrl -- finally! A real URL! (But you must escape lots of characters, such as the forward slash and colon.)
Hid -- again, always seems to be '0'.
Some of these items are perhaps optional, but experimenting with what may be left out only lead to frustration The Tagged Text guide is far from complete, as I'm sure you already knew.
As noted, some (or all) of the named items need a backslash escape for a few characters, but I can't find a definitive way to determine in advance what is 'good' and what is 'not good'.
The following script creates a Tagged Text file with a couple of working hyperlinks in it -- I don't know if this is of any help for your internal links.
var hyperlinkDest = [];
var text = "This is some text with a link [http://www.jongware.com/idjshelp.html] and another one [http://forums.adobe.com/thread/1014617?tstart=0] in it.";
var tagtext = text.replace (/\[(.+?)\]/g, function (full, match)
 return makelink (match, 'title:'+match, match, match);
// When done processing plain text, add the destinations at the end:
tagtext += hyperlinkDest.join('');
tagFile = File(Folder.myDocuments+'/__tmp.txt');
if (tagFile.open('w') == false)
 alert ("Unable to create temporary file!");
 exit();
if (File.fs == "Windows")
 tagFile.write ("<ASCII-WIN>\n");
else
 tagFile.write ("<ASCII-MAC>\n");
tagFile.write ("<dcs:HYPERLINK=<cu:1>>\n");
 tagFile.write (tagtext);
tagFile.close();
// 'text' is the actual text that will be clickable
// 'title' is what will appear in the Hyperlinks palette
// 'name' is the internal name in the Edit Hyperlink dialog
// 'url' is the actual URL that will be linked to
function makelink (text, title, name, url)
 var destkey = hyperlinkDest.length;
 // In URL you must escape forward slashes and colons
 // .. and some other characters as well, by the way. There seems to be no list
 url = url.replace(/\//g, '\\/').replace(/:/g, '\\:');
 hyperlinkDest.push ('<HplDestDfn:=<HplDestName:'+name+'><DestKey:'+String(destkey)+'><HplDestUrl:'+url+'><Hid:0>>');
 return '<Hpl:=<HplName:'+title+'><HplDest:'+name+'><DestKey:'+String(destkey)+'><CharStyleRef:HYPERLINK><Hid:0><Brdrv:0><HplOff:0><HplLen:'+String(text.length)+'>>'+text;

Problems with input accented characters after moving JInitiator to JDK 1.5

After upgrading from JInitiator 1.3.1.18 to JDK 1.5.0_06 (jdk plugin in IE), the input of accented characters (in our case portuguese) isn't working anymore in text areas on the forms (Forms 10g).
So, if you push first the "´" key and then the "a" key, you should get as result "á" (worked correctly with JInitiator), but after upgrading to JDK 1.5 you will get simply a letter "a".
Pressing Alt + 160 shows correctly "á".
Somebody can give a clue about this problem please?
Downgrading again to JInitiator is no option for us, as we need a more modern JVM (for a Dicom viewer applet we developed), and IE crashes if you have an Oracle form running with JInitiator, and then try to open another IE page with an applet requesting JVM 1.5 ...
Thanks a lot for your comments.
Alberto A.Smulders
HostDat Lda. - Portugal

In IE, the server must be in the Trusted Sites list & the security for Trusted Sites set to low
Tools -> Internet Options
Security Tab
Sites button
Add all Forms servers, or use a wildcard to get your entire domain. If you are not using SSL, uncheck the "Require server verification (https:) for all sites in this zone"
Set the Security Level for this zone to Low. If the slider bar is not there, click the Default Level button, then slide the security setting to low.

Accented characters in tagged text

Similar Messages

Maybe you are looking for