Pyanepsion

I would like to export the lists contained in Font manager and in Resource Manager. How to do ?

Hello, Is it possible to export the content of the font manager? Of the resource manager? Thank you for your explanations.

😂 So if it's missing the steering wheel in a car, isn't that a bug in itself? I would not quite say that. OK. How to get around this big shortcoming?

Hello, The Bahnschrift variable font that ships with Windows 10 displays 15 different styles, each with a name. Affinity Publisher finds 15 styles, but it can do nothing with them, not even display them.

Hey! The purpose of this bug report is obviously not to compare this or that language! It is a question of highlighting that the dictionary provided by Serif is of another age, not to say useless, and of recalling that there exist very competent specialized companies capable of carrying out a really useful extension of correction of text . What a horror to have to spend 4 h 30 instead of a few minutes on barely 6 pages, just to enter proper names so as to purge the spelling checker and detect the real errors, not those that this spelling checker invented by incompetence. It is sufficient that Serif authorizes these companies and that it provides them with information on the necessary adapters.

You are right! Grammar is obviously also important even in languages like English, and an English adaptor would obviously be welcome too. The structure of French and English are, however, very different. A simple word existence checker is often enough in English, but it is almost completely useless in French as shown in the example above with Little Red Riding Hood.

In French, unlike other languages such as English (for example), spelling and grammar are intimately linked. You can't have one without the other. Moreover, in addition to offering a tool where you can spend several hours memorizing words where you should only spend a few minutes, Publisher offers a vocabulary list that is more than a generation out of date! It still had to dare. Creating spelling software is a profession. Let the professionals do it.

Hello, I had to check 6 pages containing proper names. I had to memorize each word one by one in the dictionary and it took me many hours where it should have taken only a few minutes! The French spell checker integrated into Publisher is almost unsuitable for professionnal use. It is based on the principles of English spelling, a language which hardly knows declensions, genres, conjugations, and homophones: les pools des poules du couvent couvent un oeuf neuf. This also requires an in-depth analysis of the limit and then of the structure of each sentence, which the French spellchecker integrated into Publisher has no idea. Therefore, it is based on a comparison with a list of words, as in the 1980s! Which is stupid (really!) for use in the French language. It cannot recognize a word in upper and lower case: Manger des pommes et manger des poires. It does not know French typographic spaces. This tool is also based on the spelling of old French, which has not been used for more than a generation. Creating spelling software is a profession. I do not understand why we find here the lists of Olivier R. for Mozilla in 2012! Impossible for it to correct this funny example where there are only spelling mistakes (no grammar error) about Little Red Riding Hood: Aile pot cédé thym lit vrai dû peu t’y chat peu rond roux jeu. who should be: Elle possédait un livret du petit chaperon rouge. The French company Diagonal from Nice, would no doubt be very happy to be able to implement a French adapter, as it has done for other applications such as Microsoft Office, Quark XPress, InDesign (and many other softwares). It has experience. It has existed since 1995. Many large publishers of books, newspapers, and magazines, as well as all French state departments, too, use their spelling checkers. Why would Serif not grant them the authorization and the informations necessary to create such an adapter? This would be of great service to the French and English speaking user community. https://www.prolexis.com/societe/la-societe-diagonal#contact

Hi LibreTraining. My first professional version of Windows is 10. So I don't have the right to use an earlier version of font. AngsanaUP is delivered in a single OpenType collection file called angsana.ttc containing 8 fonts version 5.05: Angsana New, Angsana New Italic, Angsana New Bold, Angsana New Bold Italic, AngsanaUPC, AngsanaUPC Italic, AngsanaUPC Bold, AngsanaUPC Bold Italic. If you use another version of font with only one font per file, it is illegal. https://docs.microsoft.com/en-us/typography/fonts/font-faq

