We still have problems with the encrypted passowords in URLs of Web Images. The fix of case 32406 is working: BUT : If the encrypted pwd ends with a slash itself, you will get 4 slashes and your method with the three slashes around the encrypred pwd will fail.

What a hassle. We would most like to write the password unencrypted into the document. But okay, we solved this problem too.

I have an Web Image URL containing a user name and a password. The password is kindly encoded when writing to the document. But apparently the encoding can contain characters that break the URL, e.g. some additional /s.

This bug is fixed now. Encoded password are enclosed in /// now automatically. Here's an example:

http://paul:///AU+mn2/87c/Ppm8=///@priint-grid-mediaproxy-service:80

We still have problems with tables not starting until the following page : Some table do not start at the current page but on the next page only.

If a frame has overset during product buildup, the continue-template is used. Before we do that, we test to see if increasing the frame size will reduce the overset. Unfortunately, in comet_pdf we can only see that we are inside a table - but not how far the table fits. For this we would have to draw the table - a huge lack of performance. But this way, unfortunately, we only see that we have an overset but it doesn't change.

With a little workaround we could fix the problem.

We would like to post-process the finished PDF from comet_pdf. Is this possible within the program?

Yes , this can be done in the DocWatch "Before Close" script. For your convenience there is also the new global value gDocumentPathPDF now. In addition, so that the metadata can 'see' the changes, another DocWatch Before Close call is made directly before the metadata creation. In this situation the (new) variable gBeforeMetaData has the value 1.

See here for the whole story.

You now can define customized dictionaries for each language supported by your hyphenation rules. See here for more information.

Can I query the color profiles of a document?

For this purpose there is the new function document::get_color_profiles now.

Shockingly, the program's metadata previews are all empty (white).

The problem is fixed and the previews are correct again.

After an update from Big Sur to Monterey, comet_pdf crashes in about 50% of the cases that worked fine before. It is not a certain configurations that cause the program to crash, but the same call leads to only about 50 successfully and correctly created PDFs in 100 attempts. In the other 50 cases, the program crashes. And, indeed, the error only occurs from Mac OS Monterey onwards, before that everything was fine.

We were able to identify and neutralize the problem. comet_pdf now runs correctly again under mac OS Monterey.

Under certain and very rare circumstances the text of a table cellmay not be displayed as of PDFlib 9.3. This is caused by special text lengths and separation rules.

The problem was caused by an extremely small rounding error of 0.006 pt. We now circumvent these errors by a slightly less stringent check. This solves the problem.

color::redefine_swatch crashes comet_pdf reproducibly.

The problem is fixed.

After importing paragrph styles using document::import_styles comet_pdf crashes while generating the final PDF.

The problem is fixed now.

We would like to refer to files (e.g. fonts) in our XML folder in the program arguments. But at this point the program doesn't seem to know the $COMETDATA macro yet.

Yes, that's right. The program has not yet established a data connection. To solve the problem, we did the following:

If the -l (--login) argument points to an XML folder, the $COMETDATA alias is immediately (pre)assigned now. A data connection does not exist at this point, but the later program arguments can already use the alias $COMERTDATA. Again, this is only valid for connections to xml folders!

Would it be possible that paths in program arguments (e.g. -i) start with . or ..? That would be very useful.

Previously, "." was replaced by the current path of comet_pdf. This is changed now and follows the common replacement that "." means the current working directory.

# Exporting page 1 / 1
# Fit frame 279, current size 509.236200 x 218.685000
# Fit frame 279 done, new size 509.236200 x 218.685000
# Fit frame 279, current size 509.236200 x 218.685000
# Fit frame 279 done, new size 509.236200 x 218.685000
...

with a lot of fitframes. Sometimes it never ends :-(

The problem are non-rectangular frames with the text alignment "Bottom". Then we must first find the Y-coordinate where we start to draw the text. This is a bit computational. Hence the many fitframes, which unfortunately cannot be avoided. But if the text is empty, then we get into an endless loop.

That is fixed.

Inserting %!TT does not remove the paragraph style at the insertion point.

FXD

The logfiles for the renderer can be set to any path. But if the corresponding folders do not exist, then no log is written.

Fixed for the following log files:

• -v, --log
• --logx
• -u, --pdflog

FXD

The cScript functions table::stroke et al. do not seem to do anything when setting the 'sides' parameter to a sum of values, e.g. eTopSide + eBottomSide

FXD

When rendering a .w2ml file containing images which change their anchoring during rendering (e.g. by moving an inline frame somewhere else), the images are correctly visible in the exported PDF, but after rendering the result W2ML (from --autsoave) again, the images suddenly disappear.

FXD

When I use document::update_url_links all URLinks of the document get the same image. But the downloaded pictures are all correct.

FXD

Under Linux, the function system::os has no defined return value.

The function now returns kLinux (=3) if the program is running on Linux.

Text in table cells, which was actually given in the same font size, is sometimes output by the renderer in different font sizes. Strangely enough, this only happens if the frame has a fitframe.

PDFlib has an automatically enabled feature that can automatically shrink tables if the frame is too small. By default, up to 90% reduction in height and up to 50% reduction in width are allowed. With the Fit frame, the frame is made small and then gradually enlarged - when the table fits for the first time, Fitframe has reached its goal - but the table only has 90% of its actual size.

That's fixed. But you can search for it for two or three days.

The license check for PDFlib fails if the XCACHE folder does not exists.

Ha ha, what a nice bug :-) FXD

Sometimes strokes of type "None" are drawn in tables.

FXD

Strokes of hidden cells are not drawn correctly sometimes. It looks like these cells are ignoring the StylePriority.

FXD

Document page margins wrong after Autosave.

FXD.

You need W2MLs at least from release R25152.

first_page_type wrong after Autosave in documents with single page spreads (facing_pages="false")

FXD

Document intention 'print' changed to 'web' after Autosave.

FXD

Paragraph delimiters lost after Autosave.

This is a side effect FogBugz 24807. FXD

The keepRowsTogether property is lost at Autosave.

FXD

The cScript function frame::shows_textend always returns -1 (kFailure) when called with a linked textframe which is not the first in the chain.

FXD

If a frame only contains empty placeholders (which were replaced by zero width spaces during loading), the frame::fit function leads to an endless loop in the product structure, in which more and more pages are created.

Yes, PDFLib believes that text of size 0 x 0 will be inserted. But the zero width space already has a height. We use the current font size. That solves the problem.

If a multi-column text in the last column contains no text, the frame::fit function fails and does nothing. In the product structure, this results in more and more pages being created in an endless loop.

FXD

We have a test template, which contains >> and << as fixed text in a text frame. Between these characters there is a text placeholder (loads the string id). With PDF Renderer the template does not work correctly, the text is parsed wrongly. For comparison I replaced the >> and <<.
Both templates are shown in the whiteboard, see the text after String Id

StringId: >><cTypeface:><cLanguage:>...

FXD

Text chains in templates are apparently not restored when the template is used.

FXD

comet_pdf sometimes produces overset in table cells when the text content is rotated by either 90 or 270 degrees. This also happens when there is plenty of space for the text.

The cell space was coordinated without taking the rotation into account.

This is now fixed.

When processing a W2ML from InDesign® through comet_pdf and saving it again without any changes, the attribute "fill_priority" on table styles is lost.

This leads to the cell fill attribute not being applied at all.

FXD

Yes. The chance of this is about 1 : 10⁹. In this case, there is a conflict between the old and the new type of license keys. To prevent this, we have removed the old license key check.

Old styled license keys are no longer accepted by comet_pdf. If you are using an old type of license key, please contact license@priint.com.

The function table::cell::get_textpos returns wrong text positions for cells behind merged cells.

FXD

In comet_pdf, oversets sometimes occur in table cells that InDesign® does not have. I understand that this is due to the different running widths of the text. But is there any way to get these oversets displayed?

When using the -ao program option oversets are now also displayed in table cells. In addition, warnings are now written to the output for all cell oversets.

To avoid oversets in cells, you may also use the table cell option "Crop content to cell", see here for more informations.

In text chains the paragraph rulers are only shown in the first frames. In all other frames the lines are not shown.

FXD

In some cases the function returns frame::overset in the parameter lastFrameWithText 0.

FXD

Sometimes a frames shows an overset mark in the PDF altough the frame does not have an overset.

FXD

I use frame::replace with an empty string to delete some text. This works fine in most cases. But if I try to delete text at the beginning of a paragraph it works only if I remove the complete paragraph. If I remove only a part of the paragraph at the beginning of a paragraph, I will loose this paragraph delimiter too.

FXD

