derekkinsman
-
Posts
16 -
Joined
-
Last visited
Posts posted by derekkinsman
-
-
M1 MacOS Monterey (12.4), Publisher 1.10.5.
I've attached some screenshots, but the gist of it is that a body of text will wrap from one column to the next before reaching the bottom and any attempt to force that wrapped text back will cause the next line to wrap forward instead. In the screenshots you can see Column 1 goes all the way to the bottom, Column 2 wraps with one line of space available, Column 3 (second screenshot) has that single line, at the top of the next page now, that should be at the bottom of Column 2. If I do something like set the tracking on the paragraph really tightly to pull that Column 3 text back across to column 2 the current bottom line from Column 2 ("first design for…") will instead move over to the top of Column 3, leaving even more space at the bottom of Column 2. All the text in the document is being controlled with text styles and there isn't any accidental line heights or paragraph spacing happening. And it's happening randomly through the full document. The source of the text was originally a Word docx file, but even backspacing the text and manually typing it out in Publisher has no effect.
-
3 minutes ago, Old Bruce said:
Do you have the menu item View > Show Guides checked?
Huh, turns out I did not have that enabled. I guess that resolved that bug. Or turns this into a feature request: dragging a guide into the workspace should turn guides on, and/or, guides should be on by default.
Thanks!
-
Currently on version 1.8.4, and macOS 10.14.5.
The guides will only appear in the "ruler" section as you can see in on the top ruler one inch from the left.
-
@Alfred Crimson Pro is the third iteration of the font. https://github.com/skosch/Crimson
-
@knguyen as a fix, you can download Crimson Pro (it's not on Google Fonts, still free). It is something that can be exported to PDF.
-
@Pauls just discovered that this crash also happens when I try and reorder pages via the Pages Tray.
-
@Pauls It looks like it's only happening in one document. Is there a way to get the crash log? The Apple Crash Reporter tool doesn't actually pop up ever. It's more like the app just quits.
Here's the results of me slowly deleting all the assets from a duplicate file and trying to figure out what's causing it:
- Inserting 2 pages works fine, it only crashes when 1 page is inserted
- Inserting before or after doesn't make a difference.
I've attached the duplicate with zero assets, just a bunch of blank pages, in it as it still crashes the app for me.
-
Using 1.8.2 on MacOS 10.14.5.
Crashes every time I insert a page from the left hand Pages tray. Add page from the menu bar works fine.
-
16 minutes ago, Pauls said:
is that from Google Fonts or somewhere else?
You can upload files to the original location
Yeah, I think it's from Google Fonts. Possibly Font Squirrel. I actually resolved it. I'm not sure why but there were multiple installed copies, only one was active (the OTF version). I reactivated all versions, then cleaned up the "multiple versions" error and now everything works as expected.
Maybe Publisher is trying to use TTF files, and it craps out because they're disabled? No idea. But reseting the active/inactive/multiple versions states of fonts fixes it.
-
On 12/19/2019 at 4:35 AM, Pauls said:
Some people have been getting problems when they have duplicate fonts installed - maybe you have 2 versions of the problematic font ?
This error has popped up again. Different font (Vollkorn). The font is working in the first row of the table. Fails in the paragraph, and the second column. It also displays correctly in the first column, however it has decided to reduce all the numbers by 1, so instead of that column going from 1-8, it now goes 0-7. It also no longer works in a file that it once worked in. Happy to send you some files as well. It also works when I export to all the other file formats.
-
1 hour ago, LibreTraining said:
Crimson Text has problems with how the name fields are configured.
Everything is in the style group fields and the Typographic Family fields are empty.
Style groups should only have: Regular, Italic, Bold, Bold Italic
Crimson Text also has Roman, Semibold, Semibold Italic in there.
This is confusing APub and causing font corruption.
It also confuses the heck out of LibreOffice.
So I made a version with fixed names which works properly in LibreOffice - Crimson Text LO
Just tested and it also works properly in APub 1.8 beta.
I left "Roman" in the Typographic Style field where is is OK.Crimson.Text.LO.(fixed.names).7z
Try those fonts.
My guess is that will solve your issue.Interesting. Will give it a try. Although, as in my screen grab above Crimson Text works fine in one document, and not in the other.
-
Also just noticed this. Doesn't happen all the time. For me it's specifically Crimson Text, Roman that goes all gobbledegook. Italics, Semibold, Semibold Italic, Bold, and Bold Italic all work fine. Just tried to create a test file to upload and it worked completely fine. Same font.
-
Interestingly, for three different documents I get two different errors.
1. Can no longer reproduce error I described above.
2. Works. File printed.
3. Crashes the instant I hit Print, as described in original post. -
@Jon P this is also reproducible by changing options in the print dialogue. It happens to me when I go Print > Layout > Pages Per Sheet: <select anything>. Crash.
Text wrapping to next column before hitting the bottom of the current column
in V1 Bugs found on macOS
Posted
@Dan C omg, you're a hero. It was the "Keep with next: N⇅ lines" option that was causing it. Mine had defaulted to 1. I somewhat assumed that was disabled/required one of the above options being enabled due to it being right aligned while the other options were left aligned. But it's fixed now. Thanks for the quick reply!
Be well.