Tagging Text in a document

Hey all,
I haven't used swing in a while. Here is my problem:
A user can view a document at a time. The document is tagged with <begin><end> tags. I would like to process the document and show text between <begin><end> highlighted. The user can remove any tagged text by right clicking and clear. Also the user can add new tags by simply highlighting.
e.g.
The quick <begin>brown fox<end> jumped over the <begin>lazy dog<end>.
brown fox and lazy dog would be pre-highlighted when the doc is loaded.
Has anyone done something like this before in swing? Any help would be great to get started. Thanks.

1. <begin><end> is not proper XML and is thus a bad idea. Use <highlighted></highlighted>
2. Better yet, just use the html tags for setting the background color (check out )
user12374594 wrote:
Hey all,
I haven't used swing in a while. Here is my problem:
A user can view a document at a time. The document is tagged with <begin><end> tags. I would like to process the document and show text between <begin><end> highlighted. The user can remove any tagged text by right clicking and clear. Also the user can add new tags by simply highlighting.
e.g.
The quick <begin>brown fox<end> jumped over the <begin>lazy dog<end>.
brown fox and lazy dog would be pre-highlighted when the doc is loaded.
Has anyone done something like this before in swing? Any help would be great to get started. Thanks.Edited by: tjacobs01 on Jul 18, 2011 11:08 AM

Similar Messages

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.

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.

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

Importing URLs using tagged text

I'm trying to import tagged text with URLs into InDesign. InDesign sees the links, but does not seem to know that the links are URLs (rather than text anchors or page links). I have nearly 1500 hyperlinked pieces of text I want to import, so I can't manually create Destination Definitions for all of them. When I try to send definitions in using tagged text, InDesign (CS2) crashes. Any help very much appreciated.

There are many ways of "tagging" information in an InDesign document. For what you're doing, I'd suggest a unique paragraph style used only for this purpose, then you can search for text in it and use the contents.
Dave

Tagged text in Linked Textframes

Hello,
I have an InDesign document with a textframe linked on multiple pages. inside that textframe, there's tagged text. I can retrieve the XMLElement objects and the InsertionPoint (xmlElement.getStoryOffset()) in java. Now all I need to do is to know what page each tagged text is on.
Is there any way to do this? I've been looking for hours, and can't find a way

I'm sorry, i don't explaind my situation very well.
With InDesign, i have a program that interop with and populate some textframes on a template.
I want to fill a textframe, and if the textframe have an overflow with the text, i want the textframe resize automaticly and shift the next textframe :
Actually, when a textframe is overflows with text (We can see it on the picture with the little red square on the first bloc of textframes), the textframe is not resized and the next textframe is not shifted to the bottom.
What i want is when the textframe is overflows with text, InDesign resize the textframe in height to fill all the text, and shift the next textframe to bottom of the first textframe.
Sorry for my confuse explanations.
Best Regards.

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 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 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

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

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.

Hyperlinks in tagged text

Good morning,
I'm building tables of contents programmatically and save them as tagged text for importing into InDesign (CS3) for later export to PDF.
That works fine for bookmarks and hyperlinks to web sites but not for links to other PDF documents. Why?
In fact if you create bookmarks, http://hyperlinks and file://links in InDesign, they work in PDF, but when you export it as tagged text and then re-import that same tagged text again, the first two still work but the file://links are lost. Why?
Another funny point: file://links insist on *.indd targets even though the resulting PDF file will look for *.pdf one. Why?
Thanks for any enlightenment, Texane02

So it does. It also drops it if you export in GB 18030. I would file a bug report:
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Only workaround I can think of would be to enter some other unique character (maybe |?) and find/replace it in ID after bringing in the tagged text.
Ken
Hold on, I tried exporting tagged text and then bringing it back in. It's not dropping the forced line break. It's exporting it as a single Line Feed (hex 0a). And it interprets that as a forced line break when importing back in. My text editor ignores Line Feeds. I had to look at it in a hex editor to see the 0a.
I don't know if that helps any. However you're producing the tagged text, you would need to be able to make it enter a line feed without the carriage return.
Ken

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.

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.

How I generate index markers using Applescript and tagged text!

One of the challenges I've faced in automating the book making process using Applescript with inDesign is that there don't seem to be any AS commands for making new index markers (anyone please correct me I if I'm wrong about this).
I've tried various js scripts which do an OK job, but they don't make the actual native markers. This means you have to wait until the book (consistiing of multiple ID files) is complete (so that all the page numbers have been established) to generate the index.
Recently, I read a tweet from someone with a link to a technique which uses tagged text and find and replace with GREP to edit the tags, inserting the tagged text index tags in the text file and then re-placing the text file in the ID page. In itself, this works great. But I'm dealing with literally thousands of separate text frames, none of them connected in a story.
The books typically consist of around 1200 pages with almost that many people, each of whose names I need to index with "Lastname, Firstname" references. And those particular strings don't (can't) appear anywhere on the pages. There will also be about 50 ID files all combined into one book. So it is imperative that I have ID generate the native index markers. To help keep things straight and efficient, I'm creating separate small text frames to hold the lastname, firstname strings. I created an object style for these frames which sets the attributes to "nonprinting", and I place the frames in the margin.
Then I realized that I don't actually have to have ID export the tagged text files for each. I exported one prototype and copied its tags to properties in my script, and then I concatenate them with the respective list item values I import from the database.
At the proper point in the page building script, I tell "textwrangleer" to make a new document, set its contents to the index string for the current record, save it to disk, overwriting the previous one, and then tell ID to "place" it in the index text frame, which generates the ID index mark.
I actually got an AS error when I first tried this: "file doesn't exist" or some such. Then I realized that the "place" command was happening too soon, so I inserted a .5 sec delay in the script, and it worked.
This is actually my first major script for actual work, and I'm so excited about it! I promises to cut production time down to about a thenth of what it was.
I still have to add some logic to branch between handlers with slightly different parameters for five different page formats, but the same page building handler will work on all of them.

A note on this:
Daniel Swanson wrote:
I've tried various js scripts which do an OK job, but they don't make the actual native markers. This means you have to wait until the book (consistiing of multiple ID files) is complete (so that all the page numbers have been established) to generate the index.
These scripts typically search for words and immediately write out the page numbers they are found on -- one shot indexing.
The solution is to add both the topic and its page reference to the current document's index:
if (app.activeDocument.indexes.length == 0)
app.activeDocument.indexes.add();
app.activeDocument.indexes[0].topics.add(app.selection[0].contents).pageReferences.add(app.selection[0]);
The first lines only make sure there is an index to add to (per default, a new document has none).
The last line adds a selected word to the index (it must be a plain text string, hence the use of its 'contents'), and then adds a reference to the selection in the text itself.
Adding the same word a second time will for a change (quite untypically for ID's Scripting) not result in an error but simply add another page reference to the existing one.
When doing this in a loop: remember to work backwards, because the index marker itself gets inserted into the running text, and that will throw off your text indices.

Tagging Text in a document

Similar Messages

Maybe you are looking for