Leaving-Adobe
Members-
Posts
29 -
Joined
-
Last visited
Everything posted by Leaving-Adobe
-
Affinity publisher file corrupted
Leaving-Adobe replied to Apm89's topic in Affinity on Desktop Questions (macOS and Windows)
Same with my current Version 1.10.6. The .afpub file still works so I would call it corrupted but each time I save it it grows. The original 34mb file became in the first step 845mb and then grew save-by-save until 1,1gb. I have 24pages - so I would want to copy all of them to a new document. Preparing this answer I realiced that rather the whole build must be corrupted: I killed one element after the next in order to find the error. I saved several steps, all 1,06gb fat files. In the end I had a BLANK PAGE. 1,06 gb. Thats so crazy that I opene up a new thread. Did it happen in/with another file to you?! Sebastian -
Hi! I was just about to write below this post. Now the situation is so absurd that I better opened up a new thread: My Publisher made a usual 34mb file become 855mb after opening and saving it. The second time saving made it 1,07gb. Deleting the elements and pages took some 200/300 mb,then it rose again. Attached you find the "end": A blank document weighing 1,06gb. Wow. Other files I created or re-opened/saved behave normally. Any idea what that is? How can I "save" the original 34mb file?! Thanks and all the best Sebastian
-
No seriously working DTP person would "just install" a him/her totally unknown programm that - moreaover - is not just "same same as Indesign" and print a book, work sth. out or whatever. They had to get used to it in order to "guarantee" the qualitiy they stand for. Do you pay their hours to do so, too? My DTP and visual collegues learned Adobes Creative Suite as I did 20 years ago at university od arts. After aprox 20-30h working with publisher I would say "ok, I get along with it", but exporting a print pdf for a expensive book or so - puh...one wring setting and you waste thousands of euros and lose possibly a customer or two...
-
Wouldn't altering IDML piss off a lot of Indesign users, too? What does altering mean concerning re-adaption. Is this really a point?
-
"Not intented" doesn't mean it's illegal. So far I've not seen one concrete point why AP isn't supporting IDML. Furthermore it irritates me that this point "INDD is a closed format" is repeated and repeated again. What for? Do you want to compare with greedy Adobe? No. Is there a easily handable alternative within Adobe Indesign? Yes. It's not about INDD, it's about IDML
-
It's already embarassing to ask my service provider "Sorry dude, my Affinity Publisher could read your kindly provided .idml file but isn't able to export one. Could you please use this and that (add on / work around etc.) in order to..." But even if we were willing to handle that problem by passing it to our partners: the 200$ Converter mentioned here is discontinued. Why could that be? Am I one of just a few publisher fans that isn't working in a "affinity bubble" but rather trying to CONVINCE the de facto Adobe users to also swop to Affinity. How could I convince them if they are not even able to have a look on my work?! Could someone responsible pls. explain again, why exactly it is not affordable to invest in an export option that writes the currently (!) used .idml standard?
-
Do Affinity's programmers / deciders really think that Adobe would alter its .idml-specs as soon as Publisher is able to export into it? And even if they did: Isn't the hassle to adapt to eventual changes in .idml worth it - comparing to the trouble we professionals have NOT BEING ABLE AT ALL to share our work with the rest of the world who still mayorily uses Indesign? Isn't that ignoring facts? To let us Publisher fans force or at least convince service providers or collegues to "also buy, install and learn" Affinity isn't nice. To say "Well then you're better off staying with Adobe"s subscription trap hell, neither. To be honest: I just realice Affinity Publisher is a dead end road concerning colaboation – i would have never though that and it annoys and saddens me. 😞 Sebastian
-
Counting mechanism
Leaving-Adobe replied to ophuzii's topic in Feedback for Affinity Publisher V1 on Desktop
Still a needed feature. In this thread BTW people were already A YEAR before explaing, why word and acharacter count is so crucial: -
Copying data into tables
Leaving-Adobe replied to riball's topic in Feedback for the Affinity V2 Suite of Products
Unfortenately you are right! I tested it with just one row - only with this tiny amount of data it doesn't crash.. -
Copying data into tables
Leaving-Adobe replied to riball's topic in Feedback for the Affinity V2 Suite of Products
Hopefully we will once be able to maintain the format of cells in which ne data is being pasted in -
Linked Text Documents
Leaving-Adobe replied to Archangel's topic in Feedback for Affinity Publisher V1 on Desktop
In order to make Publisher ready for group projects it would be great when for example publicly shared Google or Next Cloud Documents could be linked into text frames, i.e. be "ingested" be Affinty. In this case even some basic formatting feature could be overtaken. In the resource manager we could switch between linked/embedded and refresh an online source, too.- 10 replies
-
- affinity publisher
- word
-
(and 7 more)
Tagged with:
-
Search all missing links at once
Leaving-Adobe replied to kenmaclord's topic in Feedback for Affinity Publisher V1 on Desktop
talking of recopenig indesign docs and having to relocate dozens or more of links: I miss an option to drop a missing file when relocating many links. Without such a "drop" button I have to stop the process or relink a fake graphic in order to go to the next missing link.. -
Hello! See attached screenshot: My publisher document is 1024 x 720 px, one of its sources 1455 x 2000 px. According to the "ressource manager" it is placed with 219 dpi. How can that be? Facing the pixeled output in Macs Preview (up left) you see it's definetly coming out with 219 or worse - its a 100% jpg. Any idea what could be wrong? All Affinity products are uptodate as well as my Mac Big Sur is. Thanks and all the best, Sebastian
-
I prefer to work time-economic. Therefore Adobe's integrated html feature was absolutely senseful because it's often the person who made the graphic who is ought to deliver the whole image map. I see that follower and friends of Affinity are proud and fond on/of these Affinity products. But to tell me or other people should write the html code for image maps themselves is ridiculous. The code itself is not so complicated, I know html basically since 20 years, but any image map (code) creator saves us tons of times. As long as Affinity doesn't have that feature one can use https://www.image-map.net – eventually there are even better services out there, but it worked for me.
-
Hyperlink on images Affinity Publisher
Leaving-Adobe replied to Albo's topic in Feedback for Affinity Designer V1 on Desktop
Ok, I guess that is a problem for many who can't or don't want to work anymore with Adobe Illuustrator. Hopefully it is being implemented soon.