Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
callegar opened this issue Jul 11, 2023 · 4 comments
Open
Assignees
Labels
type: enhancement New feature or request

Comments

@callegar
Copy link

It is now common to use Lualatex or xelatex. While both can fall back to operate as the traditional latex engine, there is advantage in using their ability to fully support unicode and to use system (otf, ttf) fonts.

Would be good to have some notes in the documentation on how to best use these engines and fonspec.

@welcome
Copy link

welcome bot commented Jul 11, 2023

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

@gsilano gsilano self-assigned this Jul 13, 2023
@gsilano
Copy link
Owner

gsilano commented Jul 13, 2023

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.

@callegar
Copy link
Author

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.

@gsilano gsilano added the type: enhancement New feature or request label Jul 15, 2023
@gsilano
Copy link
Owner

gsilano commented Jul 24, 2023

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! 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants