Jump to content


  • Content Count

  • Joined

  • Last visited

About pdussart

  • Rank

Recent Profile Visitors

348 profile views
  1. Guys, I have to stick to PagePlus. Spelling is very hard to manage with Affinity Publisher. I want a simple thing: 1) the user interface is English or any other interface language supported by Affinity, regardless of the computer OS set-up. 2) Uncouple the spelling languages from the Affinity interface language; e.g.interface in English, spelling in French 3) Please provide: - a single command to define the spelling language for the whole document. This should be used as initial set-up or to overrule language settings of imported PDFs Note: PDF imports from Pageplus which are correct in French are not understood as such by Affinity and are shown as incorrect because English is used as default spelling language by Affinity. - a command to define the spelling language by page (right click on the Master page and the Page views - adjust the spelling language on the spread dialog) - a command to define the language by text block (right click) - it should be easy to manage multi-lingual documents and toggle spelling by page/blocks of text etc, in a WYSiWYG way 4) BUG ? if you change the spelling language in the Preferences/Auto-correct, whatever you do, it always go back to English and the change of spelling language does not occur. Note: the spelling Help explanations are not clear and do not seem to provide practical help for the spelling questions. Regards, Philippe
  2. Dear all, My printing company is changing its recommended ICC profiles. I have to do some reprints. It was ISO coated V2 (ECI), it becomes PSO Coated v3. Can I "just" go back to the .afpub file and export it as with the new profile ? This would be a matter of seconds. Do I need to go back to each picture and do something ? Then replace existing pictures with new profiles ? This would be matter of hours or days for large documents ? By the way, I might have the same issue with old Pageplus X9 files that I need to reprint. Regards, Philippe
  3. Joachim, Thank you. My layer name and the colour name are OK, with the _ underscore. But the channel name not (see the screen pictures). I have checked and rechecked my design and still get the problem with the automatic tool of the printing company. I will check with their staff,probably at cost. Regards, Philippe
  4. Sir, In order to produce stickers, in am in touch with a German Publishing company. In order to get stickers cut around my design, a layer with the compulsory name "Cut_KC" must be created. I will be the path for the machines to cut around the design. The VolltonFarbe / Solid colour must be also called "Cut_KC" It seems that Affinity Photo (latest production version on Windows) gets rid of the underscore. So my PDF files are rejected by the printing company. It costs 80 EUR to ask this supplier to fix the problem,..... It seems that the Colour Channels are not properly named (no underscore) This might be the naming issue in the file generated by Affinity ? Please advise See attachments Regards, Philippe Colour_name_bug.afphoto Colour_name_bug_message.afphoto
  5. Gabe, I am happy with UTF-8. Regarding metadata entry, I would prefer to enter key metadata info as a last step in Affinity. This would happen in the field. I would use a template with about 8 fields like Caption, Description, City, Country, Keywords, Author, Copyright notice, Usage terms. After such template set-up I just see the fields that I need, no less no more. It is also a way of not forgetting one of these fields. Juggling with 4 windows could be error prone and time consuming. Also an update in one go of the RAW and JPG files of the same shot would be useful. Back in the office, another team or myself are dealing with fine tuning of this matadata (like resolving keywords mispellings, keywords dictionnaries, translations and other metadata issues). Like Uwe, I am using Daminion to manage this second step. We have got 30,000+ RAW/JPG couples, I.e. 60,000 files managed that way so far. Regards, Philippe
  6. Dear, I am a little bit puzzled by the new metadata management. It is anyway good news, I am waiting for this since day 1. IPTC data entry fields seem to be split in 4 windows: - File - IPTC (Image) - IPTC (contact) - Rights I would favour a single window, juggling from one to the other is not convenient. Most if not all other photo managers do so. (Adobe, Xnview, Irfanview, etc) Adding a template for the fields that matter to you is also an usual feature Not clear whether encoding is UTF-8 or similar, whether you can change the encoding, in order to read and store properly accented and special characters (French, German, Spanish, Arabic, etc) Is XML coming with the next beta release ? Regards, Philippe
  7. Dear all, The help function of Affinity Photo regarding EPS and other export is confusing. I need to get a 100% vector based EPS file, starting from a JPG file. I assume the following EPS export process : File Export then the "More" section and use for Rasterize "Nothing" in order to get an 100% Vector EPS file ? Is "Nothing" the same as "100% Vector based" ? I have no way to check this. Please help Regards, Philippe
  8. Dear all, IPTC is the driver, as it defines the metadata to be stored. (the WHAT) IIM was HOW ITPC defined the way of storing this metadata. XMP is a more recent way HOW to store metadata. XMP has progressively replaced IIM. XMP is flexible and enables also to store metadata from various sources like EXIF, Core ITPC but also user created fields. Some tools create two files for a single shot, say 123XX.JPG and 123XX.XMP On the other hand, JPG standards allow to store metadata directly within the JPG file. In this case 123XX.JPG only As far as Affinity Photo is concerned, if Serif chooses for a limited ITPC support (say a dozen of fields), an update of the JPG file would suffice without separate XMP file. If you go the DAM route, OK. I would not overload Affinity Photo with this. (step three for me) Here is a list of tools that are recognized by the ITPC organization, as per www.itpc.org Affinity Photo should get there in order to join the "professional" club, assuming this is the Serif's aim. ACDSee Pro 10 Adobe Photoshop CC 2017 Adobe Photoshop Lightroom CC 2015.8 Daminion 4.6 DigiKam 5.0 ExifTool 10.46 FastPictureViewer Professional 1.9 FotoStation 8 Image Relay 5.0 Imatch 5.5 Photo Mechanic 5 Photo Supreme 3.3 PhotoGem 1.0 Portfolio 2.5.3 STOCKBOX PHOTO 5.40 WPMeta 1.3 XnViewMP 0.84 Regards, Philippe
  9. Dear all, IPTC is an old well established standard, implemented in most image management tools (from freeware to expensive ones) IPTC was just implemented by Adobe in their products in the 90's, but the development of these standard started in the 70's. The International Press Telecommunications Council (IPTC) was established by a group of news organisations including the Alliance Européenne des Agences de Presse, ANPA (now NAA), FIEJ (now WAN) and the North American News Agencies (a joint committee of Associated Press, Canadian Press and United Press International) to safeguard the telecommunications interests of the World’s Press. Since the late 1970’s IPTC’s activities have primarily focussed on developing and publishing Industry Standards for the exchange of news data of all common media types. EXIF is limited in its ability to describe pictures. ITPC standards coupled with XMP (a way to describe them in a sidecar file) are very useful. I am managing a 30,000+ pictures data base and using a subset of ITPC standards: Caption (text description), Picture taken date, Picture Update date, Keywords, Country, City, GPS location, Picture author, Copyright (rights owner), Copyright notice (text), Event Affinity Photo and Designer should be able to enter such ITPC data. Affinity Publisher should be able to register a wide set of PDF Properties. I mean just data entry for these 3 Affinity products It looks like Affinity Photo is using Lensfun for its lens correction. May be a business deal regarding metadat with Exiftool, XnView or Irfanview would help for providing a robust solution (Serif do not want to re-invent the wheel, ...) A DAM (digital asset management) is a different story. DAM is used e.g. to manage large sets of pictures, create folders of your pictures, select pictures, add further descriptions, etc. This is a complement, if you have very large quantities of pictures, if you a long term archiving need. Newspapers and museums use DAMs to extract a single picture out of millions in two clicks. This could become a fouth Affinity Persona. Personnaly, I see three separate tools in professional image management, rather than an integrated tool. Lightroom tries but is far from perfect. 1. A tool like Photomechanic to copy images from a camera, populate automatically some metadata, rename file names, etc 2. A tool like Affinity Photo for picture improvement (including appropriate picture descriptions through EXIF, ITPC, XML) 3. A DAM like Daminion to manage large quantities of pictures, with search facilities based on metadata Regards, Philippe
  10. In order to illustrate this request, here is an example out of Foxit. This is part of the ORGANIZE section, under PAGES management Note 1: there are other function like MOVE and SWAP, but Publisher has already other ways to deal with this Note 2: I would prefer to stop using Foxit. Using multiple tools is prone to conversion and other manipulation issues.
  11. Dear all, My problem is as follows: I get from various external contributors files in various formats. Some of them are ready, some of them are to be improved or illustrated, etc. I do not get them in the right sequence, ther might be days between inputs. First arrived, first processed. Features request: INSERT and REPLACE functions Functionalities: - if you right click on a page, in addition to "ADD PAGE", show also INSERT from/to input pages BEFORE/AFTER page xxx of my new document - if you right click on a page, in addition to "ADD PAGE", show also REPLACE from/to input pages BEFORE/AFTER page xxx of my new document - if you create a section, allow INSERT from/to input pages - if you go back to an existing section, allow INSERT and REPLACE from/to input pages Regards, Philippe
  12. Dear, the problems of French dictionary mentioned above seem to have disappeared with Regards, Philippe
  13. I did the same exercise with a French dictionary from Github. Also problems. Process: - download dictionary from Github - copy file into Affinity (as per previous mails) - reboot - Set Affinity without any form of spelling check - Open Affinity. Load a file with a 100% correctly spelled text - Affinity shows the text not underlined, as spelling check is off (this seems OK) - apply spelling check - no underline (everything seems OK, i.e. the French words are recognised as correct) - change one word so that it is mispelled (this word only is now underlined, which is OK) - if you spell correctly this word, all words are now shown as incorrect. The English spelling check seem to take-over the French one. Installing a dictionnary file is not enough. Note: In the Document Preferences Auto correct you can select a short list of languages, you can select French and save this option, but if you go back to this screen, it shows English again, regardless of your previous setup in French. This is may be the problem. All this despite the Additional dictionary folder of Tools still points to the French dictionary, ...
  14. Dear all, Additional note: the Colour Picker of the free tool GIMP reads the same values than Affinity Phato and Designer in all cases tested. This tool must be correct regardless of the screen, the (work) file should contain the right values. So, it looks like the Affinity Colour Picker reads correct CMYK values. Another glitch, probably linked: - I tried the Flood Fill value 0,0,0,14 with the weird file mentioned above. Afterwards the colour picker showed the correct value of 0,0,0,10. - with the Flood Fill value of 0,0,013 I read 0,0,0,9 with the Colour Picker May be Affinity is doing some conversion process internally ??? Regards; Philippe
  15. Dear all, Similar issue with Affinity Designer. I can provide two simple files. One accepts CMYK with a value of 0,0,0,10. This one looks OK The other let you enter 0,0,0,10, but sticks with 0,0,0,7 as fr as the Picker is concerned. The one with 0,0,0,7 is weird: - if you end up with 0,0,0,10 displayed on the CMYK sliders, - if you save immedialely this file, quit Affinity, it reopens with CMYK 0,0,0,7 Something strange definitively happens Regards, Philippe
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.