py/ai-job-search
1
0
Fork 0
mirror of https://github.com/MadsLorentzen/ai-job-search.git synced 2026-09-17 00:26:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(changelog): the \namefont override is live on every moderncv version, not a 2.4+ no-op

Browse Source 
The #323 entry described the renewcommand as 'a true no-op on moderncv 2.4+';
head iii's \firstnamestyle/\lastnamestyle route through \namefont, so the
override is what produces the 34pt name on 2.4+ as well. Verified by macro
expansion at review time.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Mads Lorentzen
2026-08-15 21:32:11 +02:00
co-authored by Claude Fable 5
parent c696b60b77
commit 5c6ffe8aa7
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+3 -3
View File
@@ -37,9 +37,9 @@ per-file diff commands.
set its name styling through `\firstnamestyle`/`\lastnamestyle`, which moderncv 2.3.1 set its name styling through `\firstnamestyle`/`\lastnamestyle`, which moderncv 2.3.1
(Debian/Ubuntu apt) does not have, so a fresh fork could not compile its own example CV (Debian/Ubuntu apt) does not have, so a fresh fork could not compile its own example CV
on that toolchain. Name styling now routes through `\namefont`, the hook every name-style on that toolchain. Name styling now routes through `\namefont`, the hook every name-style
macro shares: a true no-op on moderncv 2.4+ (where head iii typesets via macro shares: live on every version (on 2.4+, head iii's `\firstnamestyle`/`\lastnamestyle`
`\firstnamestyle`/`\lastnamestyle` and never calls `\namefont`'s replacements), and the both route through `\namefont`, so the override is what sets the 34pt name there too), and
only option on 2.3.1 where those macros do not exist. Two review follow-ups landed in the the only option on 2.3.1 where those macros do not exist. Two review follow-ups landed in the
same change: the `\hypersetup` comment now names the real clash mechanism same change: the `\hypersetup` comment now names the real clash mechanism
(`\RequirePackage[unicode]{hyperref}` on < 2.4; `\PassOptionsToPackage`, introduced in (`\RequirePackage[unicode]{hyperref}` on < 2.4; `\PassOptionsToPackage`, introduced in
2.4.0, is what removes the clash), and the metadata block sets `pdfpagemode=UseNone` - a 2.4.0, is what removes the clash), and the metadata block sets `pdfpagemode=UseNone` - a