Layout to PDF text cutting off

I see several closed threads about this but there doesn’t seem to be any solutions. When I export from Layout to PDF, the text is cut in half. I’ve tried almost every sans serif font available to Microsoft. I’ve tried all of the options in the text pulldown menu and nothing repairs the issue.


Since I’m not the first person to have this problem, is there a solution that doesn’t require me to give someone my files?

Hi, try to change the Text Line Height to default from Menu bar > Text > Spacing.

http://help.sketchup.com/en/layout/formatting-text#:~:text=Line%20spacing%3A%20From%20the%20menu,from%20the%20submenu%20that%20appears.

You’re telling me that the custom spacing always results in errors like this?

Yes, I got that issue before.

I found a thread about this from 2020. Too bad no one has addressed it yet.
I guess my drawings have to look ugly.
Thank you for your help.

1 Like

I haven’t seen that. Can you share a file? Is it only rotated text? And what font are you using?

b

There are several threads over the past 5 years where others have had this issue. I found them in a Google search.
-I don’t share my files. Far too much liability.
-All text where I tried to use custom spacing. Single spacing is far too wide for highly detailed construction drawings.
-All fonts.
Don’t worry about it. I have other options than LO. For all my 24x36 pages, I arrange the SU scenes on pages in LO without any text. Then create jpgs of each page and import each onto pages in my 2D drafting program for adding text or dimensions. The extra steps take longer and the pdfs created from the other program are huge files, but at least those drawings are readable. I’ll be doing this for other page sizes as well, I guess.
My 2D page program was created in and hasn’t been updated since 1997. Maybe LO will catch up to the 90s?

I’ll start using LO again when it let’s me create pages of this quality. At single spacing, I would need twice as many pages

Are you changing output resolution in File->Document Setup->Rendering? The normal workflow is to work in lower resolution and export high, although I always get a beefy enough machine and do both in high when I can.

b

-My machine is more than beefy enough to handle Enscape scenes and trees that cover several square miles of Location Terrain from SU.
-I have my screen res set low and my output set high, already.

My documents can be text heavy and I try not to produce ugly documents.

I have occasional rotated text and it’s never cut off like that.

Can’t you rustle up and share an example file showing the issue?

Again, the issue was directly related to custom spacing of the text and apparently has been around since the 2020 version. There doesn’t seem to be any interest in fixing it.
In this example, the top grouping is single spacing and the bottom two are custom spacing. The top row of text gets cut off only in the PDF export.
Do you want me to send you this LO file?

You don’t need to share a client file. Just create the issue and post it. It could be gibberish for all we care. Or you could copy / paste out the offending text into a blank template - that would have taken less time than me typing this reply.

I’m sure the SKP team would be interested in learning where this breaks down.

Here’s someone with the same issue in 2020

I did right before you sent your last message

I don’t have this issue that you have.

Like Mike said – just share an example gibberish file.

What you shared was a screenshot – we can’t diagnose from that.

I already did that. Scroll up

LO text spacing.layout (23.2 KB)

Forgive if I’m being dense but what custom spacing are you trying to achieve?

In the example file the font is set at 10pt and with the custom spaced text boxes you have set the custom spacing to 8pt which is less than the font size and the lines will therefore will get bunched.

For sure – if you want bunched up lines like that (I think it’s ugly) then it’s going to get trimmed off like that (it’s trimmed in Layout if you look closely).

But that’s no excuse – yep, I guess it’s a bug and ought to be fixed…

ok – I’ll take my words back somewhat.

There is something odd going on but I have never noticed it in my workflow because the way I work with text is a little different to what you have shown in the file.