Tagged text export unicode

hi,
is there any possibility to set the ITaggedTextImportPreferences before exporting to a tagged text file with an IExportProvider?
i need to export it in Unicode, but default is ASCII.
best regards

As far as I can tell, this isn't a new bug in as much as InDesign CS3, CS4, CS5 and CS5.5 (Mac) all exhibit the same problem exporting soft-returns in Unicode encoded Tagged Text where they are replaced with hard returns on import. Unfortunately it appears that we may be the only ones that care and thus it's unlikely that Adobe will fix it (unless someone adopts it as a JDI bug).
Update: after testing some more it appears this is an export bug for Mac OS-only. In other words, if you use a PC to export a story that contains soft-returns to Tagged Text (Unicode), the soft-returns are preserved when placing into a document using a Mac. And vice-versa, using a Mac to export a story with soft-returns to Tagged Text (Unicode) and then placing this into a document using a PC exhibits the same substitition of soft-returns for hard-returns.
Message was edited by: Caleb Clauset

Similar Messages

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.

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.

Exporting Table from Indesign to tagged text.

Hi, all! I need to export table from InDesign to tagged text by the script. I found ExportAllStories.jsx in samples. It's good example but I have some questions 1. In my document more then one table and I need to export only some of them. So, how can I export only one of them? May be Tables have some "labels" or something other differential sign? 2. How can I ser encoding type of distanation file (by the default InDesing set <ASCII-WIN>, but I'm need to set <Unicode>).

Edit>InCopy>Export All Strories.
Open the INDD in InCopy.
This assumes everyone involved has access to the files.

Exporting Text as InDesign Tagged Text in CS3

Hello All,
I am facing a problem exporting the Text from InDesign Document as InDesign Tagged Text. It use to work properly in CS2. But in CS3 the IExportProvider interface CanExportThisFormat() always returns false for the format name "Indesign Tagged Text".
InterfacePtr<IPMStream>filetream(StreamUtil::CreateFileStreamWriteLazy(sysfile));
iiExportProvider->ExportToStream(filetream, doc, iselMgr, formatNameOfInterest, kSuppressUI);
If the CanExportThisFormat() function is ignored and directly tried to export with the above ExportToStream() function it still fails to export into stream.
Has the way to export the InDesign Tagged Text been changed in CS3.
Can any one whos tried this please help as its urgent.
Thank you in advance.
Regards
Farzana.

Hi Vikas
I export files from Photoshop as png's at 72 dpi.
Here is our current holding page. http://www.iheartmylife.co.uk/ All the text on this page has been loaded in as png's from Photoshop along with the image. As you can see none of it is as sharp as it could be.
Many thanks for your assistance.
James

How do I import an InDesign tagged text file into multiple pages and export as .ps or .pdf using Jav

