Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

PaoloT

Members
  • Posts

    764
  • Joined

  • Last visited

Everything posted by PaoloT

  1. I wonder if this a geographical thing. All the metalwork and printer companies and shops I've asked, in my area, don't make any problem if I send them a DXF, an SVG, or an AI file. One of them explained that the best format is the one that comes directly out from the drawing program, so for them it is equally DXF or AI. I feel a bit like when everybody was screaming that they needed a DOC file, and then an RTF file did the job as well; or when everybody was swearing that you couldn't send publishers anything else than a Finale file. Or those who giggled when you explained them that you were publishing books, but not using QuarkXPress. It's never that file format. It's always the one that gets the job done. Serif should make a video tutorial about preparing files for an engraver. All considered, more than printing books, this is one of the most common jobs for a designer. Paolo
  2. Hi, After the new version of Pandoc (v3.0) has been released, I have to reiterate a request for ICML import to Publisher. Pandoc v3 includes an improved ICML converter. This converter would make going from (nearly) any text file format to Publisher with no effort. If the source file contains text layout instructions (as you can do with Pandoc markdown, LaTeX, or Scrivener) Publisher could rebuild the layout faithfully. ICML is a subset of the IDML file format that Publisher can already import. It is just one of the "Story" XML files inside the IDML package. Unfortunately, there is no way that I could find to convert an ICML file into an IDML one, so at the moment Publisher can't take advantage of this Pandoc converter. Pandoc and LaTeX are in strong use in the technical industry and in the academia. Such a converter would allow Publisher to be the end interface to generate PDF files from internal or end-user documentation, or research materials. Paolo
  3. …something you can do with the older Macs, but not with the new ones! 😁 Paolo
  4. Not that I'm objecting to the export functionality, but the DXF format is usually asked because it comes directly from the CAD, and there are no dangerous conversions in the middle. If the original drawing is made in Designer, it is likely that an SVG exported from it is more accurate than a DXF converted with another program. Paolo
  5. I would say that the world would have more and more problems, if we really consider a computer from less than four years ago an obsolete one… https://www.nationalgeographic.com/science/article/e-waste-monitor-report-glut I'm using a Mac from 2013, and it works perfectly fine. It can even install the OS from the end of 2021, and with a little patch it can run with the current one. I could install 64 GB in my obsolete Mac, and could have installed twice of that, while the most recent Macs struggle, or can't have that amount of RAM at all (the one just introduced stops at 24 GB). And I have tons of ports, including 2 x Gigabit Ethernet. And yes, I barely use 1/3 of its CPU power when rendering a full orchestral simulation. When this 1/3 will really get old, I'll use the remaining 2/3… Paolo
  6. I'm not sure it is totally this way. I own the perpetual version of 2021, that freezes the features of that year. The 365 version has continued to evolve, but I can open its files with my version. Also, I would think that the DOCX and XLSX file formats can be opened with any version of Word and Excel from a few years up to today. Only, the missing features are ignored by the older versions. Paolo
  7. The really secluded program is, in fact, Publisher. Both Photo and Designer have export options that may help sharing with V1 and with other programs. Not so with Publisher. Paolo
  8. Maybe. But do you have any idea about why they should do it? I've assisted, even in companies where I have worked in the past, to discussions about preventing users to save to the file format of a competitor, to forbid them to go/return there. I've always found this completely fool, in particular when the other company is a much bigger one, and an established one that wouldn't need compatibility with the data of the smaller company to survive. At the same time, the smaller company suffered lack of interoperability, therefore of easy reuse of their customer's work in a more general context. This made the tools of the smaller company useless, despite their appeal, good quality and lower cost. Paolo
  9. It could even be IDML. If Publisher 2 could export this format, Publisher 1 could open the exported files. With the obvious limitations imposed by the different features available in the source program. A single interchange format would solve so many problems. Paolo
  10. I would add that not only native speakers would find support for non-Roman languages useful. Even professionals and companies writing in English, or other Roman-based languages, need their creations or products to be delivered worldwide. The omission of large areas of the world makes Publisher unsuitable for this type of job. I understand how difficult it is to implement this support, and the many years Adobe needed to give imperfect support testifies it. However, I think the importance of this issue shouldn't be underestimated. Paolo
  11. Unless you have already tried, I would rebuild each note one by one. In the word processor, I would insert a note, and then paste the source. It's a very long work, for which I would probably advise against using Publisher. I'm not using it myself for this type of work. Sadly, the lack of export functions can be a very hard hit for some of us. Paolo
  12. Its advantage is, however, that you can type directly in Publisher, with no need of exchanging data with Designer. Until there isn't direct support from Publisher, I would think that 30 USD (or less, if you purchase the multi-license) is an acceptable price for an easy solution. Paolo
  13. And you could still print the open source colors yourself! All you would need is something like Pantone reference cards to make them… Paolo
  14. FontBook can do it. Just create a dedicate smart folder. Paolo
  15. It would suffice if Publisher did as InDesign: export a story in a linear way, with all the styles applied and the images in the text, converted to a format that RTF can support. But I would greatly appreciate if Publisher could export linked images, at least as an option, as links that it can then rebuild when importing the same file. If RTF, now a rather obsolete file format, can't do it, DOCX could maybe do it, or be able to be adapted to do it. This way, one would be able to export the story as a DOCX file, have it edited or translated, and be able to have the linked images reappear in the text when one imports it into Publisher. Paolo
  16. If you just need text, maybe copying from Publisher and pasting into Word may work. I've done some tests. Copying from Publisher V1 and pasting into Mac Word 16, all the paragraph styles are preserved. Character styles are not applied, even if the character appearance is there (you can ask Word to select similarly-formatted text, and apply the character styles from the list). Images are not pasted. Accented character are not pasted. Tables are not pasted. With Apple Pages 10, nor paragraph or character styles are pasted. You have to select similar text and create the styles again. No image or table is pasted. Accented character are pasted. With Nisus Writer Pro 3.3, all the paragraph styles are preserved. Character styles are not applied or imported, even if the character appearance is there. No image or table is pasted. Accented character are pasted. Paolo
  17. As Groucho says, "I don’t want to belong to any club that will accept me as a member". Paolo
  18. I've seen the old workbooks on sale for something less than 200 euros. Now I know how Serif can afford to keep the software price so low! 😁 Paolo
  19. @v_kyr, @loukash, @R C-R, thank you for the hints! Yes, I found the plugins inside the folder where Photoshop is installed. Moved them to a common repository, and AfPhoto sees them perfectly fine! Paolo
  20. I wonder if something has changed, since when you installed them for Photoshop. I just noticed that what I downloaded ("nikcollection-full-1.2.11.dmg") is not a set of plugins, but of stand-alone applications. So, while AfPhoto can see the other Photoshop plugins I indicated, these can't, because they aren't plugins! I wonder if the plugins are still available, or they can now be downloaded only as separate apps. Paolo
  21. Do you know how to install it? I'm on a Mac, and when doing it I can't select the Affinity programs as the targets. Should I install them for Photoshop, and then copy them somewhere inside Affinity Photo? EDIT: Sorry, I chose Photoshop, and I see it is installing them as a separate folder on their own. I'll then be able to add them to Photo by choosing them manually from the program. EDIT 2: Hum. But I fear they are not working. The containing folder is in my Plugin Search list, but the filters don't appear in the Filters > Plugins menu. I'm still on Photo V1. Paolo
  22. @loukash and @Ghost Rider, thank you for your contributions. But may I ask you (and anyone else) to discuss of problems and solutions in one of the other existing threads? I would like this one to remain entirely devoted to the missing (and added) import/export features, so that they can be found as easily as possible. Paolo
  23. What about recurring headers? They wouldn't be created by Publisher. Paolo
  24. My preferred workaround would be creating the table in a wordprocessor, with the same identical page layout and styles of the Publisher document. It could then be exported as a PDF file, and inserted, piece by piece, in the Publisher document. Any change would be made in the wordprocessor, and then exported and automatically updated. This would work if the table starts on top of a page. If there is variable length text before the beginning of the table, positioning it would be more difficult. With documents with many tables, one could even start to consider switching to the wordprocessor entirely. Paolo
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.