Hi Maxim,
I think the problem is not the fact that I may be inclined towards book
typesetting but that TeX itself and its workflow is inclined towards
book typesetting. This fact is something that must be taken into account
and that many LaTeX users sometimes forget. The concept of a 'fallback
On 17/07/2021 01:34, Juan Manuel Macías wrote:
Maxim Nikulin writes:
I think that low level implementation in browser or in some underlying
library is much faster
LM Roman 12
abc абв…с
LM Roman 12, CMU Serif
abc абв…с
They are two different scenarios:
Maxim Nikulin writes:
> I think that low level implementation in browser or in some underlying
> library is much faster
>
>
> LM Roman 12
> abc абв…с
> LM Roman 12, CMU Serif
> abc абв…с
>
They are two different scenarios: web publishing and book typesetting
On 16/07/2021 02:40, Juan Manuel Macías wrote:
Maxim Nikulin writes:
In CSS it is possible to specify a list of fonts and a glyph is taken
from the first font where it is present. Despite particular fonts have
limited coverage, I see wide range of Unicode characters on web pages,
that is why I
Jean-Christophe Helary writes:
> Since org uses Latex to achieve export to PDF, which is quite a
> common demand nowadays, something that normal org users can
> understand should be posted somewhere.
I second that! I just wanted to try to lower the expectation that
(most) scripts will work out
> On Jul 16, 2021, at 18:20, Stefan Nobis wrote:
>
> The last glyph ("TELEPHONE RECEIVER") is not visible for me. Remember,
> that Unicode gets expanded quite often and it is not easy for font
> developers to keep up. I still think that the expectation, that Org
> and/or LaTeX will support
Maxim Nikulin writes:
> Do Unicode TeX engines support such combination of fonts?
Yes, they do.
My rather long response was due to my impression that you are quite
surprised that not everything is supported with the default
configuration as you expected.
I wanted to highlight that it is even
> On Jul 15, 2021, at 4:05, Stefan Nobis wrote:
>
>> Is it possible to provide reasonable defaults for fonts?
>
> I do not think so. You want Cyrillic. But what about Japanese,
> Chinese, Devanagari, Tamil, Arabic etc? I doubt that there exists a
> single font that supports all these scripts
Maxim Nikulin writes:
> In CSS it is possible to specify a list of fonts and a glyph is taken
> from the first font where it is present. Despite particular fonts have
> limited coverage, I see wide range of Unicode characters on web pages,
> that is why I am almost sure that system font
On 15/07/2021 02:05, Stefan Nobis wrote:
Maxim Nikulin writes:
There are cm-super fonts for at least of 15 years.
There are many tradeoffs in many aspects. No single font pleases
everyone. So you want to say: Your requirements are more
important/common/stylish/whatever that the requirements
Tim Cross writes:
> Stefan Nobis writes:
>> But maybe we could assemble a list of good (enough) fonts for
>> different languages/scripts and provide a default setup in Org for
>> LaTeX export, that sets a proper font for the chosen document
>> language?
> I think such a list would be a really
Stefan Nobis writes:
> Maybe. I'm currently myself struggling a little bit with a flexible
> configuration, that can be used with many different kind of documents
> (short notes, larger reports, beamer presentations) and provides all
> the extras I like to use. There is no clear best package
Maxim Nikulin writes:
> It perfectly suits for e.g. a book when camera ready variant is
> required. For routine notes it is better to keep from defaults as
> minimal as possible to minimize problems that may arise a decade
> later. I would prefer to avoid Linux Libertine if I am going to send
>
Maxim Nikulin writes:
> There are cm-super fonts for at least of 15 years.
There are many tradeoffs in many aspects. No single font pleases
everyone. So you want to say: Your requirements are more
important/common/stylish/whatever that the requirements of other
people?
I do need only latin
On 14/07/2021 13:44, Stefan Nobis wrote:
The main point: utf8x and the associated package ucs are not
maintained for quite some time (utf8x seems to be last changed in
2004) and as far as I understand have always been more of a workaround
than a solution. But I'm not an expert in this regard.
Maxim Nikulin writes:
[utf8x]
> Maybe, I have seen such warnings. However I have tested neither utf8
> nor utf8x on real examples. That is why I am unaware what can be
> broken in particular. For small examples with various symbols
> outside of ASCII, utf8x may give better support.
The main
Hi Maxim,
Maxim Nikulin writes:
> I do not know if new engines allows to get list of available fonts and
> to choose a set of fonts with better coverage than lmodern.
LuaTeX and XeTeX use harfbuzz as OpenType rendering engine. On
LuaLaTeX and XeLaTeX you must use the fontspec package
On 10/07/2021 23:44, Stefan Nobis wrote:
Maxim Nikulin writes:
(add-to-list 'org-latex-inputenc-alist '("utf8" . "utf8x"))
so I am unaware whether \usepackage[utf8x]{inputenc} has any drawbacks.
Do not do this. Both, utf8x and ucs, are obsolete and deprecated for
quite some time.
Maybe, I
On Monday, 12 Jul 2021 at 13:09, Tim Cross wrote:
> I also use a couple of templates via either company or yasnipet which
> I use for some org documents which have a 'standard' outline and
> header setup.
The autoinsert package (built-in) is quite useful here as well. I have
a skeleton org file
Juan Manuel Macías writes:
> Tim Cross writes:
>
>> Just FYI for those who don't know, you can use the org-latex-classes
>> variable to define your own pseudo document classes, possibly using the
>> DEFAULT_PACKAGES, PACKAGES, EXTRA_PACKAGES macros and other latex
>> settings. So for example,
Hi Jonathan,
Jonathan McHugh writes:
> I recall there was momentum re exporting to Context from Orgmode, hopefully a
> solid implementation is available.
It seems that a member of this mailing list, Jason Ross, is working on a
ConTeXt backend for org:
Hi Jean-Christophe,
I have heard positive things with regards to the document management system,
Context, for handling non Latin characters.
It may be worth considering as an alternative to Latex.
I recall there was momentum re exporting to Context from Orgmode, hopefully a
solid
Tim Cross writes:
> Just FYI for those who don't know, you can use the org-latex-classes
> variable to define your own pseudo document classes, possibly using the
> DEFAULT_PACKAGES, PACKAGES, EXTRA_PACKAGES macros and other latex
> settings. So for example, you can add the babel or other
Maxim Nikulin writes:
> (add-to-list 'org-latex-inputenc-alist '("utf8" . "utf8x"))
Do not do this. Both, utf8x and ucs, are obsolete and deprecated for
quite some time.
For proper unicode support, switch from pdflatex to lualatex or
xelatex. With these newer backends (and proper adjustments
On 10/07/2021 20:52, Juan Manuel Macías wrote:
I agree with you that Org should have multilingual support. A few months
ago I started this thread here, with some proposals:
https://orgmode.org/list/87o8d95pvo@posteo.net/
I tried to draw more attention to support of locale-aware formatting
Juan Manuel Macías writes:
> Hi Jean-Christophe,
>
> Jean-Christophe Helary writes:
>
>> I had given up on Latex because mixing languages sounded like a huge
>> pain in the butt but I see that without some org-level infrastructure
>> it is not possible to achieve much when exporting to
> On Jul 10, 2021, at 23:38, Juan Manuel Macías wrote:
>
> Hi Jean-Christophe,
>
> Jean-Christophe Helary writes:
>
>> I had given up on Latex because mixing languages sounded like a huge
>> pain in the butt but I see that without some org-level infrastructure
>> it is not possible to
Hi Jean-Christophe,
Jean-Christophe Helary writes:
> I had given up on Latex because mixing languages sounded like a huge
> pain in the butt but I see that without some org-level infrastructure
> it is not possible to achieve much when exporting to Latex/PDF (unless
> I missed something).
Well,
> On Jul 10, 2021, at 22:52, Juan Manuel Macías wrote:
>
> Hi Jean-Christophe,
>
> Jean-Christophe Helary writes:
>
>> I guess it is an issue with the Latex backend and could have been solved
>> with the proper Latex settings, but it seems weird that the default settings
>> do not allow
Hi Jean-Christophe,
Jean-Christophe Helary writes:
> I guess it is an issue with the Latex backend and could have been solved with
> the proper Latex settings, but it seems weird that the default settings do
> not allow for out-of-the-box multilingual support.
I agree with you that Org should
I was busy last year going back to school and I wrote a research paper for my
first year of master almost entirely in org-mode.
My workflow was trivial:
- write in org-mode
- enter the bibliography with Zotero
- export to ODT and open in NeoOffice
- modify in NeoOffice
- deliver
At first, I
31 matches
Mail list logo
