Rendering issue with recent MacTex 2024

[gbergling]

I recently discovered that something in the last couple of weeks produces an rendering error with XeLaTex on MacTex 2024. The headlines got screwed up. See the attached screenshot.

Any hints on solving this?

[github-actions]

👋 Welcome! Looks like this is your first issue.

Hey, thanks for your contribution! Please give us a bit of time to review it. 😄

[JerryAZR]

I'm experiencing the same issue on Windows with XeLaTex and LuaLaTex.
However on Overleaf it seems to render correctly

Version info:

> xelatex --version

XeTeX 3.141592653-2.6-0.999996 (TeX Live 2024)
kpathsea version 6.4.0

> lualatex --version

This is LuaHBTeX, Version 1.18.0 (TeX Live 2024)
Development id: 7611

[pannone]

I had the same problem on Windows. I have solved by modifying line 665 of the file awesome-cv.cls from \vspace{-2.0mm} to \vspace{2.0mm} (I just removed the minus). Let me know if it works also for you!

[galaris]

Also affecting osx

a@b examples % xelatex --version
XeTeX 3.141592653-2.6-0.999996 (TeX Live 2024)
kpathsea version 6.4.0
Compiled with ICU version 74.2; using 74.2
Compiled with zlib version 1.3.1; using 1.3.1
Compiled with FreeType2 version 2.13.2; using 2.13.2
Compiled with Graphite2 version 1.3.14; using 1.3.14
Compiled with HarfBuzz version 8.3.0; using 8.3.0
Compiled with libpng version 1.6.43; using 1.6.43
Compiled with pplib version v2.2
Using Mac OS X Core Text and Cocoa frameworks

a@b examples % lualatex --version
This is LuaHBTeX, Version 1.18.0 (TeX Live 2024)
Development id: 7611

I had the same problem on Windows. I have solved by modifying line 665 of the file awesome-cv.cls from \vspace{-2.0mm} to \vspace{2.0mm} (I just removed the minus). Let me know if it works also for you!

This solved it, thank you!

[mitcdh]

I had the same problem on Windows. I have solved by modifying line 665 of the file awesome-cv.cls from \vspace{-2.0mm} to \vspace{2.0mm} (I just removed the minus). Let me know if it works also for you!

I'm not sure this is the whole fix, I was playing around with it, and there seems to be a lot of extra space now around centuries. Also cvitems lists don't seem to render correctly. Are those not occurring for you?

[pannone]

Hi, for what I am seeing it seems that it renders correctly. Il sab 3 ago 2024, 12:21 Mitchell Hewes ***@***.***> ha scritto:

…

I had the same problem on Windows. I have solved by modifying line 665 of the file *awesome-cv.cls* from \vspace{-2.0mm} to \vspace{2.0mm} (I just removed the minus). Let me know if it works also for you! I'm not sure this is the whole fix, I was playing around with it, and there seems to be a lot of extra space now around centuries. Also cvitems lists don't seem to render correctly. Are those not occurring for you? — Reply to this email directly, view it on GitHub <#532 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHHB6BCRAOHOSDFACDFDJHLZPSVJLAVCNFSM6AAAAABK25XIVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRWGY3DKNJWGA> . You are receiving this because you commented.Message ID: ***@***.***>

[mitcdh]

This is an example of how it renders to me with just the inversion of the 2.0mm.

Here is the original:

[ericswpark]

Can confirm the same issue with MiKTeX on Windows, and unfortunately @pannone 's suggestion above didn't completely fix the issue for me. It did get rid of the overlaps, but just like @mitcdh 's example there's still a lot of unnecessary margin that wasn't there before. Wondering what changed between the distribution updates to cause such behavior.

[pannone]

I do apologize for the non-complete fix. I have Miktex on Windows too, and actually I have noticed now that I also have some extra space. Sorry again! Il mer 7 ago 2024, 10:53 Eric Park ***@***.***> ha scritto:

…

Can confirm the same issue with MiKTeX on Windows, and unfortunately @pannone <https://github.com/pannone> 's suggestion above didn't completely fix the issue for me. It did get rid of the overlaps, but just like @mitcdh <https://github.com/mitcdh> 's example there's still a lot of unnecessary margin that wasn't there before. Wondering what changed between the distribution updates to cause such behavior. — Reply to this email directly, view it on GitHub <#532 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHHB6BD6HQZ37WDJK6DJIHLZQHOBDAVCNFSM6AAAAABK25XIVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZSHE3DCOJVGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ericswpark]

I'm not sure whether my PR will fix the issue for everyone, but changing the \vspace for the cvitems directive fixed the issue for me. The output from MiKTeX matches up exactly with previous generations. If you are affected by this issue please test with the PR and leave a comment on whether it works for you or not. Thanks!

[thiagoveloso]

I'm not sure whether my PR will fix the issue for everyone, but changing the \vspace for the cvitems directive fixed the issue for me. The output from MiKTeX matches up exactly with previous generations. If you are affected by this issue please test with the PR and leave a comment on whether it works for you or not. Thanks!

I just wanted to let you know that the fix worked for me, while the proposed fix by @pannone did not.

[sandrofsousa]

Can confirm that @ericswpark commit fixed the issue for me on latest mactex.

[krapie]

@ericswpark's workaround worked for me, thanks! 👍🏼

[marcosrosse]

@ericswpark solution also worked for me, thanks! 👍