Please update documentation on how to use unicode engines and fontspec #34

Activity

1. welcome commented on Jul 11, 2023

   

   welcomeBot

   on Jul 11, 2023

   More actions

   Thanks for opening your first issue here! Make sure that no other issues on the same topic have already been opened!
2. gsilano

   self-assigned this

   on Jul 13, 2023
3. gsilano commented on Jul 13, 2023

   

   gsilano

   on Jul 13, 2023

   Owner

   More actions

   Hi! Thanks for raising this issue and suggesting the use of Lualatex or xelatex with their advantages in supporting unicode and system fonts. It would be beneficial to provide documentation on utilizing these engines and fonspec effectively. Unfortunately, I don't have the time to explore this implementation currently.

   If you have any ideas or are already working on it, please feel free to share your draft or thoughts. I appreciate your input in enhancing our project.
4. callegar commented on Jul 15, 2023

   

   callegar

   on Jul 15, 2023

   Author

   More actions

   As a matter of fact, everything works well with the unicode engines, once one has discovered a few tricks:

   • do the obvious \usepackage{fontspec} in the preamble
   • load the fonts using \setmainfont, \setsansfont, \setmonofont.
   • in the sans font make sure that you define a compact face, e.g. \setsansfont{TeX Gyre Heros}[FontFace = {c}{\shapedefault}{TeX Gyre Heros Cn }] otherwise the option narrow won't work.
   • have a \renewcommand{\familydefault}{\sfdefault} if your main family is a serif font

   furthemore you may want to have

   \makeatletter
   \def\ecv@lfoot{%
     \footnotesize\textup{\ecv@page~-~\ecv@cvofkey}\\
     \textup{\ecv@footername}
   }
   \makeatother

   in the preamble if your main font is serif and you want the page number in sans. This changes the \textrm to \textup in \def\ecv@lfoot.

   Documenting this might be useful IMHO.

   👍React with 👍1Reacted by Christian Cahig
5. gsilano

   added

   type: enhancementNew feature or requestNew feature or request

   on Jul 15, 2023
6. gsilano commented on Jul 24, 2023

   

   gsilano

   on Jul 24, 2023

   Last edited by gsilano

   Owner

   More actions

   Absolutely! I totally agree with you, but unfortunately, I'm swamped with tasks right now. However, would you be up for helping out by improving the documentation? You can make your changes in the europecv.tex file. Once you're done, just open a pull request with your updates. After that, I'll review everything and merge it into the repository. Eventually, I'll also make sure to propagate those changes on CTAN. Thanks a bunch for your support! 😊

   👍React with 👍1Reacted by Christian Cahig
7. github-actions commented on Oct 16, 2026

   

   github-actionsBot

   on Oct 16, 2026 – with GitHub Actions

   More actions

   This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
8. github-actions

   added

   wontfixThis will not be worked onThis will not be worked on

   on Oct 16, 2026
9. gsilano

   added a commit that references this issue on Oct 19, 2026

   Fix stranded rule at page bottom, PostScript detection, fontspec docs

   ...

   fb8a5a8
10. gsilano commented on Oct 19, 2026

    

    gsilano

    on Oct 19, 2026 – with Claude

    Owner

    More actions

    This is addressed in fb8a5a8 (part of #52), building on your notes, @callegar.

    Documentation: the manual has a new part, "Using XeLaTeX and LuaLaTeX", in the "Dependencies" section. It covers:

    • fontspec with \setmainfont, \setsansfont and \setmonofont;
    • dropping inputenc and fontenc (the input encoding options are ignored with a warning under Unicode engines);
    • fonts with the glyphs needed by the language options (Greek, Cyrillic, ...);
    • \renewcommand{\familydefault}{\sfdefault} with a sans serif font such as TeX Gyre Heros or Arial;
    • an example preamble that works with both europecv and the new europecv2020 class.

    narrow option: while testing, I found that with fontspec the narrow option can't reliably be combined with FontFace. The option sets \bfdefault to bc, and fontspec then registers its regular bold face under that series, overriding the bold condensed FontFace (bold text came out in TeX Gyre Heros Bold, not Heros Cn Bold). The manual therefore recommends selecting a condensed family directly, for example \setsansfont{TeX Gyre Heros Cn}. Its regular and bold faces are then both condensed, and XeLaTeX and LuaLaTeX compile it with no font warnings.

    Footer: the footer now uses \textup instead of \textrm, as you suggested, so it follows \familydefault without the redefinition of \ecv@lfoot in the preamble.

    This will be available on CTAN with the next release (2026.10.19).

    ---

    Generated by Claude Code
11. gsilano

    closed this as completedon Oct 19, 2026