Jump to content

Search the Community

Showing results for 'package' in content posted in Discussions and Suggestions for Affinity Publisher Beta on Desktop.


Didn't find what you were looking for? Try searching for:


More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support Forums
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Affinity Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 84 results

  1. I'd prefer to use function of making Package of all linked content to one Folder.
  2. I made a Swedish hyphenation dictionary from the Open source files at Libre Office, but it's getting tedious to install them in the actual application package every time the beta expires and there's a new version available. Couldn't the language dictionaries be stored somewhere outside the app package? For instance in a /Documents/Affinity/Dictionaries/ folder. I attach the Swedish hyphenation dictionary folder for anyone who wants to use it when trying out Publisher. sv-SE.zip
  3. No preflight! In Indesign it is File> Package. In PP: Saving as packages It can be really frustrating when you transfer a file to another computer only to find that you are missing either an image or a typeface. The “Save as Package” feature allows you to gather together all the files that you’ve used in a publication, including fonts and linked graphics, for easy transfer to another computer or to a print bureau. When you package a publication, you create a special PPP file that contains the linked resources. This can be opened and extracted at a later date and will preserve the file links. This method allows you to continue work on the publication, without having to worry whether you’ve overlooked supporting resources. By including resources such as bitmaps, movies and sound files, regardless of whether they are linked or embedded, documents can be guaranteed to open on any machine. Including referenced fonts ensures that they will always look the same. To save a document as a package: Go to File>Save as Package… Type a name for your publication and choose a destination folder. Click Save. The Save as Package dialog appears. Check the Fonts option to include any font files within the package. The Linked Resources option is checked by default. Click OK. The file will be saved as a PPP file, but one that has special properties that allow PagePlus to recognise it as a package when it is next opened. Close the publication. When you save the file as a package, the file size will increase as it will include all of the resources and/or font files that have been used. Please bear this is mind if you intend to email the document as an attachment!
  4. Hi guys thanx for this beta, it looks great! My suggestions: - Lock guides (also in Affinity Designer) - Package whole document - Implementation of GREP - Implementation of Nested text styles - Make master page from actual page - Import or place text from Word, tables from Excel
  5. Yes, updating and improving code is important. That's what I was doing, learning new fonctions and new way to do things when it happened. But I expect Affinity teams to know what they are doing, since those new programs are — from what I read — faster, and more efficient than their old ones. Perhaps, once they have completed the 3 main applications, they'll use a "common files" folder too, and the apps' folders will be lighter. But I wouldn't compare with Adobe apps, since their apps aren't perfect (the current version of PS I use need waiting few seconds before doing anything to an image… even a shortcut, perfect excuse to test AP at work!). On the other side, they have more feature too. I found more worrisome the files' size. Usually, sending an archive of all the needed files for a project (file, images, fonts), is a big/huge package. What about project made with Affinity suite?
  6. Preflight: https://helpx.adobe.com/indesign/using/preflighting-files-handoff.html Better check before saving! If I recall correctly, the preflight options on older versions had the option to package in the preflight tool.
  7. I miss the package order of InDesign or Quark. Or i don't have found it in the menues of publisher
  8. This is not always the case. Restricted fonts are not included in a PagePlus package, but PP doesn’t warn the user about such omissions.
  9. A I have understood, a docx is essentially a zipped package of XML files. It shouldn't be too hard to come up with a pretty convenient import tool for that. But I also understand that as long as you can copy-paste the text from the text processor of your choice, it's not the most urgent feature to build.
  10. CS 4 has a (relatively) simple workflow. I know a pro who uses it regularly—because it's familiar. He also has CS 6 for more complex issues, like handling more recent RAW files. But CS 4 does most of what he needs to do. And he's in no hurry to upgrade his OS, despite my warnings about security issues. I wouldn't put him on Mojave in any case. Too many problems. Real substantive changes, like APSF. So, yes, pros get stuck in ruts, just like anyone else. Change is challenging and for some people it represents totally unnecessary hassles, not to mention expense. I use CS 4 to run my Epson scanner software, which has not been updated for 64 bit apps, like Photoshop beyond CS 4. But I also have CS 6 and Photoshop CC, with Lightroom in Adobe's photography package. InDesign, however, has not been discounted, which is why Publisher is appealing.
  11. For the very very Last Time: CS5.5 works in the latest Mac/Mojave. Partition your disk and install High Sierra to be on the safe side. Try to install CS5.5 I have illustrator but still I do all my illustrator-work in Indesign. For me that works. So for your needs, you wouldn’t need the whole package. (However Adobe seems to coerce one into renting the whole lot.) If you absolutely need to go to CC, look out for education version. (Adopt a kid in the neighbourhood, it’s cheaper. Or take a temporary job as volunteer to teach in primary school ) In general, going back to 1985 isn’t fair. Even simple text files from that period loose their formatting when eventually opened. I do not understand how a pro can get stuck with CS4. best regards, Over and Out cb
  12. I do not understand the persistent moaning about Indesign files. Export to pdf & archive. For text, click in text & export to Word if that is the problem. Perform "Package” for all non-text. Ask a friend how you to batch (or automate) this, in case you want to do that with ‘many’ files. If this is not sufficient, simply use... Indesign. I do not understand the need for opening Indesign files. Nobody sends Indesign files to someone else. An Indesign-file is only in use as long as your job has not been finalised. So what is the problem ?
  13. There are scripts that can batch open & save as an IDML or package and also save an IDML in the process. They can save a lot of the grunt work. As regards AI files, do note you are only opening the PDF portion of an AI file. By default, AI saves a PDF inside the AI file. But if you turn that off, AD cannot open an AI file. As regards IDML, how faithfully an IDML will be opened will be an on-going effort by Serif. Both applications I use that can open an IDML have updates to the routines that do this in order to fine-tune how faithfully it works.
  14. InDesign has a File > Package... command that collects the InDesign document, along with fonts used and linked artwork into a single folder. This makes it easy to collect all the necessary assets for a single project to either archive or to share with a printer or collaborator. Does/will Publisher have a similar feature?
  15. Well, I was not thinking of the SVG drawings, I was thinking of the format using the CPAL and COLR tables of an OpenType colour font. For me, Affinity Publisher should be a first class software program, so that it is not a question of "Well, if you want features like that, you need to get EXPENSIVE PACKAGE that is EVEN MORE EXPENSIVE PACKAGE if bought in the United Kingdom" but that "Well, that Affinity Publisher software from Serif is amazingly modern, even futuristic, notwithstanding its budget price." For example, I have already noticed the feature that all of the Universal Character Set can be accessed as characters (rather than just as glyphs) and that the characters can be extracted from a PDF that has been produced, even that the underlying text can be extracted from a PDF that has been produced where there are ligature glyphs used in the display (subject to the font having suitable glyph names for ligature glyphs so as to facilitate that extractability). For me those are significant advances over PagePlus. So, while I appreciate that things take time, and there is not the thing about priority, I hope that such features are on the agenda. I wonder what is the target market for Affinity Publisher. For example, there was a time when PagePlus seemed, over a few updates, around PPX3 and PPX4, to be focused on printshops, with PPX5 OpenType capability was introduced. I first started using PagePlus with PagePlus 9 because it included the ability to produce PDF documents. PagePlus 12 allowed plane 0 characters to go to PDF as characters rather than convert to curves and PPX5 introduced OpenType facilities. My publishing is as pure electronic publications on the web. The OpenType facilities in PPX5 I found to be great. I was able to use them to test fonts that I had made using the High-Logic FontCreator program. I have found that sometimes it takes quite a while for Serif to introduce a new feature, yet when they do, they do it extremely well. William
  16. Hi there, thanks for releasing this new application, it looks great. I would like to swithc from InDesign to your Publisher. Could you please add the the package document feature? I would really need this feature, package whole document into one zip file including all imported images, files and fonts but keep it accesible as a separate files... in a same way as InDesign does. Thanks. Regards Pavel
  17. Linking photos is good. A function such as Indesign and PagePlus would be better. There you can save the file as a package. All images, graphics and fonts are saved in one folder and the program is told that the location of the images is now in the package folder. This is useful if, for example, you have to send the typesetting files to an agency, the publisher, etc. If you rename your image folder or move it to another hard drive or uninstall the fonts it will be hard to make everything available for AP again. I hope the publisher will still get this feature.
  18. First, excuse the English written here. I do not speak or write fluently, but this will not stop me from trying to help in the development of this tool that can be cheaper and accessible for everyone compared to Adobe. My suggestion to developers and programmers would be to create a fourth tool for the Affinity family, in which it makes the package of any company file. It could be made available for free and track all Affinity applications. With that you would not be copying and would not be accused of plagiarism by Adobe. The action of the new application would be to collect and save to a folder all files related to that Affinity file, such as Photo, Designer and Publisher, which would be: fonts and images (even embedded ones in the resolution being made present within the file). The operation, for me, would be simple, open this new program, go in the option to generate package of the file and this would appear as a folder where the user determines itself. I hope this is viable.
  19. Coming from InDesign, I was particularly looking forward to seeing how Publisher handles links and packages. So far I've gathered that it embeds resources by default, but that you can release the embed and change the setting to linked in the resource manager. But is it possible to package and collect all files as it is in InDesign? Say you have a very large document with 20-30 GB worth of links and you want to send it over to someone else to finish the project. How would you go about that in Publisher? Will the document file size be 20-30 GB in that case? Sometimes I send the InDesign file without links to other people, so they can see the layout. In that case it would be quite cumbersome to include all resources. And what if you only wanted to send a couple of the linked files - how would you easily access those files from within Publisher? I don't see a "Reveal in finder" option for linked files.
  20. I work with InDesign since version 1 and have to say I like how Publisher looks and works. There are attractive features there! One thing I probably missed if not I really would love to have is the option to package items like used pictures and fonts.
  21. Exporting a PDF file is one of the most important things a Publishing package must do accurately. I will quickly pitch a publishing package if it cannot produce a quality PDF file. If this is a problem, I hope it will be fixed. I bought Affinity Photo yesterday and Affinity Designer a month ago. But I will pitch both if I can't get a quality PDF from Affinity Publisher as Carrieph2 says.
  22. They, Serif, likely will never open INDD files directly. It would be a moving target as Adobe changes the file specs often. Serif might be able to create a routine that can go a long way around the INDD issue. But I doubt it would be worth the hassle. Best to plan on a script or plug-in that can open ID files and create a package with them which can also create the IDML automatically. There are free scripts (I've posted one such link) that can simply walk through a folder structure. Set it to work over a weekend or two. Mike
  23. When working inside of a company, even a small one (like the 8-person company I worked for before I went freelance again), with separation of labour, these are the kinds of workflows we're dealing with. Heck, even in most professional work I've done individually as a freelancer, I wasn't even asked to do colour correction or retouching because the materials arrived at my digital doorstep in ready or near-ready form. I'd say more than half of the use cases in the DTP market – save perhaps for a zine/self-publishing thing, and herein lies the issue if that's the market Serif is aiming for –, benefit more from layout automation than from cross-app file manipulation. May I remind you that I've worked on events, both of the artsy and the medical (really boring) kind, publications (both just the book covers and the whole enchilada, with hundreds of images and hundreds of text pages)…? Never once have I missed this functionality. I keep all my files tidy, and I can get at them quickly and relink them in a heartbeat (well, I only wish right-clicking them in the Links panel wouldn't grind InDesign to a halt, but that's a whole 'nother matter). Not being able to quickly set thousands of words and resize my layout so I can check, on the fly, how they behave, on the other hand, is an absolute non-starter. I'm not questioning your assertion; of course it would be the reverse for other projects. A minority of them. Which would still be doable without said cross-app editing feature, whereas the projects I am speaking of just can't be done in a serious and professional fashion without basic DTP features. I know this sounds very “road-to-Abilene-ish” (and am I repeating myself here? It certainly feels like it), but it's better to have a decent app which appeals to everyone, professionals and prosumers alike (i.e. current users of Adobe CC, Serif's actual competition and the package it will be compared to by default by reviewers, whether any of us likes it or not), than a superb prosumer app which will be completely panned by professionals (i.e. which will only appeal to users who are content with apps like Corel in the early days, Serif's own defunct Plus suite, MS Publisher, etc. etc.). The latter scenario would make Publisher effectively DOA, whereas the former would buy it some time to limp along with the rest of the Affinity suite while it played catch up with InDesign. While not an ideal situation, that was precisely how Adobe killed Quark in the long run, so I wouldn't be betting against Serif just then if that was the case. I stand by what I've said: if Serif is investing on that functionality over the missing stuff some people have been clamouring for here in the forums, that's utterly misguided. There's no point in differentiating from your competitors if the basics just aren't there, sorry. If that's what you're all fixated on, the brand new reinvented wheel Serif is selling you, and believe that's the end-all, be-all of DTP, I have a nice, red suspension bridge just like the Golden Gate to sell you as well.
  24. That's all fine and dandy, but that should not be their #1 priority, sorry. The extra few seconds it takes to open that one file externally are negligible in comparison with the extra seconds, multiplied by whatever number of objects you have (at which point they would become minutes, if not hours), it would take to reposition them all in case you made some change just because there wasn't an inline/anchored object functionality in Publisher yet. The same goes for having to redo an entire project because you can't fill master page text frames with content, resize or reposition them after the fact and have the corresponding pages and content reflect those changes. That's how professional DTP apps work, and the whole point of using a DTP app instead of WordPad or TextEdit.app (i'm not even comparing DTP apps with Word or Pages, because those two can do that, too, and produce very decent results if you take your time to learn how to get them to do it). Nobody with more complex workflows and projects will even give Publisher a serious go if those features aren't there, and if they inadvertently jump right in and buy it outright because Photo and Designer are indeed awesome, some may even get pissed, ask for a refund and even drop a bad review. With all due respect for Serif devs, I know I would, and I'm hopeful I will instead buy it on day one and be happy that it works for at least some of my more complex projects, and not just for four-page inserts… Just my €0,02, which by now must be adding up to a €10 bill or two as I've been hammering this point here for quite a while now. Objectively speaking, the time savings brought by said novel feature, which they put front and centre on their website and InDesign kind of lacks, are vastly outweighed by the time savings (or lack thereof) brought by those super, super basic and essential features I've mentioned, hence my comment about which features Serif devs are probably working on right now. We all assumed that said marketing choice meant that the other basic features would be there, you know? As in, “look at how our app is actually superior to InDesign”… Except it isn't, because that feature doesn't make enough of a material difference in the grand scheme of things. It's kind of like selling you a boat with tire chains and expect you to use it as a snow vehicle; yes, it has a feature indeed useful for the use case it's meant for, but the core package is completely inadequate (even if you could, in theory, throw it off a snowy hill and have it slide halfway through ).
  25. I placed it within app package: ⁨Affinity Publisher Beta.app⁩ ▸ ⁨Contents⁩ ▸ ⁨Resources⁩ ▸ ⁨Dictionaries⁩ Possibly there are some better other locations as this possibly disappears when app is updated... I do not know how it behaves then.
×