Jump to content
You must now use your email address to sign in [click for more info] ×

JanG

Members
  • Posts

    31
  • Joined

  • Last visited

Recent Profile Visitors

406 profile views
  1. Thanks for your patience. Meanwhile I have tested the file with an Rtf-version of my Word file – And it works! Not only no corrupted fonts anymore, bu also the footnote numbering is no issue anymore. This seems to be a way to work around these problems. Thank you all for helping me.
  2. Thank you all for your most valuable input again. I am sorry that I have to ask you for some more patience as I am simply too busy to reply for the moment. Please give me a few more days. Thank you. 🙂
  3. Thanks again for your input. To make the font issue more clear: I opened a template for the layout (no issues) and than imported text from a word file (red warning with Garamond fonts). Next I tried to switch the font in publisher and to change the fonts in word to some well known font (Times New Roman) by searching and replacing the Garamond settings. After import to Publisher I immediately get the red warning. So something in the file seems to be strange. Unfortunately, I am not able to do a search for "Garamond Pemr Pro" as this font does not show up in the list I have to choose from. Publisher shows the issue to be located in the first line of the heading. So I cut it out, wrote the headline by hand again in Publisher as well as in Word. Still I get red warnings. So I cut away the full first page and replaced it (red warning). Then I opened the word file in two other programs (Pages, Libre Office), checked for issues ad exported it again as Word files. Red warnings in both cases (WTF). So for the moment I have retired to ignoring the warnings – but I hate doing so. Something with this file seems to be completely corrupted ... Does anybody of you have any ideas concerning the footnote numbering? Thanks!
  4. Thanks for your help! Unfortunately, locating the missing character does not help at all, because there is none – neither visible nor invisble. Even if I delete the whole paragraph (with some characters before and some after the critical location) from the publisher file nothing changes. The same is true if I delete the passage in Word before importing. Somehow Word has managed to replace all fonts called 'Garamond Premier Pro' into files called "Garamond Pemr Pro'. And not even reinstallatin of the fonts changes anything. It is really frustrating. BTW, is there a way to make command characters show up in Publisher (like it is possible in Word)?
  5. I am using Publisher in Version 2.0.4 on a Mac with a plain though formated text document generated in Word (Version 16.71). At first everything looks normal in Publisher. Yet, when i look for the checklist, I get a disturbing result. My Problem is most simply illustrated by a screen shot: The file I am working on is using the Garamond Premier Pro font from start to bottom (Bahnschrift is a font I am using just for the footnotes in the text. the text behind the first appearance of Garamond Premier Pro in the image means in English: 'Usage of unsupported characters'. This is really strange as the word file opens and reads without any problems and the publisher file has been created from scratch with defining master pages and then importing the word file. Of course, the font is fully installed on my computer. So, what is going on here? Where does this problem come from? And how to get rid of it? Furthermore I have problems with the numbering of the footnotes in the text. In the text everything looks fine. But although I have been using just the standard settings for footnotes all footnotes get an additional digit. For instance footnote 1 in the text is numbered as 1.1 in the footnote body (s. 2. image). And this although I have tried to set the numbering to document (and book and all the other settings wide). The only thing that helps is to delete the place holder for the footnote number (#). But in this case I lose the upward positioning and size reduction of the numbering. What is going on here? Can anybody help me? Thanks!
  6. What about the sidenotes bug(s): disappearing of notes, crashing of Publisher if there are too many or too long notes? And what about display option like sidenotes appearing from top to bottom of a page or filling up from bottom to top? I need these function urgently and would highly appreciate Publisher not crashing when converting footnotes to sidenotes under the mentioned conditions! Of course I can work around these issues but it means a lot of work done by hand although it should at least be assisted by Publisher 2. Thanks.
  7. Thanks, Mike. It is - somewhat - reassuring to hear that other people are affected by the issue as well and that it is not only showing up on my computer. I can work around these problems and I will wait what Serif comes up with in the next updates.
  8. Okay, I tried to follow your advice, Mike. I even stopped using the photos because I would like to have the foot- to sidenote conversion ready first. I even improved the text source by importing and exporting it to my original MS Word (Office 2021). But still some things d not work and one thing lead to an inevitable of publisher 2. Look at the file I have created for you (Example 2). The sidenotes start on page 5. But if you look at page 8 and 9 you still see, what the 'sidenotes' looked like after the conversion: they still use the style of the footnotes, though somewhat changed as can be seen from the style name 'footnote+'. Now, that is not a major issue and can easily converted to the sidenote style called 'Körper' here. This worked nicely until I tried to convert sidenote 7. It included much more text in the original version, and let Publisher repeatedly crash if I changed the style to the more space consuming 'Körper' style. Now I would like to invite you to add further text to sidenote 7, by typing or copying whatever you prefer. You will note, that sidenote 9 and to a growing amount 8 as well disappear. This is especially strange for sidenote 9, as it is already completely an the next page 8, although its referencer is on page 7. What is even more spooky is, that sidenote 9 reappears, if you remove the text again in sidenote 7. But sidenote 8 never appears again in its full length. Just the first line reappears. Actually, I just noticed that publisher seems to add a full, though invisble page to the document if you add further text to sidenote 7. I think there is something very buggy with your sidenotes. Example2.afpub
  9. It would be extremely helpful, though, if you could make the sidenotes start at the top of the page. Now everything is pushed to the bottom of the page and the next page. It simply doesn't seem the best way to organize sidenotes. Also we want to add images to make the side info more valuable, and that the side notes don not fill the page height limits us. BTW, here is the word file that let the Pub crash - or at least the first ten pages of it. The result should look more or less like the pdf. Example.docx 20230113 Satzexperiment01 p4-6.pdf
  10. I will share a part of the file later. I have found a work around in manually replacing each footnote by a sidenote. I really hate(!) that the sidenote content is not just placed in a textframe that could(!) be moved around independently – and actually I am thinking about doing that myself to gain more freedom in designing the pages. Publisher crashes here whenever I do quite ordinary things like copying text into sidenotes that extent over more than one page (yes, I have actiated split notes). Actually, I am thinking that the problems might have to do with the Word file I am using as material. As I have learned it is itself a file that was exported from Pages. And I ran into problems with such a file before ... Is that possible? (The file opens and behaves very well in Word.)
  11. And Publisher crashes also, when I try to add a sidenote on a page that has no space left for additional sidenotes, so that the note would have to be placed on one of next pages. This is more than frustrating!
  12. If I may also suggest a new feature, it would be to enable also the vertical positioning of sidenotes, i.e. to enable a positioning starting at the top of the page/frame (running down just one after the other) or at the position of the text where the sidenote is entered or that the sidenotes are filled up one over the other on the side to end at the bottom of the the page/frame. Or even to make the frames of the sidenotes freely movable around the page.
  13. Hi, I started to work on a book project yesterday. The text was written in word and contains about 250 footnotes. It imports smoothly into the text frames I have created, showing all the footnotes without issue. But when I activate the replacement function in publisher (Text --> Notes) Publisher crashes, i.e. it just disappears from the screen. An info window with a report for Apple appearing a few seconds later is all info I get. I am running Pub 2 on a MacBook Pro M1 with M1pro and 16 GB under macOS Ventura 13.1. I have restarted my system several times but no improvement. This is extremely deterring as the book is my main work right now and the whole design concept relies on sidenotes. Is this a known issue? Thanks
  14. You are right, Wosven, the files are required. It was too late yesterday, I am sorry. Meanwhile I have checked the RTF import. It does not show any unexpected breaks, yet it lost the small caps. A tedious fault to repair ... So if anybody in the know should have a closer look at the files, maybe you could give me a hint how to avoid the unexpected breaks? Thank you. BTW, in this case I have used the 'original' Word file for the import, but please note that I have no certain knowledge whether its origin is really Word itself. It might well be like in my case with Pages that it is just the result of some format changing export procedure from some other software. Please be aware the the first unexpected break occurs on page 7 of the publisher document. Thanks again for your help. Highly appreciated! Import test word -> publisher.afpub Layout Garamond V5 J1 T1.docx
×
×
  • Create New...

Important Information

Terms of Use | 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.