On Tuesday, August 17, 2021 at 1:03:39 PM UTC-4 BP wrote:

On 2021-08-16 18:31, Hugh Esco wrote:
> Reason I ask is that this query of my file system was not very helpful to
> narrowing down what path to a noto font was being used, or what file
> extension I might be interested in as I explore my options to satisfy my
> client's requirements.
>
> ```
> $ find /usr/share/ -name noto
> /usr/share/texlive/texmf-dist/fonts/truetype/google/noto
> /usr/share/texlive/texmf-dist/fonts/enc/dvips/noto
> /usr/share/texlive/texmf-dist/fonts/opentype/google/noto
> /usr/share/texlive/texmf-dist/fonts/map/dvips/noto
> /usr/share/texlive/texmf-dist/fonts/type1/google/noto
> /usr/share/texlive/texmf-dist/fonts/vf/google/noto
> /usr/share/texlive/texmf-dist/fonts/tfm/google/noto
> /usr/share/texlive/texmf-dist/tex/latex/noto
> /usr/share/fonts/truetype/noto
> /usr/share/fonts/opentype/noto
> ```
>

There is info in secs 2.2 and 2.3 of the fontspec docs which I linked to
earlier on how to load fonts by path and file name. Basically like this
if doing it from a defaults file:

``````yaml
from: markdown
to: latex
pdf-engine: xelatex
variables:
mainfont: NotoSerif-Condensed
mainfontoptions: &fontoptions
- 'Path=/home/benct/.fonts/Noto/'
- 'UprightFont=*Medium.ttf'
- 'BoldFont=*SemiBold.ttf'
- 'ItalicFont=*MediumItalic.ttf'
- 'BoldItalicFont=*SemiBoldItalic.ttf'
sansfont: NotoSans-Condensed
sansfontoptions: *fontoptions
monofont: NotoSansMono-
monofontoptions:
- 'Path=/home/benct/.fonts/Noto/'
- 'UprightFont=*Medium.ttf'
- 'BoldFont=*SemiBold.ttf'
``````

Pandoc just copies all this into the fontspec `\setmainfont` etc.
commands. It is possible that the quotes aren't always necessary but the
likelihood that the YAML parser doesn't like asterisks in unquoted
strings is high, so use quotes when in doubt.
You can use YAML anchors and references to save on the typing inside the
same defaults file but as you see I couldn't do it with SansMono because
it doesn't have any italic styles. You could fake italic with fontspec's
FakeSlant feature if you really needed it.

