Stefan Nobis writes:
> The other problem: Not everyone does a full installation of TeX Live.
> So even if good fonts are available, they are not always installed on
> every system (but this part could be mitigated by documentation and/or
> error messages and hints).
Fair point.
I guess that a vi
Google’s Noto font might have the best coverage and is open source.
Tom
> On Jul 2, 2023, at 7:48 PM, Stefan Nobis wrote:
>
> Ihor Radchenko writes:
>
>> Though ideally all the necessary fonts should be provided by
>> TeXLive. I am not sure why they are not yet there in 2023.
>
> First pro
Ihor Radchenko writes:
> Though ideally all the necessary fonts should be provided by
> TeXLive. I am not sure why they are not yet there in 2023.
First problem: Is there any free/libre font out there that has a
really broad and comprehensive coverage of Unicode glyphs? I really
don't know, but
Stefan Nobis writes:
> Ihor Radchenko writes:
>
>> AFAIR, the basic problem is that we cannot guarantee that any given
>> UTF font is installed.
>
> Yes, indeed. Probably the best route is to make tweaking as easy as
> possible. There are still too few (if any) really comprehensive (and
> good l
Ihor Radchenko writes:
> AFAIR, the basic problem is that we cannot guarantee that any given
> UTF font is installed.
Yes, indeed. Probably the best route is to make tweaking as easy as
possible. There are still too few (if any) really comprehensive (and
good looking) Unicode fonts available.
-
"Dr. Arne Babenhauserheide" writes:
> Isn’t the speed more relevant for large documents?
I always had the impression that luatex has mostly a rather fixed
overhead. Maybe that's because many of my larger documents make quite
some use of TikZ and most time may be spend there. Therefore I assumed
Hi. Stefan.
> "Stefan" == Stefan Nobis writes:
[...]
Stefan> That's quite strange. I just re-tested with emacs -Q (Emacs 28.2
with integrated Org
Stefan> 9.5.5). It generates the following tex file:
[...]
Stefan> Maybe there are some other configurations on the Emacs or LaT
Stefan Nobis writes:
> But only recently I discovered a package called "fontsetup". And this
> package seems to provide a big step towards the goal discussed in the
> above mentioned thread: Provide default fonts for most common
> situations. The goal of fontsetup is more about easy switching bet
Stefan Nobis writes:
> Ihor Radchenko writes:
>
>> The downside of lualatex is that it is slower:
>> https://list.orgmode.org/orgmode/87a69j9c6s.fsf@localhost/
>
> Yes, for sure. But I have the impression that newer versions of luatex
> have become a bit faster (maybe it's just a subjective imp
Stefan Nobis writes:
> On the other hand: Luatex is much more flexible and has better support
> for modern fonts and modern font render engines.
So does xelatex, AFAIU.
> It depends what one assumes to be the most common use case for Org. If
> it's many rather short and simple documents then pd
Ihor Radchenko writes:
> The downside of lualatex is that it is slower:
> https://list.orgmode.org/orgmode/87a69j9c6s.fsf@localhost/
BTW: One of the discussion points in that thread has been the problem
of default fonts. With pdflatex the default font is CM (Computer
Modern) and if the appropria
Ihor Radchenko writes:
> The downside of lualatex is that it is slower:
> https://list.orgmode.org/orgmode/87a69j9c6s.fsf@localhost/
Yes, for sure. But I have the impression that newer versions of luatex
have become a bit faster (maybe it's just a subjective impression that
I want to be true, be
andrés ramírez writes:
> I have tried the snippet. But It shows just Japanese and the other
> paragraphs are not present on the PDF.
That's quite strange. I just re-tested with emacs -Q (Emacs 28.2 with
integrated Org 9.5.5). It generates the following tex file:
--8<---cut here-
Hi. Stefan.
> "Stefan" == Stefan Nobis writes:
Stefan> Hi. I got curious and it seems if you are willing to use lualatex
(which is, I think,
Stefan> currently the most actively developed engine and nowadays a really
good choice), the
Stefan> following solution should work:
[
Stefan Nobis writes:
> I have no experience with Japanese output and I'm unable to read
> Japanese, so I could not judge the correctness or quality. But the
> above approach seems to work quite well and it might be possible to
> support this solution from the Org side (because only a single packa
Hi.
I got curious and it seems if you are willing to use lualatex (which
is, I think, currently the most actively developed engine and nowadays
a really good choice), the following solution should work:
--8<---cut here---start->8---
#+TITLE: Doc multi-lingual
andrés ramírez writes:
> Arne> I think you have to solve this on the LaTeX-side: including
> packages that support the
> Arne> required unicode.
> Thanks. That helped. It ended like this:
I’m glad to hear that! Thank you for posting your solution.
> #+LATEX_HEADER: \usepackage{CJKutf8
Hi. Ihor.
> "Ihor" == Ihor Radchenko writes:
[...]
Ihor> We discussed a similar issue previously in
Ihor> https://list.orgmode.org/orgmode/87h6z7jq4o.fsf@localhost/
I have dowloaded de whole thread. And I got something that shows
'quotation marks' in place of Japanese characteres.
Hi. Arne.
> "Arne" == Arne Babenhauserheide writes:
[...]
Arne> I think you have to solve this on the LaTeX-side: including packages
that support the
Arne> required unicode.
[...]
Thanks. That helped. It ended like this:
--8<---cut here---start-
"Dr. Arne Babenhauserheide" writes:
> I think you have to solve this on the LaTeX-side: including packages
> that support the required unicode.
Well. Org does provide support for non-English languages. For example,
see org-latex-language-alist and org-latex-guess-babel-language.
It would be nic
Hi,
Andrés Ramírez writes:
> Could You address me to the proper sintax for the japanese characters to
> appear in the output?.
I think you have to solve this on the LaTeX-side: including packages
that support the required unicode.
For a part of that I usually use uniinput, for example this:
htt
Andrés Ramírez writes:
> When exporting this document the Japanese characters do not appear in
> the output.
> ...
> Could You address me to the proper sintax for the japanese characters to
> appear in the output?.
We discussed a similar issue previously in
https://list.orgmode.org/orgmode/87h6
Hi.
When exporting this document the Japanese characters do not appear in
the output.
--8<---cut here---start->8---
#+TITLE: Doc multi-lingual
#+options: author:nil email:nil toc:nil num:nil
#+LATEX_HEADER: \usepackage[french,japanese]{babel}
#+LaTeX_HEADER: \p
23 matches
Mail list logo
