Answer inline
On Wed, 2 Apr 2025 at 20:20, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > Actually, what I would do after looking around is
> > * short term (even as a bug fix in 9.7): modifying the error message and
> > say that unsupported Unicode characters can only be d
Pedro Andres Aranda Gutierrez writes:
>> I doubt that it will be a trivial enough fix for bugfix branch, but I
>> agree that such message (or warning) would be nice to have.
>>
>
> What about
> ("^!.+Unicode character" . "[unicode character(s) not supported by
> pdflatex. Set org-latex-compil
Pedro Andres Aranda Gutierrez writes:
> Actually, what I would do after looking around is
> * short term (even as a bug fix in 9.7): modifying the error message and
> say that unsupported Unicode characters can only be dealt with in XETEX or
> LUALATEX.
I doubt that it will be a trivial enough f
Hi again
Actually, what I would do after looking around is
* short term (even as a bug fix in 9.7): modifying the error message and
say that unsupported Unicode characters can only be dealt with in XETEX or
LUALATEX.
* Long term as a new feature in 9.8: introducing two custom variables, one
to enab
Pedro Andres Aranda Gutierrez writes:
>> My main idea is making export work "by default" for more users.
>> Without having to set defcustoms. So, I'd prefer detecting non-ascii to
>> be done, if possible.
>
> I would at least give control over generating or not any header and then
> hard-code a r