I have an InDesign tagged text file I've translated from .xml. I need to automate the following steps:
1 - access specific InDesign template (eg. ABC_template.ind)
2 - import tagged text file into InDesign
3 - autoflow text to END of document (normally around 3-5 pages)
4 - save document as either .ps or .pdf file
5 - where the input file stub name matches the output stub name (eg., OrigName.txt outputs as OrigName.pdf).
I would like to completely automate this whole process using JavaScript (because I don't know anyone that knows AppleScript). I've automated the first part using a perl script. I've been trying to find sample snipits of JavaScript that would do one or more of the items listed above, but am having a hard time finding what I need.
Please, I'm desperate!! Can any of you InDesign scripting guru's out there help me??
Thanks in advance!!
LindaD

Hi Linda,
I might be able to help you out. You can contact me by email (click on my user name for the address), or if you post your email here.

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.

InDesign Tagged Text for Cross-reference Entries

I'm transforming XML to InDesign Tagged Text. The XML has index codes. For regular page entry type entries I'm having no problem outputting to the appropriate InDesign Tagged Text markup. However, I cannot figure out how to code cross-reference type entries. The document "Using Adobe InDesign Tagged Text CS5 Tagged Text" is extremely limited in its usefulness as it does not list all possible values for tag type tags, etc. I've tried dozens of tag combos and guesses at values. None have worked. Also, for some reason, even though I can create a "See x" type reference in the InDesign document, when I export to InDesign Tagged Text to look at the code, those tags are not included in the export.
Does anyone have a more definitive list of possible IDTT index tag values?

I have been exporting various things to IDTT to see what the result would be, with nothing really helpful as a result. I'll try hyperlinks, but reading of the Adobe guide to InDesign Tagged Text and also just looking at the InDesign scripting object model leads me to believe that there must be specific tags to create index-specific cross-reference tags.

Tagged Text in InDesign 5.5

I posted this in the general discussion and was pointed to scripting.
I use tagged text in the files I place
in InDesign. For example,
<cn>This is the chapter number
<ct>This is the chapter title
<cst>This is the chapter subtitle
<bt>This is the beginning of the body text
<ah>This is an A-level head
and so on. In PageMaker, there was a checkbox in the "place"
dialogue box named "Read tags." I checked that, and when I placed the file in the template (in which I had the styles defined), the whole chapter appeared with the formatting I wanted for each style. I could use anything I wanted for a text tag, as long as it was in <>. If it wasn't defined in the PM document, it came in in the basic style but could be formatted on the fly in PageMaker.
I can't find the equivalent checkbox in InDesign. I can't believe it is no longer there, but I can't find it. There is a lot online about exporting tagged text, but where, oh where, is my checkbox for placing tagged text? If someone knows where it is, I'd be very grateful. It seems that such a great (and incredibly easy) function shouldn't be gone.
Thanks (and apologies to those who already saw this in the general discussion),

Well, not quite four hours, but yes, I couldn’t get it to work. For one thing, I wasn’t sure about the header to use, since I’m on Windows. I used <ASCII-WIN>
<Version:7><FeatureSet:InDesign-Roman>
<pstyle:ah>
<pstyle:ah_bib>
<pstyle:bib>
<pstyle:bh>
<pstyle:bl>
<pstyle:bl_ext>
<pstyle:bt>
<pstyle:bt_fl>
<pstyle:cn>
<pstyle:ct>
<pstyle:cst>
<pstyle:epi>
<pstyle:epi_source>
<pstyle:ext>
<pstyle:ext_1stpara>
<pstyle:ext_2dpara>
<pstyle:fn>
<pstyle:fn_2dpara>
<pstyle:poem>
<pstyle:poem_1st>
<pstyle:poem_last>
I added the above to one of my tagged text files and saved it from Word as .xml. When I brought it into InDesign, I got a sidebar with a couple of entries, one of which expanded to several “parts.” There was nothing in the template until I double clicked (I think that’s what I did; maybe right clicked) one of those sidebar items and placed the text. It came it as one long file with no returns and no formatting. The tags remained as text.
I came back to the Internet and found an article by Peter Kahrel entitled “A GREP queries manager.” OK, I admit I didn’t understand much of it, but the notion of chaining queries sounds good.
I did the Lynda.com tutorials when I was first ordered to make the change to InDesign (last month). I found them very helpful, but if they have anything on this, I missed it. Maybe I was too busy figuring out how to turn pages, find things on the pasteboard, and determine what character styles are and why I have to use them J
“Not hard”? Um, what is the etiquette for asking you to do this task for me? I’m assuming that once I had a script in hand, I could add new paragraph styles by mimicking the entries. Is that right? Would it really be as easy as opening all the files and running the script to make the changes throughout? That sounds wonderful. Even running it on one at a time would be a great improvement. Do I need to contact you off list, and, if so, how?
Thanks . . . yet again.

Tagged text not recognised

First experiments at moving content between applications. I exported a simple IDD file as tagged text to see what it looked like, replaced the content with a couple of sentences of my own using existing styles, File > Place ... and IDD places the tagged file as plain text, including the tags: so it starts anglebracket ASCII-MAC anglebracket. I hope there's something very simple I'm doing wrong!
IDD CS5 on Snow Leopard, by the way. Thanks in advance for any help.

Saving an ASCII file with any random text editor may change the line endings. InDesign is particularly picky about this; see http://forums.adobe.com/thread/746804 for a series of wild experimenting.
I found the best, nay, the Best text editor to wrangle with tagged text is TextWrangler. Checking and altering the line endings is extremely straightforward with that.

Tagged Text and Hyperlinks

I am attempting to create a document with two sections that are generated as tagged text via a database. This has worked for years. Now the client wants me to link a name in the first section with the appropriate name/description in the second section. The file will then be saved as a PDF. Seems pretty straight forward.
Unfortunately, I cannot seem to get the right set of commands to make this work with tagged text. Whenever I want to do something new with tagged text I would just build a sample manually and then export the document to tagged text. From there it is pretty straight forward to reproduce.
When I try this with my current sample, the exported files do not contain any code for the linking. The destination text appears to have some addition tags that reference them as the destinations, but the source text has no additional tags. I tried Adobe support, but they just said sure it works, but since you are doing scripting we can't help! I haven't even gotten that far yet! I even sent them the sample files and they ignored them.
Has anyone done this or proven that it can't be done?

Marc,
I'm a newbie with InDesign. I'm trying to do something similar as you are. And I'm not having much luck with Hypertext links. Have you made and progress? I've just converted some jobs from FrameMaker to InDesign. (My customer's request). I had much better luck with FrameMaker.
Thanks,
Roger

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

Linked Adobe Tagged Text files importing without styles

I have several data-heavy weekly publications where suddenly, the link to all Adobe Tagged Text format files have the proper paragraph styles and character styles stripped on being placed. I'm aware of the default settings issue, where you deselect all and make sure the character styles is none, and that does not seem to be the issue. Specifics are
Working in CS 5 (Version 7.0.4)
The Adobe Tagged Text format files are exported from Excel spreadsheets
The InDesign documents have links to the Adobe Tagged Text format files, and Update Link is used inside InDesign to update the text when the file is exported from the spreadsheet.
When the publications are opened on my workstation, ALL files linked to Adobe Tagged Text files are not imported correctly, they revert to the Basic Paragraph style.
These are not new documents I'm designing or new Adobe Tagged Text files, this is part of a production process that has worked without issue for years.
When the same documents are opened on another workstation, and Update Links used, they come in perfectly, so it doesn't seem to be a document or file corruption problem, but a problem with my environment or ID settings.
It's not one specific document or file, it is every single document that has a link to an Adobe Tagged Text file (and we have lots, I tried several!)
I've opened the text files in the text editor to check them, but as I mentioned: same document, same files, I'm the only one who can't update without stripping out the styles.
Thanks! Nancy

Hi, Peter! Thanks for the response. Yes, it's really Tagged Text. See below. After exporting from the spreadsheet and database, opening the document in InDesign, and selecting update link, we do no editing in InDesign after the fact because everything is already setup exactly as we want it with the Tagged Text format.
I have literally hundreds of these among several different documents, updated weekly, mainly dealing with prices and numbers. Every one of the links to Tagged Text format files in every publication now strips out the Tagged Text paragraph style and character style formatting on Update Link on my workstation only. On my other two workstations, the links update without issue, and everything is correct in the final document.
So I'm beginning to think I need to look at rebuilding something, maybe as Joel said, replacing preferences. I keep looking for a workstation or ID option that might effect this.
<ANSI-WIN>
<vsn:6><fset:InDesign-Roman><ctable:=<Black:COLOR:CMYK:Process:0,0,0,1>>
<dps:Pnl Comp\:Pnl Comp \$Numbers=<Nextstyle:Pnl Comp\:Pnl Comp \$Numbers>>
<dps:Pnl Comp\:Pnl Comp Bold \$Numbers=<BasedOn:Pnl Comp\:Pnl Comp \$Numbers><Nextstyle:Pnl Comp\:Pnl Comp Bold \$Numbers>>
<dps:Pnl Comp\:Pnl Group \$Numbers=<BasedOn:Pnl Comp\:Pnl Comp \$Numbers><Nextstyle:Pnl Comp\:Pnl Group \$Numbers>>
<pstyle:Pnl Comp\:Pnl Comp Bold \$Numbers> $302 $302 $278
<pstyle:Pnl Comp\:Pnl Group \$Numbers> 203 202 211
<pstyle:Pnl Comp\:Pnl Group \$Numbers> 456 458 393

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

How can I place Tagged Text in InDesign

I use tagged text in the files I place
in InDesign. For example,
<cn>This is the chapter number
<ct>This is the chapter title
<cst>This is the chapter subtitle
<bt>This is the beginning of the body text
<ah>This is an A-level head
and so on. In PageMaker, there was a checkbox in the "place"
dialogue box named "Read tags." I checked that, and when I placed the file in the template (in which I had the styles defined), the whole chapter appeared with the formatting I wanted for each style.
I can't find the equivalent checkbox in InDesign. I can't believe it is no longer there, but search as I do, I can't find it. There is a lot online about exporting tagged text, but where, oh where, is my checkbox for placing tagged text? If someone knows where it is, I'd be very grateful.

John Hawkinson wrote:
For reference SuzeiQ's thread in the scripting forum is here: http://forums.adobe.com/thread/908213.
Though I think it really wasn't a scripting question :-).
Also, Peter, post your script!
I presume that last was directed to Mr. Kahrel...

Tagged text export unicode

Similar Messages

Maybe you are looking for