Images in rotated frames haveing wrong positions and clip paths in the resulting HTML.

FXD

Rotated inlines in table cells are wrong.

FXD

Rotated inlines in rotated parent frames are wrong.

FXD

Using comet_pdf, the function table::merge_equal doesn't work correctly. It sometimes merges cells with different content.

FXD

FXD

My W2ML contains a lot of inlines. Unfortunately the PDF doesn't always show the right inline.

This nasty error again :-( I hope I hava a final fix for that now.

Is there a way to save the finished input W2ML at any location (i.e. nothing per --autosave)?

You now have the new option

--save path

to do that.

In my datafile I have some HTML texts like 

%!TT_html_&lt;p class=&quot;priint_Maler&quot;&gt;Gabriele Münter...

Or, for better readability. un-escaped: 

%!TT_html_<p class='Priint_Maler'>Gabriele Münter...

The XML file containing this text has the encoding "uff-8".  

If I use this text, which is sent through html::to_tagged internally, in a placeholder, the result PDF unfortunately no longer contains Gabriele Münter but

    Gabriele M√°nter

Yes, this is a small conversion error unfortunately.

• ü in UTF-8 consists of two characters : C3 BC
• In Mac-Ascii these are exactly the characters √ and °.

In short - one convertation too much. The bug is fixed.

After autosaving a file, I always get the text "guides" right behind the first node (<psc:elementlist>) of the resulting W2ML. The text is not enclosed by any element, it appears directly on the top level of the XML structure.

Yes, this always happens, then the original W2ML does not contain any guide, e.g. it contains the empty element 

<guides/>

near the end of the XML.

The error is fixed now.

Under some rare circumstances --autosave will crash the renderer.

FXD

I have the simple text aaübb. If I call

    frame::gettext (fr, str, 0, kEnd, kExportTT);

I always get 

    <ParaStyle:NormalParagraphStyle><pHyphenation:0>aaübb

for result and the ü inside the text is not escaped.

Yes. I fixed it. Result is now as follows:

 <ParaStyle:NormalParagraphStyle><pHyphenation:0>aa<0x00FC>bb

My function variables still containing tags like <0xXXXX> instead of the original UTF-8 letters although the W2ML contains the correct letters (see below).

FXD

I have some text placeholders with function variables with values like:

    max . 20°

If I export this to W2ML, the string max 20° is converted into

    max. 20<0x00B0>

Generally, this is no problem. BUT if I try to load the placeholder, the placeholders load command will use exactly this string - and is therefor executed wrong, because the database (or PubServer, or XML-query) expects exactly  max . 20°, and not  max. 20<0x00B0>.

FXD

To solve this problem with W2MLs, you need to re-export your INDDs to W2ML again!

No matter what export format I choose, the function table::cell::get_text always returns w2 tags.

FXD

placeholder::get_value works fine as long as the text index points to the primary story. But for text positions inside table cells it doesn't work.

FXD

Using comet_pdf, all text exporting function like frame::gettext or table::cell::gettext are exporting TaggedText including w2 tags, no matter wich format the exporter wa given.

FXD

Blending mode on images not applied

Done now

Colors in tables are missing after --autsave.

FXD

The renderer calculates the row height in merged rows incorrectly.

FXD

I have a table cell with the content:

aaa
bbb
ccc

The content is shown well in the PDF. BUT if I use --autosave and opens the file again, the cell content is changed to

aaa
bbbccc

FXD

Awesome fonts

FogBugz 24931

Is there a way to find out in which frame of a text chain the text ends?

The function frame::overset has an additional parameter that contains this information now.

I have inserted some log messages into my placeholders. I noticed that placeholders are loaded up to six times (!) by the renderer. The result is still correct - but it takes a lot of time.

Oops, that's not that good.

FXD.

In my script I use table::get_textpos to find out the internal text range of the tables cells content.

Then I link all placeholders of this text area with placeholder::link2. Unfortunately this doesn't work. All placeholders remain unchanged.

Using InDesign® instead of the renderer it works.

Yes, the difference is a completely different management of table cell texts in InDesign® and comet_pdf. (If you know how InDesign® does it, you'll understand why we did it differently.). But unfortunately, the functions for editing placeholders were only prepared to load ONE cell, but not an entire cell range.

FXD

Inlines in table cells are sometimes not loaded.

FXD

If a placeholder is loaded multiple times, the postfix of the placeholder also appears multiple times in the PDF output. The prefix, on the other hand, is correct.

FXD

I use the -Vi option of the renderer to see the current internal state of the text models. I noticed that the record ID of w2 tags is displayed further as to be 0, 0, 0, '', although I previously made a placeholder::link and the placeholder text was loaded correctly too. 

I'm sure it's just an output error. But it's a bit confusing.

FXD

Paragraph style settings for hyphenations such as shortest word, shortest pre/post syllable are not written to the result W2ML by comet_pdf. When re-importing the W2ML into InDesign®, the default values are therefore always set there. 

This is done now. Paragraph style settings for hyphenations are now written back into the W2ML by comet_pdf. Only exception is "Duden Silbentrennung" - this setting unfortunately is localised by Adobe and can therefore not be transported without loss. 

But please note: The settings are transported by comet_pdf, but cannot be applied. See here for more informations.

It seems that hyphenation is always activated. Settings to disable hyphenation in paragraph style or tagged text seem to be ignored.

Indeed, hyphenation hasn't been turned off yet. This will work now.

Also the settings

• Distance -> Word distance : Minimum
• Distance -> Word distance : Maximum

are supported.

But please note: Minimum and maximum word spacing are only used by comet_pdf in texts without hyphenation! Unfortunately, there is no direct equivalent of the word spacing between InDesign® and PDF:

• In InDesign®, the values mean that the optimum word spacing can be changed up to the specified limit. Whatever the optimal word spacing is, 75% means it can be reduced to 75%.
• In PDFlib, on the other hand, the word spacing is specified as a percentage of the space letter of the current font.

We can therefore only approximate the size of the word spacing, but not specify it exactly.

Other hyphenation settings supported by InDesign®, such as shortest word, shortest prefix and suffix, and maximum hyphens allowed, are not supported by comet_pdf.

However, values for hyphenation defined in paragraph styles, with the exception of Duden hyphenation, are retained when writing W2MLs (--autosave) and are thus restored when the W2ml is re-imported into InDesign®. (Duden hyphenation unfortunately is exported in the current InDesign® language by Adobe and can therefore not be supported.) Local deviations from the paragraph's hyphenation rules in TaggedText are ignored and will not be written back.

The license works. Only the --pdflic option didn't work properly. That's fixed.

Importing PDFs is well done by the comet_pdf - but only if the file have the extension .pdf. Is there a way to import PDFs without a file extension?

Yes. For files without extension we now check whether it is a PDF. This allows you to import PDFs without an extension.

Please note: The PDF check is a special case. The renderer cannot (and does not want) perform a general format check on files. 

I have a text frame with a table in my W2ML. If I adjust this frame to its content, the frame does not change its size. So the frame should be able to display its complete content. Nevertheless, the last row of the table is always missing in the PDF.

I have checked this and found a somewhat mysterious behavior of PDFlib in the special case when a table ends with line edges of weight 0.0. I corrected that carefully.

If a text contains more than one table with inline frames, the W2ML generated by comet_pdf may not be opened in InDesign®. InDesign® crashes when you try to open the W2ML.

This is not an error in comet_pdf. It's InDesign® that crashes.

The reason was inlines in the tables. We're pretty close to the limits of what's possible - inlines are not supported by InDesign® in TaggedText-Export/Import: Instead of inlines, only spaces are exported. And all this in a rather idiosyncratic combination with additional ParaStyles. So that we can support inlines in the renderer, we have to calculate their positions in the tagged text over and over again. Unfortunately, this sometimes goes wrong because of the additional (and unexpected) line breaks that InDesign® comes up with. This is a very unfortunate problem.

That's why I re-implemented the complete export/import of inlines both in InDesign® and in the renderer. This should prevent the problem from occurring again in the future.

BUT: It is important to exchange plugins as well as renderers and create the W2MLs again!

Using \$DESKTOP... as path for the XCACHE causes the program to terminate with thefollowing exception:

fatal exception: [2124] PDF_set_option: Can't set option 'topdown' in 'object

FXD

Is there a way to avoid entering the admin password in the Linux version?

Yes, see here for more informations.

Function variables not replaced in placeholders of frames not replaced.

FXD

The DEMO watermark is not drawn over all frames.

FXD

Sometimes I get the message 

Cannot save '/Users/paul/Desktop/402653700 Kopie.w2ml'. Try to re-create w2ml with Comet plugins of at least revision R7901.

when I try to save a W2ML using option --autosave.

FXD

I have some text frames that have been fitted to their content in InDesign®. In the PDF of comet_pdf some of these frames unfortunately have an overset.

Yes, the text run widths of InDesign® and comet_pdf are not 100% the same. Both use different text renderers.

Text frames that were not treated with fitframe by comet_pdf itself, retain their original size from W2ML, but when rendering the text content, the available text area is slightly increased by 0.3 Pt. This helps to avoid small text oversets in comet_pdf. BUT: That won't work 100%. And values >0.3 will also cause the text to protrude beyond the bottom edge of the frame.

In text frames whose content consists of a single inline, fitting the frame to the content is ignored.

FXD

I use the Linux version of comet_pdf. After starting the program, I am asked for a sudo password. What is that for?

We need the sudo password for license checking. If we don't get the right password, comet_pdf cannot check the license and is started in DEMO mode therefor. The password is encrypted and saved in the file zpasswd next to comet_pdf. If you do not want this, you can remove this file at the end of the comet_pdf. (But then you will be asked for the password again next time.)

All if-else-end constructions in layout rules seem to have been destroyed - and they no longer function. The error does not occur until R24142. If you open the document with an older release, everything is as it should be again.

Oh, that's a big mistake! R24142 should therefore not be used!

The bug happened while porting the plugins for CC2019 and is fixed now.

Attention: Layout rules with if-else-end that have been configured in R24142 must be reconfigured with another release!

Can comet_pdf convert quotes to typographic quotes?

Since now - yes. See here for more informations.

Embedded images in comet_pdf have a poor resolution

FXD. See here for more informations.

Attention: To fix the problem, you have to recreate the W2MLs using at least v4.1 R24141 of priint:comet plug-ins too!

Calling comet_pdf -s hello under Linux, the resulting PDF does not contain the QR Code but I see the warning

Cannot load pdf '/home/..../XCache/U26831/my_temp_files/barcode_1.pdf' 

I add option -VX to the renderer call to see inside the XCACHE - the file barcode_1.pd is there and seems to be correct.

Unfortunately the conversion from PS to PDF is done asynchronously and the PDF is not ready at the time that is needed by the renderer.

FXD. Conversion is done now in time.

Using the Linux version of comet_pdf with

comet_pdf -s hello

I get the error

Error 2517 in PDFlib pdflib font cannot be embedded (pfa or pfb font file not found)

Obviously the font Courier used in this document cannot be embedded into the PDF. Okay, we do not embed such fonts now. This fixes the error.

Suddenly the renderer crashes in a call to server::load_placeholder_str. In last revision, all works fine.

Ooh, this is a side effect of the fix of bug 24013. FXD

I have a para style with a "space before" greater 0.0. This setting is applied by the renderer - thats very nice. However, it seems that the space between paragraphs in comet_pdf is slightly larger than in InDesign®. Can you correct that?

I adapted that a little better. Unfortunately, we do not know exactly how Adobe calculates the distances. So we can only approximate that.

If I try to open the attached w2ml (see here for file), comet_pdf will crash reproducible.

Using option -V* I can see strange things like

<w2cell:...>><0x200C><CellEnd:>

in the internally transformed tagged text. May be, this is the reason?

Yes, this was the reason. FXD

Frames with tables sometimes become too small with fitframe - just 0.5p, but this will cause the last row of the table to disappear. What can this be?

After that I searched for a long time. The problem is that the line width of such tables was not defined by the width but by the color [None]. In this case, InDesign® automatically uses the line weight 0, no matter what the width is actually set.

In the renderer we do the same now, so that the problem is solved.

I have successive empty paragraphs in my document - someone uses empty paragraphs for spacing. Anyway, the three empty paragraphs each have font size 12. But the paragraph before has font size 36. It seems that I get a distance of 96 points then.

FXD

If a frame has an text overset in the PDF, the renderer informs the user by an Export warning like

Export warning

    [To find frames by UIDs in the PDF, please use option -au.]
    [To find text frame oversets, option -ao may be usefull too.]
    Overset in text of frame 4787

This is very fine! But it would be perfect if there were also a page number.

This is done now:

Export warning

    [To find frames by UIDs in the PDF, please use option -au.]
    [To find text frame oversets, option -ao may be usefull too.]
    Overset in text of frame 4787 at page 14

If I want to insert PS images, I get now and then irritating error text of the form

%% BoundingBox ...

The message comes from the program that makes the internal conversion of the image to PDF. Apparently this program writes some issues to the terminal. We suppress these messages now.

The renderer does not know the variables gDocument and gDocumentID of doc watch scripts.

The variables are defined well now.

I have a document with a long text (9 pages) with 5 tables. For some reason, the last two tables are not drawn.

FXD

Using priint:comet, one can create serializations of documents in In InDesign®. This is not yet supported in comet_pdf, right?

Now you can :-)

Sometimes the program falls into an infinite loop when creating the PDF.

The problem was an empty PDF preset and is fixed now.

Sometimes empty lines appear in PDFs of comet_pdf that are not in InDesign®. The ID document only contains a soft return - but in the resulting PDF I get TWO line delimiters.

The problem is a strange construction inside the exported Tagged text:

<ParaStyle:abc><0x000A> WITHOUT a newline (\n) character before <ParaStyle:abc>

We are now removing such constructs from the W2ML export.

document::open fails for indd files.

Yes, it opens w2ml's in case of comet_pdf. But to avoid incompatibilities in code, we now replace the file extension "indd" by "w2ml" automatically.

The comment anchors of frame notes are mostly far away from the frame in the PDF. In the screenshot you can see a frame note in InDesign® and in the PDF. As you can see - it's not easy to see the connection between the frame and the note in the PDF:

We now placing the anchors next to the frame in the PDF:

If there are more than one frame note, the anchors are stacked:

The PDF contains the Comet notes for pages and frames only, all notes for Comet groups are missing.

FXD, also the notes for Comet groups are created.

After autosaving the input W2ML, the Comet notes elements <tagged> conaining doubled %!TT%!TT markers at the beginning of the text.

FXD

• document::notes::export_, document::export_notes

Fogbugz 23269 - Comet notes not saved by comet_pdf

The Comet Notes of a W2ML are saved now too, if --autosave is used.

If I have a placeholder with a direct statement, the function variables are ignored and the <funcvar> tags raising some errors while executing the statement. Here's an example:

#pragma var "Title" "Mr" "Miss"
select <Title> || ' ' || name from ... 

FXD

Comet notes can be shown as PDF notes in the resulting PDF using option --annot. But in these notes, all line delimiters are lost.

Strange behavior - FXD

Using option --annot, comet_pdf can export Comet Notes as PDF note available in Acrobat Pro.

Unfortunately, blanks in Comet Notes are lost, if they directly behind a style change. For instance, if I have a green word followed by a red word, the blank between the two words are lost in the PDF note.

FXD

If text is inserted at the end of a paragraph, the alignment is no longer correct. This text is always left justified, no matter what the paragraph says.

FXD

Sometimes the font colors in the PDF are wrong. The error always happens when first a SWATCH color is used followed by a "free" color.

FXD

Sometimes the W2ML contains strange bbox values like 38373487348734785668457847 ... 464.002 after --autosave.

FXD

If a text ends by a table, the fitted frame is 'a little bit' to high. It seems that the 'distance after table' is added to the frame height.

FXD

You now can create page previews of th resulting PDF. Use option --metadata 16 to do this.

I have a W2ML with two linked text frames. if I run ccc with the --autosave option, the text chaining will be gone, and in a second call I will no longer have text chaining.

Oh how disagreeable. Fxd.

Loading master items using page::masteritems_load needs an product link in comet_pdf but not in InDesign®. That leads to different results in the PDFs of course.

The behavior of comet_pdf is now adjusted. Master page frames no longer need to be linked to a product.

If I use string::md5hash or strmd5hash in one of my scripts, the renderer crashes.

fxd

comet_pdf now supports the Web Images introduced in priint:comet plug-ins v4.1.

To enable/disable automatic updates of Web Images of the current input document please use option --urllink_update. To show the states of the Web Images in the generated PDFs, please use option -a with identifier h.

Using recorded data of a PubServer project will crash the renderer immediately.

Erroneously, a timer was also started here (but not terminated) to determine long instructions. This error is fixed.

Frames with tables often cause error 3425 when fitting to their content (frame :: fit_better). What does this error mean?

# Fit frame 424456, current size 476.220500 x 42.519685
PDFlib exception occurred in frame::fit : [3425]
# PDF_fit_table
# Calculated table height 55.4973 too large
   (> 42.5197, shrinking 76.6158%)
# Fit frame 424456 failed with error 3425

PDFlib raises this error, if a table inside the text cannot draw at least one body row. The minimum height of the frame is shown in the error description (55.4973 in the example shoewn above).

The renderer now independently enlarges the frame to the required minimum size. Then the renderer tries to adjust the frame again.

frame::rotate produces incorrect results.

fxd. See frame::rotate for more informations.

When building products in the renderer, new pages are not linked to the current master page.

Masterpages are correctly applied now.

Since Mac OS 10.13 (High Sierra) I get strange error messages from the renderer:

/BuildRoot/Library/Caches/com.apple.xbs/Sources/
   AppleFSCompression/
   AppleFSCompression-96.1.1/Common
    /ChunkCompression.cpp:50:
   Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources
    /AppleFSCompression/
   AppleFSCompression-96.1.1/Libraries/CompressData
   /CompressData.c:353:
   Error: Unknown compression scheme encountered for file
   '/System/Library/CoreServices/CoreTypes.bundle
   /Contents/Resources/Exceptions.plist'
/BuildRoot/Library/Caches/com.apple.xbs
    /Sources/AppleFSCompression/
   AppleFSCompression-96.1.1/Common
    /ChunkCompression.cpp:50:
   Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/
   AppleFSCompression/AppleFSCompression-96.1.1/Libraries/
   CompressData/CompressData.c:353:
   Error: Unknown compression scheme encountered for file '
   /System/Library/CoreServices/CoreTypes.bundle/
   Contents/Library/AppExceptions.bundle/Exceptions.plist'

These log entries are the result of a bug in the OS. They're  harmless and don't indicate a problem, although they do pollute Terminal output when they appear while using comet_pdf. Like dozens of others, we have reported this issue to Apple, and if you have a developer account, we would be grateful if you did likewise. 

Solution for us:

Since the error occurs only if you use the auto launch option -L, we slightly changed this implementation. The new auto launch can implementation now avoids the error messages.

Since this release, the priint:comet 4.0.5 based comet_pdf is history. Please use the 4.1 based version instead.

Please note:  You need a new comet_pdf license for 4.1. Please contact license@priint.com for a new license.

Centering inlines on pages is wrong, the inlines always appear at the top of the page.

fxd

frame::resize with reference points other than left top does not work - are better : Resizing works well, but the positions of the resized frames are amazing.

fxd.

After autosaving a W2ML, all opacity properties for knockout -, isolation - and overprint groups are lost.

fxd. The new W2ML will contain the correct values for this properties now.

The docu says, that frame::opacity returns its values in the range of 0.0 - 100.0, but the values are always in the range 0.0 -1.0.

fxd. Values are returned in the range 0.0 - 100.0 now.

Transparent frames becomes invisible after autosave.

Transparent frames now remain visible even after autosave.

Rotated frames are placed differently in the renderer than in Indesign.

InDesign® uses the upper left corner of the frame AFTER the rotation when placing rotated frames. The renderer has used the original point of the upper left corner, but this is no longer on the upper left corner on rotated frames (for instance, on a 90 ° counter-clockwise roatation this is the lower left corner).

The renderer does the same now and the problem is fixed.

After saving a W2ML file using --autosave, all inlines are missing.

Yes, the export of inlines wasn't supported until now. The inlines are properly exported now.

Inlines with Y positions relative to text line (X height, cap height, ascent, ...) will lead to the PDFlib exeption 1420.

fxd

itemlist::inlines ignores inlines in table cells and returns only ilines of the primary story.

fxd

Please note: comet_pdf Linux was tested with Ubuntu and is BETA for now.

Using the option --autosave, embbeded images are saved by its temp path, not as blob.

fxd

Using the Windows version of comet_pdf, images whose names containing German Umlaute (ä, ö, ü, ...) can not be loaded.

fxd

See here for more informations.

See here for more informations.

I have a w2ml with some tables inside and the renderer can handle this file without any complaints. But if I save this file using the --autosave and try to open this new file, the renderer crashes.

...  some problems reading the TaggedText of tables ...

fxd

Letters with diacritical marks like the German ü can be written as so called combining characters: the letter itself and then the diacritical mark.

German ü as combining character : u<0x0308>

Combining characters are now normalized by the renderer by NFC algorithm.

Since R19610 of comet_pdf, my place holders are not loaded anymore. Only the last place holder of texts is loaded correctly - all the other place holders are left untouched.

This was a real serious bug! It occurs as an unexpected side effect of the fix of bug 20687.

fxd! Place holders correctly loaded again!

Frames, fitted to their content by using frame::fit_better or any similar function can lead to an text overset in the renderer. 

Using the programm option

--fontscale float

you can force to scale all fonts and line spacing in the PDF accordingly. The font scaling has no influence on the document content itself.

The text marker "Goto next column" is not supported by the renderer.

This is done now.

ATTENTION

Goto next frame/page/even page/odd page are still NOT implemented and the usage of these markers may lead to some extra paragraph in the PDF. Please DO NOT USE markers other then "Goto next column" for now!

Embedded images with an active clippath are displayed incorrectly in the renderer. The clipping path is not used here.

InDesign® removes the according image option from such embedded images. The renderer will use the default clipping path for embedded images now by default.

Sometimes the first line indention of lists is wrong in the renderer.

This happens every time the paragraph does not define a corresponding tab, but the list uses tabs in their enumerations. The setting of the tablulator is now made automatically. This solves the problem.

I have defined some bullet points with WingDings letters in my document. These bullet points are not visible in the renderer.

okay, another problem with symbol fonts. InDesign® defnines these letters by their GlyphID, not by the letter itself (or its unicode in the private space of the font). To solve this problem, we map the GlyphIDs according the font to the right Unicode inside the private space of the font. The following fonts are supported:

• Zapf Dingbats
• WingDings
• WingDings 2
• WingDings 3
• WebDings

Some of my images are not shown with transparent background.

This happens whenever images with applied alpha channels are embedded in the document. In this case, InDesign® removes the local path settings for the image and uses the alpha channel automatically.

This is now done in the renderer too.

Textvariable "TotalPageCount" missing for text frames on master pages.

fxd

InDesign® shapes built by combined paths are not drawn correctly by the renderer. The image shows a InDesign® shape (left) and the result of the renderer:

Hard stuff : Shape paths of InDesign® my consist of any number of sub paths combined by XOR in InDesign®. As you can imagine, implementing this behavior for comet_pdf isn't so easy. But now it works, hallelujah!

Text written in Wingdings or  Zapf-Dingbats not shown by the renderer.

Letters of symbol fonts are addressed completely different from 'normal' fonts: Instead of using the unicode of a letter directly, the PRIVATE SPACE of the fonts contains any number of letters for any unicodes and one should know, how to map the unicode of the letter written in InDesign® to the unicode inside the font. And, to make it a little bit more exciting, often there is no algorithmic way to find the unicode defining a letter in the private space.

We implemented the usage of following symbol fonts:

• Zapf Dingbats
• WingDings
• WingDings 2
• WingDings 3
• WebDings

Letters using one of this fonts are shown correctly by comet_pdf for now.

In an InDesign® document I have a circle and an ellipse laying above a colored background: Using comet_pfd, the ellipse is drawn well but the circle is shown a square.

fxd

Floating numbers (float) in cScript are always rounded to the next smaller int in cScript. For instance, the call 

wlog ("", "%f\n", 2.5*2.5);

will write 4.0 to the log file.

fxd

This the new programm option --compression you can control the compression of the output PDF. Choose on of the values 0 (no compression) up to 9 (best compression).

fxd.

fxd

Fxd.

If I try to show the same table with comet_pdf, the black line between AAA and DDD is missing.

Strange behavior of InDesign® here: Cell DDD used the stroke style defined by the hidden cell above the anchor cell of DDD.

fxd.

A cell consisting of merged rows can only "grow by content" if the first row is set to "auto grow". If the first row of the range has a fixed height, the merged row can not get higher at all.

fxd

EXPERIMENTAL : New programm option --playback. Please do not use for now! See here for more informations.

Crash on table::get_row_height

fxd

• textmodel::force_redraw (but it's a nop)
• xml::attribute_exists
• xml::attribute
• xml::iattribute
• xml::fattribute
• xml::sattribute
• textmodel::set_insets

Bugfixes from Comet 4.0.5 resp 4.1

Bugfixes from Comet 4.0.5 resp 4.1

Support of new 4.1 area build features

Bugfixes from Comet 4.0.5 resp 4.1

There are some new hyphenations available:

• Spanish (es)
• Italian (it)
• Danish (dk)
• Finnish (fi)
• Estonian (ee)

See here for more informations about hyphenations.

It seems that the hyphenations are wrong in the PDF.

fxd

If I redirect the output of comet_pdf, I get a log of [m33; ... in my file. I assume, this is needed for colorization of the output. Is there any way to suppress this?

You may suppress output colorization by using the new option:

   --no_bash_colors

In this case also the SOAP long time calls only showing the amount of the time, not the progress.

If the left and first-line indentions of bullet points are defined in the tagged text (and not in a para style), the first bullet point is indented wrong.

fxd

Reading log files, it's quite hard to find out the current program options used by a renderer call. It would be nice, if the program would write it's current program options to the log file.

The renderer now writes the current program options to the logfile. To see, what happens , if option -s is used, this entries to shortcuts.xml are resolved.

comet_pdf -s posters_build -L -auf -v \$DESKTOP/aaa.log

# Application arguments :
 comet_pdf
    -s posters_build
        -l : posters
        -i : $DESKTOP/fifo/render/template_de.w2ml
        -p : $DESKTOP/fifo/priint 5.5/data/all_posters.xml
        -P : fontnames.xml
    -L
    -auf
    -v $DESKTOP/aaa.log

Anchored inlines in cells are placed wrong in case of "non-left" anchor references - Ooops, what can this mean? Simply this:

Try to find out the InDesign® behavior for this case (and play around with the ref-point of the object too and change 'relative to spine' sometimes) :-)

We hope, we found the right solution here now.

I have a table cell with an anchored object. The object is placed with an negative x-offset:

As you can see, the anchored object lies BEFORE the table. In my eyes this incorrect because the inline is owned by the cell - so it must be drawn before the cell:

Anyway, InDesign® draws the inline after the cell - so we have to do the same.

"fxd"

Rectangle frames with scalings not equal |100%| wrong will get wrong sizes in the PDF. It seems that the scaling is applied two times to the frame size.

Yes, if you ask InDesign® for the size of a scaled frame, you will get the size with the scale factors already applied. This we have in mind now while drawing frames in the renderer.

Comet_pdf now supports color profiles set in the W2ML. See here for more informations. To turn on color profile handling, see here.

Using the new programm options --w2lic or --pdflic you can validate the installed licenses.

Using the new programm options --w2lic_path and --pdflic_path you may use customized locations for license files.

The functions table::get_strokecolor_... will return wrong colors always.

fxd.

If you create a PDF with spreadwise ordered pages, spreads are too small, if the left page of a spread has a smaller height than the right page. The spread will have the height of the left page only.

fxd

• framhe::write_frame_info
• frame::apply_frame_info
• frame::delete_frame_info
• itemlist::write_frame_info
• itemlist::write_frame_info2
• itemlist::apply_frame_info
• itemlist::apply_frame_info2
• itemlist::delete_frame_info
• itemlist::delete_frame_info2
• document::write_frame_info
• document::apply_frame_info
• document::delete_frame_info
• document::delete_frame_info2
• document::page (it's a nop)
• document::show_page_elements
• document::page_elements_shown
• page::crop
• itemlist::intersections
• table::cell::get_fillcolor_rgb
• table::cell::get_fillcolor_cmyk
• table::cell::get_fillcolor_lab

• frame::get_page_element
• frame::get_template
• frame::get_chapter_id
• frame::get_z_order
• frame::is_in_front
• frame::is_at_back
• frame::bring_to_front
• frame::bring_forward
• frame::send_backward
• frame::send_to_back

• textmodel::solve_overset

The results of frame::bbox are still the same, no matter if I set the parameter spreadRel to 0 or 1.

You're right, the parameter spreadRel was ignored in the past. This is fixed now.

I have a place holder with prefix if non empty set to # "/r" pStyle "Bullets" . This prefix has no effect : No new paragraph is created, and the paragraph style is left unchanged. If I change the prefix to a single /r, a new paragraph is created.

fxd

I'm using frame::fit to fit the width of a text frame with only one line of text. This works, if the frame has no insets. But the frame becomes to small, if the frame has an left and/or right inset. 

Yes, yes, yes. fxd.

In InDesign®, a 'Indent to here' is shown as a †, if I show invisbles. In comet_pdf not.

shown now if you use option -a i

I have a bullet point text with an "Indent to here" at the beginning of the text. In the first bullet point, the "Indent to here" is applied well, but in the second not.

fxd

In comet_pdf findet linklist::collect_any keine Rahmen.

Ganz recht, das war ein Fehler im Renderer, der hier beim Suchen der Seiten eines Rahmes zu früh aufgegeben hat. Das ist gefixt.

Documentation says that table::resize_rows will set the autogrow property of rows depending on the values given for minHeight and maxHeight. But if I call

table::resize_rows (T, 0, 1, 0.0, 10.0, 40.0);

the first row will not get autogrow-able.

Oops, a == instead of a !=.

fxd

fxd

Instead of using the tint given by the alternating pattern the cell uses the default tint of 100% here. This is fixed and the cell now takes care on the tint given by the alternating pattern.

After calling document::setstartpage the master page items on the first page are wrong.

The problem were some overridden master page items on the first page.

fxd

document::set_startpage (2);

at first in our script. But it seems, that the templates placed later to the document not matching the according page types.

fxd

Using comet_pdf, frame::rotate always uses (0,0) as reference point of the rotation. Right?

As written in the documentation, yes.

You now can use the two types of reference points for rotation in comet_pdf too:

• Reference point in page co-ordinates relative to the left top corner of the frame
• Reference point given in frame co-ordinates. RECOMMENDED.

How to set a clipping path using comet_pdf?

Use the new cScript-functions image::setclips and/or image::setalpha2. In addition, all situation, where you can set in clipping index, set a clipping path too - the renderer now can read this paths.

Whiteboard support

If I use option -g (global variables), the renderer crashes every time, I call a script and no datapool connection is defined.

fxd

frame::fit with the image placement kFitContent produces an obviously wrong result. 

fxd

Not sure, if this is an floating point rounding error or if it is miscalculated: Rotated images in frames with a contour are placed a little bit incorrect (not much but 2 or 3 points).

Wrong calculation - fxd.

This is fixed for all methods of frame::fit_image now.

The blue frame edges shown by option -af are drawn inside the stroke for inner strokes and outside the stroke for outer strokes. It must be vice versa, or not?

Yes, of course. This is fixed.

• document::dump_uidtranstable

I have a document with image paths like

E:\Data\Images\...

After autosaving my w2ml on a Macintosh computer, the drive letter E: is missing for such paths.

fxd

After the fix in R11411 : Now I will loose the softreturns when I open the w2ml in InDesign®:-(

Aaargh!! fxd.

In my document are some PS images. Using option -VX I can see, that the renderer converts this images into PDF - but in the document, I can see nothing but a white frame. In addition, after autosaving the file, I can see, that the frame contains the right PDF as image.

Yes, this behaviour depends on a non empty crop box inside the PS image, which wasn't applied till now.

fxd

I now have a VeryDoc license for ps2pdf. But if the renderer tries to use this license, it crashes in the moment, it tries to convert a PS to PDF. Only if I have no (or an empty license, the conversion works.

fxd

Whiteboard support

Implementation will take a little time. The following methods are implemented now:

• elementTransform
• elementMove
• documentReorganize
• applyMasterpage

After reorganizing and autosaving a document, some of the images in the document are missing. The frames itself are still valid, but they are empty.

This occurs only on template changes. After duplicating an image from its old to its new frame, the new frame was still a text frame. We now convert it to an image frame. This solves the problem.

• document::set_firstpagetype
• document::get_firstpagetype

To create image previews from the PDFs, the renderer can use pdftoimage.exe from OpooSoft on Windows (See here for more infos.). Generated images are watermark if no license is given. After buying a license - where we have to place it?

Please follow this steps:

1. Open the license file you've got from OpooSoft
2. Open the file \imgconv\pdftoimage\licensekey.txt inside you renderer installation
3. Copy/Paste the content from file 1 to file 2. Attention! Do not add any white spaces, quotas, nor returns around this content.
4. Save file 2.

Hint

To activated the using of pdftoimage.exe, please edit file imgconv\pdf2image.cpp of your renderer installation and enable line 

// *gResult = do_opoo ();

near the end of the file by removing the first two slashes.

To temporary convert Postscript images to PDF, ps2pdf.exe is used on Windows systems (See here for more infos.). This is third party software implemented by VeryDoc. If no license is given, the software draws watermarks above the created PDFs. Therefor we bought a license. The question is, where we have to place this file?

Please follow this steps:

1. Open the license file you've got from VeryDoc
2. Open the file imgconv\ps2pdf\bin\licensekey.txt inside you renderer installation
3. Copy/Paste the content from file 1 to file 2. Attention! Do not add any white spaces, quotas, nor returns around this content.
4. Save file 2.

Load scripts in renderer 4.1 are not executed but raised an "Unexpected end of file" error always. Using 4.0.5 the same scripts are executed well.

fxd

A document contains various overidden master page items. All of this items are correctly shown in the PDF But if I autosave the W2ml and reopen it, the overiden master page items are missing.

The problem depends on the well known issue, that the renderers autosave function is stiil in work. In the cuurent situation, two things are went wrong:

1. Wrong positions of rotated frames in w2ml export.
2. Overidden master items were placed on a wrong layer

fxd 

Ein TaggedText enthält Softreturns (\n). Die erste Darstellung dieses Textes im PDF ist richtig. Wird aber das erzeugte Dokument mit --autosave in die w2ml-Datei zurückgeschrieben und dann aus dieser geänderten w2ml ein PDF erzeugt, dann sind in diesem PDF aus den Softreturns offenbar normale Absatztrenner geworden. Insbesondere bei Absatzformaten mit Abständen davor/danach oder mit linken Einzügen ist das natürlich dann nicht mehr so schön.

Das Problem ist, dass die PDFLib \r und \n genau andersrum als InDesign® anwendet. Das war an einer Stelle (nämlich beim Schreiben des TaggedText) nicht bedacht.

fxd

In case of strings consisting of at least four equal letters, hyphenation marks are inserted after every TWO letters now. For example, mmmmmm will become mm-mm-mm.

Substrings of text like mmmmm, bbbbb, ßßßßßß (Yes, people do this!) will now get hyphantaions after every four equal letter.

fxd

Same with 

• table::cell::copy_content
• table::cell::std_deviation

All fxd

Sometimes a paragraph delimiter belonging to a place holder is not removed from the text when the place holder is loaded.

fxd

The first section of documents always starts with page number 1, no matter, what the document says about its start page number.

fxd

... but obviously InDesing does.

And the renderer now too. fxd

• document::set_startpage
• document::find_frame
• textmodel::clear_placeholders
• Module itemlistlist
• table::fit_col
• table::find_overset
• table::cell_is_overset, table::cell::is_overset
• table::get_parent
• table::has_parent
• table::get_firstouter_column
• table::clear

I have a tagged text with escaped Unicodes. But the escapes are using small letters like <0x00fc>. This letters are not read by the renderer.

Not sugar, but icing sugar ... fxd

I have the impression that the height of table rows with empty cells are not correct.

Well, you're right. fxd

... and plz take a moment to think twice about from where the height of cells are coming - in most cases this is the UNDEFINDED default font size used at the insertion point of the table. Is that really what you want?

Why do you use alternating vertical lines with a weight of 0 and then set cell styles to all cells overriding this weight?

fxd (We now take care of overridings of alternating strokes.)

Place holders beginning or ending with paragraph delimiters do not remove the delimiters. This leads to extra white spaces between paragraphs in the PDF.

Very hard to solve, took me ten (!) days! fxd

Pre/Postfixes of place holders

Error messages generated by the product building process and shown in the program output are unreadable.

Yes, the messages containing Windows line delimiters (\r\n) and this is not, what the Mac Terminal expected to get.

fxd

It seems that the renderer ignores the space before/below tables. 

Not any longer

Is there any way to look into a text model a little bit closer?

You may use option -V or the new script function textmodel::dump to see the current state of one or all text models of the current document. But take care : This may produce a lot of output and the output may may only be meaningful for the guys of WERK II. 

Showing the hidden letters of a text (option -ai), I can see a big blue + in a text consisting of two inlines only. This means, between the tow inlines must be a ZERO WIDTH NON-JOINER (0x200C), but I'am sure, this letter wasn't imported. But where does it come then from?

fxd

Ich hab gerade eine Funktion auf Basis von bbox und frame::create2 gebaut. In Indesign sieht es gut aus, aber im PDF Renderer leider nicht.

Es sieht eigentlich auch im Renderer sehr gut aus - wenn man bedenkt, wie lang der Weg dahin war. Nur die Margins waren in der falschen Richtung gerechnet.

In SOAP connections you will get an instant message now if the renderer must wait longer than two seconds for a server respond. You will see messages like this in this case:

# Waiting for long time call [1] '...'ReferencesTT',...' : 8.8 secs
# Search logfile for '# Waiting for long time call [1]' for full command.
# Enable logfile writing by option -v log_path.
# Waiting for long time call [2] '...'grouped_article_table',...' : 11.4 secs

Show invisibles in text

Using option -ai you now can show invisibles in texts.

Verankerte Rahmen machen die Textzeile des Ankers so hoch, wie der verankerte Rahmen ist.

fxd

Inlines vom Typ "Eingebunden oder über Zeile" haben über und unter dem Inline einen Abstand. Vom Renderer wird der leider ignoriert.

fxd

• textmodel::inline_
• textmodel::inline_above
• textmodel::anchor
• textmodel::get_anchor
• frame::inline_
• frame::inline_above
• frame::anchor
• frame::get_anchor
• frame::release_inline

Text variables

• table::space_before
• table::space_after

Is it possible, to implement this for the renderer?

Yes, it's done now.

Hard to find ...

The error was caused by a ZERO WIDTH NO-BREAK SPACE inside the text. InDesign® does not support this letter into TaggedText! And, as a result of this, the w2ml-index of the inline points behind the text end - and isn't drawn therefor.

The only solution here is : Remove the ZERO WIDTH NO-BREAK SPACE from the InDesign® document and do not use this letter anymore!

To impede the use of this letter, we removed the Non-breakable zero Space menu from the InDesign® menue Font -> Spaces.

Sometimes, inlines in table cells are not drawn.

In most cases this depends on to small columns. In oposite to InDesign®, table columns must be wide enough to show inlines. See here for more infos.

Placing an image into a frame using frame::image and the placement info kFitContentHeight will fail with an error message:

Value -1.0 for width too small. 

fxd

Is it possible, to find out text oversets in files generated by comet_pdf?

You may use option -ao to show text oversets in PDF.

In addition, we now write a list of warnings with all text frames and (new) all table cells with text oversets. If search for "Overset in" in the output and/or in the logfile, you can easily find the oversets now.

Exit values

• itemlist::intersections
• document::revert

Text after softreturns in lists is not indented well but starts at x-position 0. fxd

What to do on "No post script name found for font ..." warnings?

Solution is described in your local offline documentation. A short note is now written to the output of the program now:

No post script name found for font 'Arialette Regular', using 'Arial'.
Font used in frame 394 for text 'sqd?fl AAAA sa?Hen?dip?sam s...'.
    To define font name mappings, edit fontnames_default.xml
    or your local fontnames.xml
    See manual for more informations:
    -> YOUR_DOCU_FOLDER/InDesign/Plugins/comet_pdf.html#Schriften

Quotas (", ') about program parameters are now ignored by default.

Yes, but the units where misinterpreted. This works now.

Please note: Optical and metric kernings are not supported.

Missing images of in-tags are not shown in the warnings. -Fixed -

It seems that the paragraph justification 'Away from binding" does not work. All other justifications and even "To binding' are working well. 

A little export error wrote binding instead of binding in this case.

Fixed.

I have

• A page template with one element. The elements size checking is disabled
• A template with one frame only. The frame has a continuing frame. 
• A product with a text longer than the templates frame.

Building the product is done well BUT the first text frame seems to be too large: The bottom side of the frame exceeds the page. Building the same product in InDesign®, the frame ends at the bottom margin of the page. 

This is fixed.

Farbtonfelder

FogBugz 16843 - Farbtonfelder werden nicht unterstützt : Der PDF-Renderer scheint die in InDesign® möglichen Farbtonfelder nicht zu unterstützen. Sei fehlen jedenfalls in den <swatches>-Einträgen der w2ml und in den erzeugten PDF wird statt des Farbtones die entsprechende mit 100% Deckkraft verwendet.

Sowohl Renderer als auch Comet-Plugins unterstützen jetzt auch Farbtonfelder. 

ACHTUNG: Um Farbtonfelder zu unterstützen, müssen die W2MLs mind. mit v4.0.5 R10600 erzeugt worden sein!

• textmodel::set_parastyle
• textmodel::find_surrounding_paragraph

Bullet points are missing right after tables if the parastyle around the table differs from the style with the bullets.

Fixed

Indentions after soft returns are treated like indentions after hard returns.

Fixed

In same rare cases a fitted frame is too small and can not show the last line of the text. is occurs only if the text contains tables. But not every text frame with tables is wrong.

This amazing behaviour is fixed now.

What does this renderer warning mean?

# Cannot auto delete LinkList in comet_pdf

To avoid this lines, call itemlist::release directly in your scripts. But since today, we can auto delete this lists in the renderer too.

Export tables to w2ml

• document::save
• document::saveas

TaggedText generated by comet_pdf contains unescaped Unicode letters.

Fixed.

Instead of replacing the cell content, table::cell::set_text inserts the text at the beginning of the cell.

Fixed

The spreads.xml of the metadata contains the fields:

...pages.page.number  
...pages.page.integer
...pages.page.ordinal

Created by InDesign®, this fields are filled with page numbers, but comet_pdf will leave this fields empty.

Fixed.

I have a simple InDesign® text with only one table. The table only consists of two cells. Every cell contains only one inline. Showing this text in comet_pdf, the first inline is missing.

The problem occurs only if the table is followed by a single empty paragraph and is fixed now.

• frame::duplicate,
• frame::create
• frame::create2
• frame::create_textframe
• frame::create_textframe_f
• frame::rectangle
• frame::count_columns
• frame::create_columns
• frame::bbox_on_creation
• frame::add_to_cometgroup
• frame::remove_from_cometgroup
• frame::is_member_of
• frame::remove_sub_cometgroups
• frame::apply_layout_rules
• frame::apply_magnets
• frame::store_magnet_distances

• itemlist::add_to_cometgroup
• itemlist::remove_from_cometgroup
• itemlist::apply_layout_rules
• itemlist::get_cometgroup
• itemlist::get_cometgroup_members
• itemlist::are_members_of
• itemlist::create_cometgroup
• itemlist::resolve_cometgroup
• itemlist::move_cometgroup_to
• itemlist::move_cometgroup_by
• itemlist::remove_cometgroup
• itemlist::store_magnet_distances

• placeholder::change_tags

• document::get_front

• xml::attribute_frame
• xml::iattribute_frame
• xml::fattribute_frame
• xml::sattribute_frame
• xml::attribute_elem
• xml::iattribute_elem
• xml::fattribute_elem
• xml::sattribute_elem
• xml::link_frame
• xml::attribute_exists_frame
• xml::count_attributes_frame
• xml::count_attributes_elem
• xml::add_attribute
• xml::path
• xml::get_xmlelement
• xml::count_children
• xml::get_child
• xml::get_name
• xml::get_parent
• xml::release
• xml::exec

XML tag support

The renderer now supports the InDesign® XML structure and XML elements for frames.

XML elements for text, tables and cells are not supported!

Opening an image with a missing clipping path will fail on comet_pdf. InDesign® will open the image without a clipping path in the same situation.

In this situation, comet_pdf now opens the image without a clipping path.

• frame::get_name
• frame::set_name

• frame::getbbox_before_adapt
• frame::get_nail
• frame::incoming_magnets
• frame::outgoing_magnets
• frame::get_magnet_type
• frame::get_magnet_is_white
• frame::get_magnet_is_rotation_only
• frame::get_magnet_reference
• frame::rotate
• frame::get_rotate
• frame::scale
• frame::get_scale
• frame::skew
• frame::get_skew
• frame::reimport
• frame::reimport_all
• frame::reimport_selected
• frame::reimport_list

• textmodel::get_parastyle
• textmodel::get_charstyle

• text::replace_all
• text::ireplace_all
• text::unix_to_win
• text::xpress_to_tagged
• text::replace_typografics
• text::fortune

• document::get_bleed
• document::set_bleed
• document::get_slug
• document::set_slug
• document::get_pageref
• document::get_spreadref
• itemlist::selected
• itemlist::get_selected_frames
• itemlist::select

Overprint

Overprints are now supported for frames, strokes and text.

Please not the following restrictions:

• Gap colours of strokes using the overprint of their strokes.
• Gap colours in rules above/below using the overprint of their strokes.
• Underlines and strike thrus using the overprint of their texts.
• Overprints in tables are not implemented for now.

Text is exported - but only in a size of 0.01 pts.

This happens, if the text has a trailing horizontal text scaling of 1%. Resetting scalings after using it solves the problem.

If you simply create a PDF by using -i the metadata export fails while creating temporary PDFs of single pages.

Fixed

Writing object styles to w2ml will crash down the renderer.

Fixed

Using option -af you can draw text insets and gutters into text frames. But this only works in the first frames of text chains not for the remaining frames.

Fixed

Compose PDFs

Multi-columns in text frames

Insets in non-rectangulare shapes are done by path scalings in the past. Of course, this is not the best solution. Therefor we implement a new and complex technique to calculate path out- and in-lines.

In the screenshot you can see an (for this case) extreme situation. The red triangle is the scaled version of the blue triangle and was used as to be the inset path for the text in the past. But the correct solution would be the text as shown here. And, well, exactly this is done now!

Text wraps

Renderer now supports text wraps. To use text wraps please use at least R9900 to create w2ml's.

Limitations

• Rotated and skewed frames are ignored for now.
• On non-rectangulare frames, only completely overlying wraps are allowed. Or, in other words, wraps must not intersect the shape!

Im Bild sehen Sie links, wie der Text um den grünen Stern läuft. Der rote Stern dagegen liegt nur teilweise über dem Text. Hier ist die Textverdrängung nicht möglich. In der Ausgabe wird in diesen Fällen eine Warnung geschrieben:

Non rectangular frame 281 has text wraps with unsupported partial intersections.

Hinweis

Die Einschränkung resultiert aus einem Implementierungsdetail der PFDlib und kann (mit gewissem Aufwand) beseitigt werden. Als Feature-Request erledigen wir das gerne, für die Standardanwendung erscheint uns der Aufwand momentan zu hoch.

In text chains inlines were drawn ones per chained frame, and as a result of this, transparencies are multiplied.

Fixed

In the past we set individual transparencies and blend modes for strokes, fills and contents. As a result of this, transparent text was coloured always a little bit by the translucent background color.

Now we can 'bundle' transparencies and blend modes for the whole frame. Here's a preview from a PDF showing different combinations of transparencies:

• frame::set_objectstyle
• frame::get_objectstyle

We now support object styles! To use object style please use at least R9900 to create w2ml's

Please not that object styles are limited to following properties:

• Fill
• Stroke
• Stroke & Corner Options
• Text Frame General Options
• Text Wrap & Other
• Anchored Object Options
• Transparency

Spreaded PDFs

Using the new option

    --spreadwise

you can create PDFs with spreads instead of single pages.

Save as w2ml

    --autosave

you can create a w2ml version of the resulting document. The w2ml version is generated in the same folder like the PDF.

Especially large documents with dozens of master pages and hundreds of styles will need a very long time to open. We therefor re-implemented the whole part of the renderer that reads the w2ml.

Documents, that need 600 seconds before are now read in 0.15 seconds. 4,000 times faster!

priint meta data

Using the new option

    --metadata

you now can create the priint meta data of the generated document. See online help or use option -h to learn more

If a table contains merged cells, inlines and images inside the table are placed into wrong cells.

Fixed

If a text contains inlines after tables, this inlines are placed at wrong text positions.

Fixed

If I use <layer> in a place holder statement and the place holder is inside a table cell, the answer is always empty.

Fixed

If a text chain contains inlines, artefacts of previous frame are shown at the next page.

Fixed

• image::alloc
• image::release
• image::bytes

If the renderer writes an output w2ml (option --autosave) the numbering styles are missing in the file.

Fixed

Embedded images

• frame::embed_image
• frame::embed_file
• frame::has_embedded_image
• frame::export_embedded_image

Comet Plugin Base 4.0.5

Renderer is now Comet 4.0.5 based and will follow the head version of the Plugins now.

ATTENTION : Old Comet3 based renderers may need a new licence file!

Rotations and skews

We now fully support InDesign® frame rotations and skews.

ATTENTION : If your InDesign® document uses rotations and/or skews, the files must re-exported to w2ml again!

Magnets may reset image positions set by layout rules.

Fixed

Comet notes

Calls to system::commit_global will force an alert, that the function is not implemented for the renderer - but it seems that the function works well.

Yes, the function works well. The alert is removed now.

The function system::setdatafile is marked as available for the renderer in the docu. But calling this function will lead to a warning and the function does nothing.

This is fixed now.

But take care: The function will change the data files definition in the database too!

Styled corners on text frames may lead to wrong text insets.

Fixed

Tables are placed without left inset if the text frame has some styled corners.

Fixed

Sometimes text is placed with double sized insets. What happens here?

This error occurs an frames they had styled corners in InDesign® in the past, but the corner radius is set to 0 in the mean time.

Fixed

TaggedText tags may contain escaped <, >, \ characters. But obviously they are miss-interpreted.

Fixed

Unnumbered and numbered lists

• page::get_margins
• page::set_margins
• page::count_columns
• page::get_info
• page::set_info
• page::templates::get_info
• page::templates::count_elements
• page::templates::get_element_info_by_sequ
• page::templates::get_element_info_by_index
• page::get_spread
• page::create
• page::duplicate
• page::set_number

Frames with an incoming bottom magnet and an oposite nail at the top are resized well - but at the reference point left-top, not right-bottom.

Fixed

If the last frame of a product is a line, the distance to the next product is wrong. Obviously the line is ignored for bounding box calculations.

Fixed

Pre/Postfix of place holders

Renderer now supports the Comet pre/postfixes for place holders.

ATTENTION: In the current version, text is only inserted! If a place holder is loaded twice, old prefixes are not deleted.

After loading all place holders one may ask for text place holders (linklist::collect). This failed because place holders are lost while loading.

Fixed

Sometimes table::cell::get_stroke returns wrong results.

Fixed

• page::get_str
• page::get_str_by_index

• itemlist::rmv_magnet
• image::setclip
• itemlist::set_alpha_channel

Some cells are not loaded after building the table.

Fixed

Place holders in completely inserted tables (PubServer tagged text) are loaded two times.

Fixed

• frame::get_corner
• frame::set_corner
• frame::get_blendmode
• frame::get_smart_item_data
• frame::set_smart_item_data
• table::cell::get_stroke
• table::cell::get_strokecolor_rgb
• table::cell::get_strokecolor_cmyk
• table::cell::get_strokecolor_lab

Document Reorganization

• productlist::reorganize
• productlist::get_products_of_document

Table place holders

Sometimes empty paragraphs are inserted after tables.

Fixed

• xml::set_document_attribute
• xml::get_document_attribute
• system::get_docwatch
• system::set_docwatch
• document::getid
• document::setid

Doc watch scripts

Paragraphs with right indentions > 0 moving tables to the right.

Fixed

If a texts ends with a table, the frame is a little big to high after fitting the frame.

Fixed

Texts without any table are fitted correctly. Also texts with exactly one table (and no text around the table) are fitted correctly. But If a frames contains tables and text, fitframe failed.

Fixed

Fixed

In case of formated but empty tagged text like

%!TT<ParaStyle:> or simply '%!TT'

text place holders are not replaced by hair spaces but removed. This misbehaviour leads to errors in the following process.

Fixed

'Potatoes' and cornered frames may lead to an infinite loop in frame::fit.

Fixed

PDFLib doesn't draw single hair spaces. And, as a result of this, we cannot calculate the height of this 'letter'.

Fixed

textmodel::get seems to ignore text formats like kExportXUnitext.

Fixed

• Row Strokes in Front
• Column Strokes in Front

Please not that the stroke drawing orders

• Best Joins
• InDesign® 2.0 Compatibility

are NOT supported.

Line types 'Dots' and 'Japanese Dots'

The renderer now can draw lines using the line types

• Dots
• Japanese Dots

The new pages created by the product building process do not have master pages.

Fixed

Using the option

-a f

the resulting PDF will show the bounding boxes of all frames in the stock color defined by their layers. This is usefull for debugging cases. But all boxes are drawn as the bounding box of the outer stroke, not of the box itself.

Fixed

Using the option

-a c

the resulting PDF will show the edges of table cells. This in fact is usefull for debugging cases. But in the current version in can only draw ONE of the lines, strokes or edges.

We now draw the strokes every time, and, if you wish, we draw the edges above the strokes. :-)

After working with the renderer a while I have a very long list of short cuts. Is there any way to shorten this list in the programs out put but not in the short cuts file?

Yes. Let the description of the entry begin with the key word

HIDDEN

Thats all.

Placing images normally limits the scaling to 100%. But not in comet_pdf.

-- Fixed --

Downloading templates from a SOAP service always fails. Yes, this was an error. Templates were stored with id 'pageitem/data/...' but retreived with '/pageitem/data/...' (with a trailing /).

-- Fixed --

< and > in string IDs of place text place holders will lead to errors while reading the tagged text.

-- Fixed --

Using tagged text longer than 65 kB will crash comet_pdf.

Fixed

• textmodel::get_table
• frame::lock(nop)
• frame::unlock(nop)
• frame::is_locked

At least the image placements 13 & 14 for frame::image are not working.

-- Fixed --

Inserting unformatted text longer than one paragraph destroys all text attributes inside the inserted text.

Fixed

Replacing a text place holder by nothing ("") leads to wrong formated text behind the place holder.

Fixed

• frame::fit_image

In case of rotated images, the image placements like in frame::image are wrong.

This is fixed.

Unicode letters in string IDs of text place holders are <0xXXXX> encoded and can not used in database compares therefore.

Fixed

<0x000D> in tagged texts may lead into an infinite loop while inserting this text.

This error is fixed.

Fontnames_default.xml is ignored, if no option -P (fontmappings) is given.

Fixed - reading Fontnames_default.xml now

• textmodel::get_parastyle
• page::get_size
• frame::is_textframe
• table::remove
• table::unmerge
• table::get_cellsize
• table::cell::get_size
• table::get_cellinsets
• table::broaden_to_frame
• table::equal_cols
• table::equal_cols_by_list

--- Non ops ---

• table::get_headers_start
• table::set_headers_start
• table::get_footers_start
• table::set_footers_start
• table::get_skip_first_header
• table::set_skip_first_header
• table::get_skip_last_footer
• table::set_skip_last_footer

• table::insert_cols
• table::remove_cols
• table::build
• table::reduce
• all get/set-functions for table the module

Merged table cells are getting the concated text of all sub cells. But empty cells may contain an empty paragraph at their very beginning and we have to take care not to add them to the anchor.

This is done now.

In some rare circumstances, cells may get a wrong color tint for their fill color: If the table defines alternating fill rules but single cells are using local colours, the tint was taken from table anyway.

This is fixed.

Master pages

• itemlist::masteritems
• frame::is_masteritem_overriden
• frame::is_overriden_masteritem
• frame::override_masteritem
• frame::remove_masteritem_override
• page::masteritems_load
• module link (all functions)
• module linklist (all functions except linklist::sync)

int gParamNInt
float gParamNFloat
char gParamNString [] with N = {1, 2, 3, 4}

For example -Q "'21.5\"' 123 4.6" will define the following for param 1

int gParam1Int = 12;
float gParam1Float = 12.5;
char gParam1String [] = "12.5\"";

This is fixed.

• color::count_swatches
• color::get_nth_swatch
• color::redefine_swatch
• color::get_space
• color::get_tint
• color::get_colors
• color::is_spot
• color::is_locked
• color::get_type
• color::is_reserved

No images were visible in inlines on Window machines.

This error is fixed.

• table::set_row_start
• table::get_row_start

Please note that only

    eStartAnywhere
    eStartNextColumn
    eStartNextFrame

are supported.

%!TT<ParaStyle:>1. A<ParaStyle:>2. B<ParaStyle:>3. C

the second parastyle was lost. The resulting text was

1. A2. B
3. C

This is fixed.

• frame::set_script_tag
• frame::get_script_tag
• frame::textlength
• priint::connection
• priint::set_prefs_editable
• priint::set_pref
• priint::get_pref
• priint::use_soap_proxy

• textmodel::overset
• frame::shows_textend

ATTENTION : Exact row heights may lead to invisible cell oversets!

• frame::group
• frame::ungroup
• frame::regrouped
• frame::add_to_group
• frame::add_list_to_group

Support of repeating elements

• table::merge

SUPPORTING POSTSCRIPT FILES!

• image::barcode
• productlist::get
• itemlist::move_to
• itemlist::move_by
• placeholder::get_value
• placeholder::sget_value
• page::get
• page::get_type
• frame::remove_image

• "" : turn off cropping
• "x", x : side-cut width in points
• "l t r b" : use different side-cuts at every side

You may find the InDesign® PDF presets here:

    /Library/Application Support/Adobe/Adobe PDF/Settings
    ~/Library/Application Support/Adobe/Adobe PDF/Settings

• title
• author
• subject
• keywords

Windows version

To use layout layers, create the layer in InDesign® document and insert it in the page template entries of your items.xml into the element <layout_layers>.

• frame::hide
• frame::show
• frame::is_hidden

implemented