Jump to content


  • Content count

  • Joined

  • Last visited

  1. 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
  2. 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
  3. Dear All, I have no way to display control characters of PDF files, so I cannot say whether Scribus writes a PDF file correctly or not (see above) But I have another example of conversion issues with the Word -> PDF -> Publisher process. 1) Create a page with Microsoft Word (bought Jan 2019, new PC on Windows 10) Set Word so that all control characters are shown 2) Save Word as PDF (with option rasterize if not embedded) or PDF/A Results in Affinity look the same. Both tested. 3) Open PDF in Publisher 247 with option "Group Lines in text frame" - the result is "strange" Publisher creates Text Frames that do not seem consistant with Word control characters. An additional logic seem to take place. - e.g. in some cases (after 10 spaces) a new frame is created, regardless of a character paragraph end In this case, I think that a new frame should not be created by Publisher after a certain amount of spaces, but after a paragraph end. I would also suggest to add a third option when opening PDF files : "Convert blocks of text" in a "structured" set of frames. Ideally, categories of blocks would be: Heading - Core text (in one or more columns) - Footer This would be an useful option for publishing simple documents as books or magazines containing "structured" pages of text. Alternatively, a third option would be "For each page, put all text in a single Text Frame, while respecting the original visual position as per PDF display by Acrobat Reader. Also, a simple tool to merge Text Frames would be welcome: - CTRL+ right click on frames to select, then merge. - Option 1: Keep the the X Y positions of the text as per PDF display by Acrobat Reader. - Option 2: Wrap text in the merged frame. 2 PDF files in attachment + 5 screen shots. Note: check the sequence of file names Regards, Philippe Publisher PDF import Text Frames Example A.pdf Publisher PDF import Text Frames Example B.pdf
  4. Dear all, I read different things about "soft hyphen" etc. I have no clue about what this is. I have used this version of Scribus and the other tools mentioned without any issue with my German printers for PDF-X3 documents. About 20 magazines and four books. I even took the risk of using Publisher 145 for printing a book. It worked fine ! (my old PC was windows 8.1 at the time - I got a new PC with windows 10 in January) As far as I am concerned, I just use the hyphen that shows on my keyboard. No Alt+ combination or whatever "clever". Note: Same issue with Affinity Photo and Affinity Designer I can only conclude that there is a "glitch" somewhere with Affinity tools. Note 2: I am using common fonts like Arial, Times New Roman, Helvetica and Verdana. Nothing fancy. Regards, Philippe
  5. Dear, If I open a PDF file with Affinity 249 on Windows 10, in some cases, - hyphen are disappearing with Affinity, while this issue does nots exists with Adobe Reader, Microsoft Word, Edge, Scribus, etc I think that during the open process, the character before the hyphen gets transformed into some combination with the previous character. See input PDF file, description of findings + screens and .AFPUB files in attachement Regards, Philippe Affinity issue Open PDF.afpub Affinity issue Open PDF.pdf mania201962p04.pdf
  6. Walt, Thank you. I was assuming that some kind of global setting was taking place through the Preferrence/ Autocorrect setting. So I suppose that this screen is "just" to be used to Add/Modify spelling check/replacement definitions. I am still a little bit confused: within Text/Text styles you can define language/hyphenation settings either through Character or Paragraph style settings but on the Studio you can only use the Character settings, NOT the Paragraph ones to manage language, etc Regards, Philippe
  7. Dear, I think spelling check does not work properly with languages other than English (UK). I am using Affinity 249, with Windows 10. I use primarily French and English dictonaries as available through standard Microsoft set-up. I am planning to add Dutch and German, as I produce pages in these four languages. Note: As far as the user interface is concerned, I plan to use only the native English version of Affinity, regardless of the language used in my pages/printouts. Regarding spelling check, if you select a language in the Preference/Auto correct screen, results vary depending on languages selected (see below). By that I mean that Affinity finds some lists of wrong spellings (left column) and correct spelling (rightcolums) . With French, at the top of this list I see: échaper (left column - wrong spelling) / échapper (right columns - OK) and so on With German, I see first änlich / ähnlich With Portuguese, I see nothing In French, If I spell a word wrong (a word as existing on the Affinity list), whatever you do, the checker always underlines the text in red (all wrong). If you go back to Preference/Auto correct, it shows English. Conclusions: 1) it seems that there is a list of 7 languages (in this "strange - non alphabetical" order: German, English (UK), English (US), Spanish (Spain), French (France), Italian, Portuguese (Brazil) 2) Four word llists seem good enough for tests (English (2) , French, German). Some are incredibly short and useless (Spanish, Italian). Portuguesse is empty and useless) 3) it seems that there is no way to use the spelling check for any language but English(UK). If you select another language, Affinity goes back to English. 4) I am not keen to load myself dictionaries, as this is prone to mistakes. Standard sets should be provided by Affinity to start with the tests of spelling check abilities (the 7 languages mentioned above ?) 4) It would be wise to add some warnings/explanation as part of the first screen describing the beta (not for production, etc) Regards, Philippe
  8. 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.
  9. 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
  10. Dear all, with 192 and previous beta , some unexpected colour inversion of whole pages happens with Export as PDF. Preview OK. See "PDF photo-color issue" By toonybrain, November 12 Various files were provided Regards, Philippe
  11. The problem is still there with 192. Additional note: the preview of the page shows correct colours. Colour inversion happens only with page 4 either in the PDF of the whole document or in the single page 4 save.
  12. The problem is still there with 174. Please note that Publisher displays the correct colour when you open the .afpub file, but all PDF exports fail to show page 4 correctly
  13. Chris_K, I have had also inverted colours within a document (1 page out of 20 is wrong and cannot be INVERTED). Issue with 139, 145 and 162 See my comments in "Negative images when exporting to PDF" by richardlockton. In attachment: single page original PDF file, Afpub file and various wrong PDF outputs created by Publisher Process: create a white page and use the PLACE fonction to position a single page PDF. Do this 20 times. Work around was to restart the whole document from scratch and PLACE differently the PDF. By the way, you will see that the .afpub files created by Publisher are huge compared to the sum of the original PDF. PDF files created by Pubisher are OK in terms of size. Note: all original single PDF pages were scanned with Vuescan and cleaned using Affinity Photo. Then resized with bleeds of 2 mm with Foxit Phantom Pro (which is part of my present workflow for managing PDF X/3 prints) Foxit was used as at the time there were issues with Publisher bleeds management Regards, Philippe BDinterieurP08aP27WRONGrecreated_with162_with_Invert.pdf BDinterieurP08aP27WRONGrecreated_with162_without_Invert.pdf BDinterieurP08aP27WRONG.afpub BDinterieurP08aP27WRONG.pdf BDPLMp004.pdf
  14. Dear, I has a similar issue with beta 145. It is still there with 162. I have made a document of 20 pages. Each page is dead simple: a white A4 page as background plus one PDF import that is positioned. All 20 pages go through the same process. No other filter or whatever applied. 19 pages OK, one incorrect: page 4 appears normally on the screen, but the exported PDF is printed with negative colours for this page only. (this is not OK) If I use the Publisher Invert filter fo page 4, the document is shown as inverted on my screen AND on the PDF (this is OK) If I cancel the Invert filter, page 4 appears normally on the screen, but is printed with negative colours. (this is not OK) Regards, Philippe
  15. Dear all, 162 Install without a glitch, with Windows 8.1: Uninstall, clean-up, install with Administrators rights. With beta 162, it seems that an additional bug is resolved. Publisher was not able to create some French and Spanish accents through Alt Gr + one key of the keyboard. It works now for "tilde", "accent grave" et "accent aigu", as per what is shown on my French keyboard. Working now (samples): ñ Ñ í é ó ò I would still like to test Publisher "native" spelling of other languages that English. Loading your own dictionaries is prone to errors and not useful for debugging. Cursor behaviour tests for languages like Arabic, Hebrew would be also welcome Regards, Philippe