>
> On Monday, August 16, 2021 at 12:10:54 PM UTC-4 Hugh Esco wrote:
>
>> OK, this seems to be working better now:
>>
>> ```
>> pandoc 2.14.1
>> Compiled with pandoc-types 1.22, texmath 0.12.3, skylighting 0.11,
>> citeproc 0.4.1, ipynb 0.1.0.1
>> User data directory: /home/hesco/.pandoc
>> Copyright (C) 2006-2021 John MacFarlane. Web: https://pandoc.org
>> ```
>>
>> NEXT QUESTIONS:
>>
>> What path is being searched for fonts?
>> How do I know what my options are?
>>
>> On Monday, August 16, 2021 at 11:55:41 AM UTC-4 Hugh Esco wrote:
>>
>>> pandoc 1.19.2.4
>>> Compiled with pandoc-types 1.17.0.5, texmath 0.9.4.4, skylighting 0.3.3.1
>>> Default user data directory: /home/hesco/.pandoc
>>> Copyright (C) 2006-2016 John MacFarlane
>>> Web: http://pandoc.org
>>>
>>> On Monday, August 16, 2021 at 11:46:08 AM UTC-4 BPJ wrote:
>>>
>>>> You probably need to upgrade pandoc.
>>>> What does pandoc --version say?
>>>>
>>>> Den mån 16 aug. 2021 17:10Hugh Esco <hre...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
>>>>
>>>>> My attempts to test this yield errors looking like this:
>>>>>
>>>>> ```
>>>>> $ pandoc --defaults `pwd`/defaults --latex-engine=lualatex
>>>>> --template=my_client.latex my_source_file.pdc -o my_result_file.pdf
>>>>> pandoc: unrecognized option `--defaults'
>>>>> Try pandoc --help for more information.
>>>>> ```
>>>>> looking at the --help output yields this:
>>>>>
>>>>> ```
>>>>> $ pandoc --help | grep default
>>>>> -D FORMAT --print-default-template=FORMAT
>>>>> --print-default-data-file=FILE
>>>>> --default-image-extension=extension
>>>>> ```
>>>>>
>>>>> but no `--defaults` switch. What am I missing here, please?
>>>>>
>>>>> -- Hugh
>>>>>
>>>>> On Monday, August 16, 2021 at 4:32:15 AM UTC-4 BPJ wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> Den mån 16 aug. 2021 10:25BPJ <b...-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org> skrev:
>>>>>>
>>>>>>> You use the `mainfont`, `sansfont`, `monofont`, `mathfont`,
>>>>>>> `CJKmainfont`
>>>>>>> variables for the font names and the corresponding `mainfontoptions`
>>>>>>> etc.
>>>>>>> variables. The latter are lists of strings with raw fontspec[^1]
>>>>>>> options in the format `'Option=Value'` or `'Option={Multi-word value}'`. The
>>>>>>> easiest way is to specify them is in a defaults file[^2] like this:
>>>>>>>
>>>>>>> from: markdown
>>>>>>> to: latex
>>>>>>> pdf-engine: xelatex
>>>>>>> variables:
>>>>>>> mainfont: Noto Serif
>>>>>>> sansfont: Noto Sans
>>>>>>> monofont: Noto Mono
>>>>>>> monofontoptions:
>>>>>>> - 'Scale=MatchLowercase'
>>>>>>>
>>>>>>> For some reason the default latex template[^3] does not contain any
>>>>>>> variable for `defaultfontfeatures` but
>>>>>>> `\defaultfontfeatures{Scale=MatchLowercase}` is hard coded. In my
>>>>>>> custom
>>>>>>> template I have added that variable[^4]:
>>>>>>>
>>>>>>> $if(defaultfontfeatures)$
>>>>>>>
>>>>>>> \mainfontfeatures{$for(mainfontfeatures)$$mainfontfeatures$$sep$,$endfor$}
>>>>>>> $else$
>>>>>>>
>>>>>> \defaultfontfeatures{Scale=MatchLowercase}
>>>>>>> $endif$
>>>>>>>
>>>>>>
>>>>>> Sorry, a typo: it should be `defaultfontfeatures` rather than
>>>>>> `mainfontfeatures`. That's what happens when you copy the wrong line and
>>>>>> use search/replace to make up for it! :-/
>>>>>>
>>>>>>
>>>>>>> Font embedding depends on your XeTeX/LuaTeX settings. Usually it Just
>>>>>>> Works.
>>>>>>>
>>>>>>>
>>>>>>> [^1]: https://ctan.org/pkg/fontspec
>>>>>>>
>>>>>>> [^2]: https://pandoc.org/MANUAL.html#default-files
>>>>>>>
>>>>>>> [^3]: https://pandoc.org/MANUAL.html#templates
>>>>>>>
>>>>>>> [^4]: https://git.io/J0UJS
>>>>>>>
>>>>>>>
>>>>>>> Den mån 16 aug. 2021 06:56Hugh Esco <hre...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
>>>>>>>
>>>>>>>> My tests seem to indicate that the fonts which are available to me
>>>>>>>> are a function of the value of the `--latex-engine=` switch.
>>>>>>>>
>>>>>>>> If I set that switch to pdflatex (which seems to be the default), I
>>>>>>>> can choose any font installed as a .sty file at this path:
>>>>>>>> `/usr/share/texlive/texmf-dist/tex/latex/psnfss/`, by setting a value to
>>>>>>>> the fontenc key at the top of my markdown source file.
>>>>>>>>
>>>>>>>> But I have not been able to sort out how to access other fonts
>>>>>>>> installed at `/usr/share`, by setting the `--latex-engine` to `lualatext`
>>>>>>>> or `xelatex`.
>>>>>>>>
>>>>>>>> All my tests seem to look alike, and changing my fonts has no impact
>>>>>>>> on how the resulting pdf looks.
>>>>>>>>
>>>>>>>> Can someone please point me to some documentation which would help
>>>>>>>> me understand how to use the full range of fonts available on this system,
>>>>>>>> suitable for which ever value I set to the `--latext-engine` switch?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> -- Hugh Esco
>>>>>>>>
>>>>>>>> --
>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>> Groups "pandoc-discuss" group.
>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>> send an email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
>>>>>>>> To view this discussion on the web visit
>>>>>>>> https://groups.google.com/d/msgid/pandoc-discuss/543536ca-7ced-4033-ad1a-ecdd3fedaf44n%40googlegroups.com
>>>>>>>> <https://groups.google.com/d/msgid/pandoc-discuss/543536ca-7ced-4033-ad1a-ecdd3fedaf44n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>>> .
>>>>>>>>
>>>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "pandoc-discuss" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
>>>>>
>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/pandoc-discuss/512edc0d-8cbb-4e97-92b9-5cd1a1bdfffen%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/pandoc-discuss/512edc0d-8cbb-4e97-92b9-5cd1a1bdfffen%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>
>