-
Posts
2,699 -
Joined
-
Last visited
Reputation Activity
-
-
Petar Petrenko got a reaction from Alfred in "Rasterize" an image?
Sorry for my Indian English. I hope it is better than your Macedonian?
-
Petar Petrenko got a reaction from Fixx in "Rasterize" an image?
IMO, until the image is not rasterized, it acts like a "smart object" in Photoshop.
-
Petar Petrenko reacted to RNKLN in Affinity Spotlight
In the meantime, it would be nice if somebody could share the two magazines. I haven't been able to find them on my hard drive, somehow. Such a pity. 😥
-
Petar Petrenko reacted to PaoloT in Affinity Spotlight
Creative Pro is not published by Adobe, but by an independent team.
Paolo
-
Petar Petrenko got a reaction from sbe in Request: Replace "Leading Override" with "Leading"
And this is not only true in this case. There are plenty of situations where you need to make unnecessary clicks which slow down the work.
Yes, one of these is Swatches panel.
-
Petar Petrenko got a reaction from PaulEC in Auto fit stock photos
Hi,
I think it would be nice if we could have an option to auto fit proportionally a stock photo to an artboard/page, while holding some modifier key.
-
Petar Petrenko got a reaction from NotMyFault in Auto fit stock photos
Hi,
I think it would be nice if we could have an option to auto fit proportionally a stock photo to an artboard/page, while holding some modifier key.
-
Petar Petrenko got a reaction from PaoloT in Auto fit stock photos
Hi,
I think it would be nice if we could have an option to auto fit proportionally a stock photo to an artboard/page, while holding some modifier key.
-
Petar Petrenko got a reaction from Alfred in ¿HowTo: Convert between Art Text and Frame Text?
SHIFT = unproportionally resize;
CTRL = proportionally resize from center;
SHIFT+CTRL = unproportionally resize from center.
-
Petar Petrenko got a reaction from Old Bruce in ¿HowTo: Convert between Art Text and Frame Text?
Try together with SHIFT key.
-
Petar Petrenko got a reaction from Alfred in ¿HowTo: Convert between Art Text and Frame Text?
Try together with SHIFT key.
-
Petar Petrenko reacted to PixelEngineer in Bug in converting PDF to Publisher
Sorry your having difficulty with this.
I don't believe that this can be officially classified as a bug in Affinity Publisher, due to the following observations. We are simply dealing with a corrupt document that was exported from another application or via transport over a network.
I was able to confirm that the original file showed evidence of corruption upon either export from InDesign and "Quartz PDFContext" on an Apple computer or through file transmission. I have also heard of situations like this where Acrobat will also find the document corrupted. The fact is here is that we are dealing with a corrupt file, this happens with MS Word documents, Photoshop PSD files I could go on and on. If an app opened this file up it is going to end up being a garbage in and garbage out situation, which is what we have here, but that is not due to Affinity Publisher. The problem is how this particular source file was created and generated using those other apps and what occurred during transport plain and simple.
It seems that Affinity Publisher does not have the problem here.
This could've happened due to numerous issues technical issues on the end of the user that exported the file or even through e-mail transmission over a network. Was this file sent to you in a zip file? As I mentioned the incompletion of data packets could be due to a number of issues which are numerous. PDF apps like Acrobat will attempt to fix corrupted tables but there is no guarantee depending on what was broken. There are so many variables.
BTW, I was able to successfully see the wording in its true form after using special tools, but even then you need to have those fonts installed in your system (some that may require a license). The first jumbled text BTW said HAL ELROD's. Whoever sent this particular PDF needs to establish better guidelines to check the integrity of every PDF file before sending them out, its not impossible and it doesn't have to be expensive either. I don't recommend wasting your time working with any corrupt files sent to you. Your time is too valuable for that. At least we now confirmed that the file was corrupted from another source to begin with.
-
Petar Petrenko reacted to kenmcd in Bug in converting PDF to Publisher
Most of my PDF editors/converters could not convert that text.
Nitro Pro displayed a warning about non-standard encoding.
PDF-XChange displayed a warning: Errors detected in the XREF table
FlexiPDF, PDF-XChange, Nitro Pro - export to Word did not work.
Infix PDF, Master PDF - export to text did not work.
Surprisingly, Foxit PDF Editor did export to Word correctly.
So it appears it did correctly figure-out the encoding (or guess).
On the majority of the text the encoding is marked as Custom or Built In.
The three text blocks which cause problems are marked as Identity-H encoding.
There is no reason for those particular pieces of text to be Identity-H.
They are just plain Latin text characters which are in the most common encodings.
The document was created with InDesign 16 on a Mac, so the PDF library is Quartz.
Not sure why it would single out those three blocks of text as Identity-H.
Above, after a quick look, I originally stated that APub was displaying the Unicode codes that are there, but it is not. It is display something else. The codes I see under the characters are all wacko, but they are not what is displayed. So I am not sure what APub is doing.
In theory, because Identity-H is a standard character map, you should be able to go from the embedded fonts character IDs (CID) and translate that into the correct Unicode code points, completely ignoring the PDF ToUnicode table. Dunno. Makes me crazy.
Their back-end application touts its ability to deal with non-standard encoding.
See: https://player.vimeo.com/video/574161060
So not sure if that is the best example, as most apps seem to have a problem with this.
This is a different issue - which caused a lot of issues with LibreOffice compatibility with Word.
Word uses a symbol font (non-Unicode) for the bullets.
The font is also called Symbol (file symbol.ttf).
In the font file the PostScriptName is SymbolMT (which is what you see in the PDF fonts).
So what happened with LibreOffice is they want to be able to round-trip documents with Word users on Windows, and LibreOffice user on Linux, etc.
LibreOffice does not always have access to this Windows font (e.g Linux users).
So they needed to get the bullets working on multiple OSs and applications.
It stopped working on LO on Linux, then it did not work on Windows, etc.
They finally got it working.
When you paste the bullets and the text, the first thing the app sees is that bullet, and that bullet is a symbol font, so it guesses that the text is all the same, and you get a mess because it thinks it is all symbols.
If you paste just the text, it only sees the text as a normal Unicode font.
If you import the DOCX it does bring both the bullets and text correctly.
-
Petar Petrenko reacted to AlanPickup in Bug in converting PDF to Publisher
Whilst I acknowledge Libre Trainings expertise in type, fonts, Unicode's, hidden control characters, etc there must be more that can be done.
Opening PDF's is one of the biggest headaches I have with Publisher. If I convert NNN's original PDF to word using an online tool (Ilovepdf) it does so without problems. I know that the original probably came from a word doc exported as a PDF, but if I copy and paste the text into publisher it gives the right characters. There are many of us who do work free of charge for small groups and charities who welcome Publisher as a stable tool at an affordable price, but most of the text for our work comes in word document format, dealing with bullets and numbering copied over is a nightmare. If you open a pdf it recognises the Bullets, but gets characters wrong, if you copy and paste it recognises the characters but not the bullets. You also need to be aware of paste or pastes special.
Whilst I accept using the place to get things right, which I often do with commercially prepared leaflets being inserted into a publication, it means any alterations are a start over in the original pdf/doc.
Not being a user of other commercial software, I cannot compare how they perform these tasks
-
Petar Petrenko reacted to stokerg in Bug in converting PDF to Publisher
Hi @NNN,
Thanks for the files.
I can replicate the issue and will get this logged with the Dev team.
If you just need to display the PDF, you can use File>Place and place the PDF on the page and the PDF will be displayed and exported correctly.
-
Petar Petrenko reacted to vdamjanovski in Affinity Publisher crashing too often
Thanks NNN for the suggestion, but I think it might be too late now, as I used an old version of InDesign and not sure if IDML was available then.
I also remember with every new version of Indesign, older ones could not read their own previous format, which was annoyance for my printers with older versions, so they advised me to always save it in PDF.
-
Petar Petrenko reacted to Wosven in Chapter page and decorations
I'm in the same situations @NNN — years of using differents apps, and using this trick when appropriate. Since I'd rather have a one story book (linked frames), that cut them in separate linked ones for each chapter.
It all depends of the book, but with only text books, this method is faster and less prone to errors. And you don't need to check ±130 chapter head or less, manytime each time you add some modifications, in the text or the design. Especially if you've got a huge amount of sometimes large footnotes. Scripting is a plus for this type of work on books.
Working with separate chapters is fine if you have the final text from the start... or few chapters, but it never happens with live authors and proof readers
-
Petar Petrenko got a reaction from Wosven in Chapter page and decorations
Hi MikeTO,
I have 30+ years of experience in DTP. Does it qualifies me of knowing this "trick"?
I've done hundreds of books, magazines, brochures... Single story, multiple stories books, multiple files organized as "book"... PageMaker, QuarkXPress, InDesign (last 10+ years) and now Publisher, but nothing seriously because last few years I'm orinted toward books and Publisher lacks foot/end notes (waiting for them to appear in v. 2.0, hopefully). I think this enhancment I am asking for will speed up the process a little bit.
-
Petar Petrenko reacted to MikeTO in Chapter page and decorations
Apologies, I was confused by somebody else's reply to you
-
Petar Petrenko reacted to firstdefence in Arc tool?
Use the donut shape, set the Hole Radius to 100%
Take a look at the settings from the context bar above the workspace.
They produce this arc...
-
Petar Petrenko reacted to Dan C in Is this a normal behaviour?
Hi @NNN,
Thanks for your report and file provided! I've been able to replicate this with your file and I am logging it with our developers now - as there are no constraints applied, I would not expect these layers to move when being grouped.
I hope this helps
-
Petar Petrenko reacted to Dan C in What am I doing wrong with circles?
Hi @NNN,
Thanks for your report and our apologies for the delayed response here!
I can confirm that the issue of dashed strokes not being displayed when a pressure profile is applied is already logged with our developers - however I don't believe that this includes the strokes having the pressure removed and returning to dashed lines when exported.
I can see why it's beneficial to export with dotted lines as that's whats been set in the app for the stroke, however the exported document then doesn't match the canvas visually, which can cause confusion (leading to threads such as this!)
Therefore I'm updating the development log now to include this information, so that our developers can discuss and hopefully find a solution that works for most. if not all
-
Petar Petrenko reacted to Pšenda in Is this a normal behaviour?
This is probably an bug(?), where nested objects from groups/layers are incorrectly(?) merged into a next group. If parent layers/groups are selected, they will be merged into the next group correctly. So the question is - how should merging nested elements from two different groups/layers actually work properly?
P.S. not only will the objects be moved from one group to another, but the position of some elements will also change - which I think is a bug. This bug (position change) does not occur, if they are both Layers.
-
Petar Petrenko reacted to R C-R in Where is the Preset?
They are not really "accurate" for several reasons, one of which is those 3 "magic" R/G/B values are just an average of the relative sensitivity of a large sample of people, but even for one person that can vary depending on their age, eye fatigue, time of day, & several other factors. Also, eye sensitivity varies depending on where in the spectrum the color is located, because there is considerable overlap in the sensitivity of each of the 3 color receptors, so many shades will be sensed strongly by one sensor & weakly by another.
Lots more about this at https://www.cambridgeincolour.com/tutorials/color-perception.htm
As you can see from that, there are wavelengths where a typical human eye is equally sensitive to red & blue green.
So really, the 'magic' values are a good starting point but as others have said you probably will need to tweak them to get something you are happy with.
