MrNate Posted November 30, 2021 Posted November 30, 2021 I'm having an issue exporting a document I'm working on with Publisher. It pops up an error on export and if I check the Pre-flight I see this: If I click on Fix, it just brings up the font list and I really can't do anything to fix the error. This document is actually 80 pages, but I have deleted almost all of them to minimize the places where this missing font might be. I have a feeling it's on more than just these two pages, but I figure if I can fix it with these two, then I can fix it for the rest. From what I can read, since MS Shell Dlg is a logical font, there isn't actually something I can download and add to my font list. I also checked my registry where MS Shell Dlg is mapped to MS Sand Serif and MS Shell Dlg 2 is mapped to Tacoma, so that seems to be setup correctly. I have attached the afpub to this post. Thank you in advance! 0020-0081-MinWithError.afpub Quote
Old Bruce Posted November 30, 2021 Posted November 30, 2021 I guess you fixed it because I don't have that font (MS Shell Dlg) nor any of the replacements you mention. All I see are the spelling mistakes and then all the Non Proportional scaling plus of course missing images. Could be in one of the Paragraph Styles, perhaps No Style is set to use MS Shell Dlg on your machine, set the default to use Arial for Paragraphs and Characters. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that.
MrNate Posted November 30, 2021 Author Posted November 30, 2021 Is this what you are talking about with regards to setting a No Style? It looks like I'm already not using any style: Quote
MrNate Posted November 30, 2021 Author Posted November 30, 2021 I just looked through all of the text styles and they are all set to use Arial. Any help is very much appreciated with this since I'm out of things to try. Quote
Old Bruce Posted November 30, 2021 Posted November 30, 2021 It appears to be on one of the Master Pages so check for empty lines in them. A paragraph return or even just a space will retain the font information. See if any of the text frames are assigned to use the font. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that.
kenmcd Posted November 30, 2021 Posted November 30, 2021 On opening the file I get no missing fonts warning; so nothing about MS Shell Dlg. Could it be coming from one of the linked SVG files? (which we do not have) Old Bruce 1 Quote
MrNate Posted November 30, 2021 Author Posted November 30, 2021 I just realized that even with the MS Shell Dlg missing error I am still able to export that afpub file to a pdf without issue, so it seems as tho that particular error isn't the cause of my being unable to export the full file to a pdf. Is there someone at Affinity that I can send my original afpub file too? Since it has proprietary information, I can't upload it to this forum obviously. It errors out at around 30% while trying to export to PDF Quote
walt.farrell Posted November 30, 2021 Posted November 30, 2021 26 minutes ago, MrNate said: It errors out at around 30% while trying to export to PDF You could try: And if you don't understand what the log file is telling you, you could upload it here. 27 minutes ago, MrNate said: Is there someone at Affinity that I can send my original afpub file too? One of the moderators can provide a private upload link when they get to this topic. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Old Bruce Posted November 30, 2021 Posted November 30, 2021 21 minutes ago, Lagarto said: You could also use "binary" exporting and always export in "halves" until you spot the page that causes the error, and then go on and alway print in halves objects on that page (halving the contents of the Layers panel). The font is missing on a Master Page. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that.
MrNate Posted November 30, 2021 Author Posted November 30, 2021 Thank you guys for all of the help. Here is the output of the last few lines of the pdflib.log file, I bolded what seems to be the error line but I'm not sure what it means: PDF_save(p_0x000001ACE1B05080) PDF_concat(p_0x000001ACE1B05080, 1.029860, 0.000000, 0.000000, 0.969221, 309.102680, 506.126481) PDF_load_font(p_0x000001ACE1B05080, "ArialNarrow", /*c*/0, "glyphid", "readkerning=false readfeatures=false readselectors=false readshaping=false errorpolicy=return embedding=true subsetlimit=90% subsetminsize=50") [-1] PDF_load_font(p_0x000001ACE1B05080, "Arial Narrow", /*c*/0, "glyphid", "readkerning=false readfeatures=false readselectors=false readshaping=false errorpolicy=return embedding=true subsetlimit=90% subsetminsize=50") [4] PDF_setfont(p_0x000001ACE1B05080, 4, 9.200173)PDF_fit_textline(p_0x000001ACE1B05080, "\027\032\025\023\020\023\023\023\025", /*c*/9, 188.555580, -55.285875, "xadvancelist={4.195782 4.195782 4.195782 4.195782 2.511180 4.195782 4.195782 4.195782 82309706.032523 }") [Last exception 1906 in PDF_fit_textline]["Floating point number 8946538032.089561 too large for PDF"] /* PDF_get_opaque(p_0x000001ACE1B05080) */ /* [0x0000005BBEC5F1A0] */ PDF_delete(p_0x000001ACE1B05080) /* PDF_get_opaque(p_0x000001ACE1B05080) */ /* [0x0000005BBEC5F1A0] */ /* writeproc(data[0x000001ACE231B020], 64058)[64058] */ [2021-11-30 15:42:07] Regarding the font, If I just open up the master pages as it's own afpub file and try to export it it works fine and the pre-flight doesn't show that MS Shell Dlg font error. Quote
Dan C Posted December 1, 2021 Posted December 1, 2021 Hi @MrNate, Welcome to the Affinity Forums Sorry to hear you're having trouble! When downloading and exporting the .afpub file provided, this completes as expected for me currently, so I'm not 100% certain what's causing the export to fail at this time. Therefore I'd like to request all the files used in your document, can you please upload all of your linked resources to the below link for me, as well as the full PDFlib.log? https://www.dropbox.com/request/GQ21ee7M87fkTy5su0Z2 Once uploaded, please reply here to let me know. Many thanks in advance! Quote
MrNate Posted December 1, 2021 Author Posted December 1, 2021 Thank you for the response Dan. I checked with my colleagues and since this document contains proprietary information I can't just post it to a dropbox. Do you guys have some sort of system setup to deal with your customers that have documents with proprietary information in it? Quote
kenmcd Posted December 1, 2021 Posted December 1, 2021 14 minutes ago, MrNate said: Do you guys have some sort of system setup to deal with your customers that have documents with proprietary information in it? Yes, the private Dropbox link he posted above. Only Dan and Affinity have access to your documents. Quote
A-- Posted June 23, 2023 Posted June 23, 2023 The MS Shell Dlg issue is unfixed as of version 2.1.1 When the error is shown in preflight, there is a "Fix" Button, but no matter what you enter, the error does not go away. MS Shell Dlg is not installed as such on my system, and for that reason, I can also not search for any text formatted with it (because it does not show in the drop box). MS information points out that this is a "logical font name", which to me sounds like it's a magic name with special handling. I have no idea how it could even get into a new file. Quote
carl123 Posted June 23, 2023 Posted June 23, 2023 17 minutes ago, A-- said: The MS Shell Dlg issue is unfixed as of version 2.1.1 When the error is shown in preflight, there is a "Fix" Button, but no matter what you enter, the error does not go away. MS Shell Dlg is not installed as such on my system, and for that reason, I can also not search for any text formatted with it (because it does not show in the drop box). MS information points out that this is a "logical font name", which to me sounds like it's a magic name with special handling. I have no idea how it could even get into a new file. Do you have a sample document you can upload to the forum? Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
A-- Posted June 23, 2023 Posted June 23, 2023 What I have is too massive and can't be shared because of rights. I'll see whether I can remove it down to minimal case. Not possible immediately. Quote
Alfred Posted June 23, 2023 Posted June 23, 2023 4 hours ago, A-- said: MS Shell Dlg is not installed as such on my system As noted in the original post to this thread: On 11/30/2021 at 5:38 PM, MrNate said: since MS Shell Dlg is a logical font, there isn't actually something I can download and add to my font list It’s usually mapped to Microsoft Sans Serif (or MS Sans Serif). Quote Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen)
A-- Posted June 23, 2023 Posted June 23, 2023 Here is the promised test file. I created it by removing as many pages as I could without clearing the error, then as many layers on the page. As you can see the preflight panel gives no help on which page the issue occurs and, in particular the "Fix" button does nothing. If you eventually locate the character in the file you will be able to set the font explicitly, but that takes forever in a complex/large document. The worst part here is that the font is never actually attached to anything printable, so actually doing all the work of fixing it might simply have no effect... MS Shell Test Case.afpub Quote
A-- Posted June 24, 2023 Posted June 24, 2023 To add something. I found that my original file contained a second instance, not in a text frame, but in an artistic text area. I tried selecting the whole text, including invisible end-of paragraph and to assign a style. That did not(!) work, even when reapplying the style. I think that is unexpected and may be caused by MS Shell Dlg not being a "real" font, or maybe by it not being installed. Instead, the only way to fix it was to actually select the one invisible character and manually select a font. That's way to cumbersome to fix something that seems to have been a result of setting an invisible paragraph format during a cut&paste operation of a short piece of text that was ostensibly a single character. Something's off here. Quote
carl123 Posted June 24, 2023 Posted June 24, 2023 5 hours ago, A-- said: in particular the "Fix" button does nothing For me, the fix button takes me to the Font Manager dialog In there I can see the missing font and automatically locate the text frame it is in In a small text frame, it is relatively easy to locate the offending character(s) and replace the font Another way: The find and replace function allows you to search for missing fonts (e.g. MS Shell Dlg 2) and replace them with the font of your choice. This approach is useful if the missing font is in multiple text frames Both the above solutions work on the example document you provided Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
A-- Posted June 24, 2023 Posted June 24, 2023 This may in the end resolve as a UI design issue (i.e. unnecessarily confusing presentation of features). First, the preflight gives you a "Fix" button. That sets up the expectation that you can fix the issue from whatever dialog comes up. The font manager has 3 things you can do. 1) you can select a substitution. (That's seems to be the main function of the dialog). 2) you can locate (That's presented only when a row is selected) 3) you can close. Results Of these, the first one (substitution) does nothing. I can't tell whether it does something for other fonts, but you can select anything you want in the test file and it does nothing. It also does not tell you it did nothing. The locate works, thanks for the tip. There are some oddities in the way this function is presented: The locate button is deactivated unless you select the font in question - however, opening the Font manager by clicking on Fix does not open the dialog with the problematic font preselected. That should be fixed. (Having experienced that substitution doesn't do anything, I never clicked on the row for the font after the first time, so never saw the grayed out button.) It could arguable placed next to, or closer the close, not at the far left, if it is intended to be one of the main "results" of accessing the dialog). --- As for search and replace, I'm not able to select MS Shell Dlg in the dropdown because it's not an installed font on my system. I therefore think it's not usable for any other missing fonts. It works fine for other fonts (I confirmed). Quote
carl123 Posted June 24, 2023 Posted June 24, 2023 7 minutes ago, A-- said: Of these, the first one (substitution) does nothing. A lot of users believe that substituting a missing font permanently replaces it It doesn't! Substitution allows you to use a different font for display/print purposes. The missing font will always be reported as missing. You either need to add the missing font to your system or use find & replace to permanently replace it with another font 11 minutes ago, A-- said: As for search and replace, I'm not able to select MS Shell Dlg in the dropdown because it's not an installed font on my system. Find and replace allows you to search specifically for missing fonts, just use the dropdown (next to Font Family) that defaults to "All" and change it to "Missing", then the missing font will show up in the Font Family drop-down. (See screenshot below) Alfred 1 Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.