Hi LibreTraining, Absolutely, but AngsanaUP is delivered in a single OpenType collection file called angsana.ttc containing 8 fonts version 5.05: Angsana New Angsana New Italic Angsana New Bold Angsana New Bold Italic AngsanaUPC AngsanaUPC Italic AngsanaUPC Bold AngsanaUPC Bold Italic It has, alas, nothing to do with the bug of Publisher. Here, your file is a single file containing only the AngsanaUPC-Regular.ttf font, supplied in version 5.010 (strange! and let's not forget that a font is a software, a script, and therefore likely to carry a virus), and it is especially illegal to extract and print this new file from a collection if you follow the instructions of the owner, Microsoft. To be continued in: Publisher Bugs found on Windows.

Yes. Strange. Have you a Microsoft or an Apple computer? I saw the bug on two different Windows 10 computers. Both computers have Adobe Acrobat Pro XI. I installed the brand new version of Thai fonts provided by Microsoft. AngsanaUPC is an OpenType collection file with 8 fonts. I installed Affinity Publisher on the test computer in its new public version, but the bug also exists in the beta version. Note that Publisher first appeared in French, and putting it in English (obviously) does not change this blocking bug.

Affinity publisher is unable to extract OpenType collection files (formerly called TrueType collection) in PDF export. The styles (italic, blod, bold italic, etc.) are then not applied. Example: Microsoft AngsanaUPC font. This is a free Thai font from Microsoft.

New test: Note that the PDF (flatten) mode produces a page with a correct appearance on the styles. There is of course no font management in preflighting. Note that the Adobe preflight of the other PDF files (with the fonts) only knows the regular font (image here). Note that the AngsanaUPC font is actually an OpenType collection file (formerly called TrueType collection), i.e. 'It is actually several OpenType fonts combined into a single file. Note that Word correctly exports all 4 styles of the font. Also note that QuarkXPress exports all 4 styles of the font in any choice of PDF. So I just did the same export test on a blank computer. I installed the free Microsoft Thai fonts and then installed Publisher 1.3.8.641. The file size varies slightly to 413.13. The problem of not printing styles remains. Therefore, I think this is a Affinity publisher blocking bug on PDF export.

I tried Publisher's default settings. I also tried the same thing on the Beta version of Publisher. Note that Word correctly exports and saves the font in its different syles. Maybe I should reset Publisher to factory settings? How to proceed ?

Hello, I would like to create a PDF file intended for the printing press and using the AngsanaUPC font supplied free by Microsoft. Everything look fine on screen in Affinity Publisher and when printed on my laser printer. It is a disaster when I export the document to PDF. Only the Regular style is included. The Italic, Bold and Bold Italic styles are exported in Regular. How do I get the correct export file? Thank you for your explanations. AngsanaUPC.afpub

Thank you.

Hello, I would like to verify visually on a PDF file what would give the impression in black and white of a document using color. How to proceed without having to convert all the colored parts of the Publisher document one by one? Thank you for your explanations.

Taking into account your comments, I therefore created 12 tables to fit on the 12 pages necessary since the update of the book is planned in a year. I hope by then that Publisher will have achieved this functionality better than do for example QuarkXpress, Indesign, or Word.

Thank you, Gary. 😀 That's what I was afraid of. Hopefully, however, this will be possible more quickly than for the footnote series. After all, this feature is easier to do, and is available on less advanced DTP software, or even on simple text writers. I also considered creating a style to rhyme the paintings, but it seems impossible to decorate it with tab fields?

Hello, I have to do a table that's a lot of pages long. This table is subject to change according to product updates. So I've broken it down into as many tables as there are pages. How can I concatenate the tables so that if I later delete or add rows, I don't have to redo all the tables? Thank you for your explanations.

With a note (footnote, side note, or elsewhere on the page), the difficulty lies mainly in the relative position of the footnote call. If, for example, the note call is on the last line of the main text of the page, and the footnote is at the bottom of the page, then it will bring the footnote call to the top of the next page.

The resource setting is configured to not integrate the images, but to keep them as linked external links. It finally seems that the problem is due to an incomplete preload since if you wait a little bit, all the Affinity Designer images end up appearing in full. The problem comes from the following situation: if the PDF file is exported immediately after the DTP Publisher file is opened, the DTP Affinity Publisher file has an incomplete picture on the final result. affinity-designer-import.mp4

Hello. When an Affinity Designer "image" is imported (a file image.afdesign) , this image only appears on a quarter of its surface when the Publisher file is reopened. Publisher 1. 8. 2. 620 Image on a master page.

Hi, J@HWC. Yeah? When my new client realized that putting footnotes rather than end of section notes would cost him an extra €220, he quickly changed his mind. Having said that, I'm looking forward to the feature coming.

Thank, MickRose.😀