Dear Maintainer,

with the file
/home/user/f/1.lyx

LyX works fine, but if i rename the dir to cyrillic:

/home/user/ф/1.lyx

LyX becomes incapable to produce pdf output,
it generates error messages with
"missing \begin{document}".

Linux tp 5.3.0-3-amd64 #1 SMP Debian 5.3.15-1 (2019-12-07) x86_64 GNU/Linux


LyX 2.3.3 (2019-06-10)
Configuration
   Host type:               x86_64-pc-linux-gnu
   Special build flags:      build=release std-regex warnings use-enchant
   Bundled libraries:       (none)
   C++ Compiler:            g++ (9)
   C++ Compiler flags:       -Wall -Wextra -fPIC -O2 -std=c++14
   C++ Compiler user flags:  -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14
-g -O2
-fdebug-prefix-map=/build/lyx-hqFnMe/lyx-2.3.3=. -fstack-protector-strong -
Wformat -Werror=format-security -fPIC
   Linker flags:
   Linker user flags:       -Wl,-z,defs -Wl,--as-needed -Wl,-z,relro
-Wl,-z,now
   Qt Frontend:
       Qt version:	   5.12.5
   Packaging:               posix
   LyX binary dir:          /usr/bin
   LyX files dir:           /usr/share/lyx

Dear Maintainer,
this bug is still actual in lyx (version 2.3.3-3) in debian unstable

I'm facing the same problem on Debian 10 Buster with lyx 2.3.2 and
french accented characters :

- if the file path contains french accented characters, export to PDF
(pdflatex) fails with :

**********

Error message ------------------------ Package inputenc Error: Invalid
UTF-8 byte sequence Latex Error: MIssing \begin{document}. Package
inputenc Error: Invalid UTF-8 byte sequence.

Description --------------------

The document does not appear to be in UTF-8 encoding.

Try adding \UseRawInputEncoding as the first line of the file

or specify an encoding such as \usepackage [latin1]{inputenc}

in the document preamble.

Alternatively, save the file in UTF-8 using your editor or another tool

**********

The 3 above proposed solutions don't work.

The problem does not appear with every document classes, only with some
of them like all koma-script classes, while there's no problem with all
Standard classes.

I'm not sure this bug stays in lyx package, maybe in some texlive
package like texlive-binaries, but I don't know enough about LaTeX to be
sure...

Thanks for caring about that bug.

I've just stumbled over this after an upgrade to buster, and can provide
an additional datum that can also be used as a workaround:

While direct export to PDF via pdflatex is broken, the resulting TeX
file is fine. That means that you can export the LyX file to LaTeX
(pdflatex), and then from the command line invoke pdflatex on the file
to obtain a PDF.

(And to no surprise, it also affects german Umlauts).

Kind regards
chrysn

Can you give it a try in unstable?

The lyx bug in question is here:
https://www.lyx.org/trac/ticket/11146

Note however that some folks still report problems so we need more
feedback on this:
https://www.lyx.org/trac/ticket/11940


Note that in this bug underlying LaTeX version matters, so please
report it together with lyx version.

Thanks,
Pavel

Can you give it a try in unstable?

The lyx bug in question is here:
https://www.lyx.org/trac/ticket/11146

Note however that some folks still report problems so we need more
feedback on this:
https://www.lyx.org/trac/ticket/11940


Note that in this bug underlying LaTeX version matters, so please
report it together with lyx version.

Thanks,
Pavel

notfound 935814 2.3.6-1
thanks

Works for me with unstable, tested with German umlauts.

Thanks for the update
Christian

Reading up on the linked "some folks still report" issue, I've repeated
the test with the Emoji character representing the German test word (not
repeated here for propriety; any emoji would do as they're all outside
the BMP).

Running the preview or export to pdf through pdflatex gave a warning:

(which only got fully readable when copy-pasted out; the symbol I tried
to avoid on screen looks like an empty rectangle), but still ran trough
correctly (ie. is not affected by the bug in question).

BR
Christian

Closing, 2.3.6-1 with the fix is in the archive.