Pedrober
-
Posts
177 -
Joined
-
Last visited
Posts posted by Pedrober
-
-
The 2.6 version ignores this feature again. What a pity!
-
The Hunspell Spanish Hyphenation module has been seriously improved a couple of days ago. See:
https://github.com/sbosio/rla-es
-
-
No, it doesn't.
-
Thank you very much for your assistance. The laser printers I am using are a Brother DCP-8070D and a Brother HL2300D. In those printers, CMYK blacks are always poorly printed. I use RGB blacks and then the printout is OK.
-
Thank you very much for your help. I am printing to a laser printer and CMYK also creates problems with blacks. I have changed my Apub document to RGB colour but it doesn't help. Anyhow, I think you're right. There is a misconfiguration problem. If I am able to figure it out, I'll report.
Regards.
-
Excuse me. I've been (and I am) very busy. I am attaching the original .afdesign file and the .afpub file.
-
I have created a pure vectorial image in ADesigner and the problem persists: perfect printing from ADesigner (or from Preview if I use an EPS exported from ADesigner) and poor printing in APublisher. Maybe I have a wrong parameter in my Apub document that is generating this problem?
-
I am quoting some of your comments here:
The 'Placed Image DPI too low' error you see in pre-flight is caused by the stretched yellow cabinet at the top right of the graphic... Pre-flight is looking at the source DPI of any placed graphics in your Designer file and that particular graphic has a DPI of 52 along the x-axis which is why you see the error, i.e., it's below the default 72 dpi, increasing that x-axis dpi to a value above 72 dpi will remove the error.
This isn't a bug but expected behaviour when dealing with small, low-resolution image files...
-
For sure. Give me a private link to send the files.
-
I am including ADesigner files in an APub publication (inside picture frames) and the quality of the printout of these designs is very poor (same behaviour if I export the page to PDF and I print the PDF), while, at the same time, the body text outside the picture frame is printed perfectly. However, If I print the same Adesigner linked file directly from ADesigner, the quality is perfect. Similarly, if I open the ADesigner file in Apub and print it, the quality is also perfect.
Preflight messages are confusing. The Resource Manager shows the placed file dpi as 343 dpi, but Preflight indicates that the placed image dpi too low (60). This issue only happens with several ADesigner files, but the printing problem occurs with all ADesigner files inside the Apub document.
The Document setup DPI is always 300dpi in both APublisher and ADesigner, but we are working with vector.
It definitely appears to be a bug. If I open the Apub publication in ADesigner and I print the whole page, I encounter the same problem as in APub. However, if I click the picture frame containing the ADesigner file and I isolate it, the printout is perfect.
I can zoom in on the ADesigner files in Apub without any problem. Even after enormous zoom, the quality of the ADesigner drawings is perfect. The problem only occurs when I print the Apub document containing ADesigner files.
The only explanation I can find is as follows: in the ADesigner files, there are some low-quality raster objects along with text. It's as if the poor quality of these raster objects affects the rendering of the text in APub printing. Anyhow, if I delete those objects in ADesigner and export the text only to eps, the problem persists in APub.
More information: astonishing! I created a PDF from my Apub and, then, I have reordered the pages in Acrobat. In the resulting file, the ADesigner files are printed OK. Any explanation?
-
I solved this problem relinking the files, but your mileage may vary.
-
Please, include footnotes support in IDML import in the 2.6 version!
-
I'm using Catalina, but my problem is only with the button in the toolbar.
-
This bug is still present in 2.5.2 version. Please log it.
-
Unfortunately, the new 2.5 beta doesn't include footnotes support in IDML import. When?
-
Very useful and enlightening posts! Thank you very much.
-
-
-
In general, the spacing of the ellipsis is tighter than the three periods and I don't like it. As stated, it's a controversial matter in typography. The fonts I am using are Sabon or Garamond variants and this difference exists. Anyhow, by chance, the difference is acceptable in the font I am now using. Thank you very much for your message.
-
It's a controversial matter but I don't use ellipsis. I prefer three points. Unfortunately, Apub separates those three points at the end of the line in justified text, leaving a full stop at the end of the line and the other two points at the beginning of the next line. Any way to modify this behaviour? I know the "No break" attribute, but it's a manual case per case solution like other suggestions I have received.
-
Thank you very much, Walt. I'll post in the suggestions forum.
-
It's a controversial matter but I don't use ellipsis but three points. Unfortunately, Apub separates those three points at the end of the line in justified text, leaving a full stop at the end of the line and the other two points at the beginning of the next line. Any way to modify this behaviour? I know the "No break" attribute, but it's a manual case per case solution.
-
I hope the 2.5 version inlcudes at last this feature!
Footnotes support in IDML import
in Feedback for the Affinity V2 Suite of Products
Posted
I hope APub 2.7 includes footnotes support in IDML import. Am i a fool?