Re: Recent commit causes uncodable character
On Sun, 27 Feb 2022 at 04:02, Thibaut Cuvelier wrote: > On Tue, 22 Feb 2022 at 16:14, Thibaut Cuvelier wrote: > >> On Tue, 22 Feb 2022 at 16:09, Scott Kostyshak wrote: >> >>> On Tue, Feb 22, 2022 at 11:43:23AM +0100, Jürgen Spitzmüller wrote: >>> > Am Di., 22. Feb. 2022 um 10:48 Uhr schrieb Jürgen Spitzmüller < >>> sp...@lyx.org >>> > >: >>> > >>> > > Am Di., 22. Feb. 2022 um 04:55 Uhr schrieb Scott Kostyshak < >>> > > skost...@lyx.org>: >>> > > >>> > >> The attached example file used to compile to PDF a couple of days >>> ago. >>> > >> >>> > > >>> > > Bisect says: >>> > > [0dc7f34e00e06e8b378236e32f86023313067b7c] unicodesymbols: parse >>> > > supplementary lines to encode alternative ways to encode symbols in >>> raw >>> > > LaTeX. >>> > > >>> > >>> > It's probably rather 3f9e21b82692, for that matter. >>> >>> CC'ing Thibaut. >>> >> >> Indeed, it's probably due to a recent commit of mine. I'll have a look, >> tentatively tomorrow. >> > > The problem is that Encodings::read does not read the full unicodesymbols > file, it mysteriously stops at character 0x0390 (which is not even the > first one with multiple LaTeX commands). > I found the root cause: some entries require a \" in LaTeX, but \\" is recognised as the end of the LaTeX command, unlike \\\". It would be helpful to have better error messages in unicodesymbols to debug these cases, but it would be hard to implement in a backward-compatible way. I think the most useful check here would be for an end-of-file symbol, but previous versions of the file format would no longer be recognised (even worse, they would be said to be invalid). But the problem should be solved for now :)! -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Recent commit causes uncodable character
On Tue, 22 Feb 2022 at 16:14, Thibaut Cuvelier wrote: > On Tue, 22 Feb 2022 at 16:09, Scott Kostyshak wrote: > >> On Tue, Feb 22, 2022 at 11:43:23AM +0100, Jürgen Spitzmüller wrote: >> > Am Di., 22. Feb. 2022 um 10:48 Uhr schrieb Jürgen Spitzmüller < >> sp...@lyx.org >> > >: >> > >> > > Am Di., 22. Feb. 2022 um 04:55 Uhr schrieb Scott Kostyshak < >> > > skost...@lyx.org>: >> > > >> > >> The attached example file used to compile to PDF a couple of days >> ago. >> > >> >> > > >> > > Bisect says: >> > > [0dc7f34e00e06e8b378236e32f86023313067b7c] unicodesymbols: parse >> > > supplementary lines to encode alternative ways to encode symbols in >> raw >> > > LaTeX. >> > > >> > >> > It's probably rather 3f9e21b82692, for that matter. >> >> CC'ing Thibaut. >> > > Indeed, it's probably due to a recent commit of mine. I'll have a look, > tentatively tomorrow. > The problem is that Encodings::read does not read the full unicodesymbols file, it mysteriously stops at character 0x0390 (which is not even the first one with multiple LaTeX commands). -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Recent commit causes uncodable character
On Tue, 22 Feb 2022 at 16:09, Scott Kostyshak wrote: > On Tue, Feb 22, 2022 at 11:43:23AM +0100, Jürgen Spitzmüller wrote: > > Am Di., 22. Feb. 2022 um 10:48 Uhr schrieb Jürgen Spitzmüller < > sp...@lyx.org > > >: > > > > > Am Di., 22. Feb. 2022 um 04:55 Uhr schrieb Scott Kostyshak < > > > skost...@lyx.org>: > > > > > >> The attached example file used to compile to PDF a couple of days ago. > > >> > > > > > > Bisect says: > > > [0dc7f34e00e06e8b378236e32f86023313067b7c] unicodesymbols: parse > > > supplementary lines to encode alternative ways to encode symbols in raw > > > LaTeX. > > > > > > > It's probably rather 3f9e21b82692, for that matter. > > CC'ing Thibaut. > Indeed, it's probably due to a recent commit of mine. I'll have a look, tentatively tomorrow. -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Recent commit causes uncodable character
On Tue, Feb 22, 2022 at 11:43:23AM +0100, Jürgen Spitzmüller wrote: > Am Di., 22. Feb. 2022 um 10:48 Uhr schrieb Jürgen Spitzmüller >: > > > Am Di., 22. Feb. 2022 um 04:55 Uhr schrieb Scott Kostyshak < > > skost...@lyx.org>: > > > >> The attached example file used to compile to PDF a couple of days ago. > >> > > > > Bisect says: > > [0dc7f34e00e06e8b378236e32f86023313067b7c] unicodesymbols: parse > > supplementary lines to encode alternative ways to encode symbols in raw > > LaTeX. > > > > It's probably rather 3f9e21b82692, for that matter. CC'ing Thibaut. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Recent commit causes uncodable character
Am Di., 22. Feb. 2022 um 10:48 Uhr schrieb Jürgen Spitzmüller : > Am Di., 22. Feb. 2022 um 04:55 Uhr schrieb Scott Kostyshak < > skost...@lyx.org>: > >> The attached example file used to compile to PDF a couple of days ago. >> > > Bisect says: > [0dc7f34e00e06e8b378236e32f86023313067b7c] unicodesymbols: parse > supplementary lines to encode alternative ways to encode symbols in raw > LaTeX. > It's probably rather 3f9e21b82692, for that matter. Jürgen > > Jürgen > -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Recent commit causes uncodable character
Am Di., 22. Feb. 2022 um 04:55 Uhr schrieb Scott Kostyshak : > The attached example file used to compile to PDF a couple of days ago. > Bisect says: [0dc7f34e00e06e8b378236e32f86023313067b7c] unicodesymbols: parse supplementary lines to encode alternative ways to encode symbols in raw LaTeX. Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Recent commit causes uncodable character
Am Di., 22. Feb. 2022 um 10:40 Uhr schrieb Kornel Benko : > Am Mon, 21 Feb 2022 22:54:55 -0500 > schrieb Scott Kostyshak : > > > The attached example file used to compile to PDF a couple of days ago. > > > > Scott > > Using utf-8 encoding (by setting non-text-fonts) cures it. > Works also if using > Document->Settings...->Language->Encoding->Unicode(utf8) > Sure, then it's no more a character that need to be recoded. Jürgen > > Kornel > -- > lyx-devel mailing list > lyx-devel@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-devel > -- > lyx-devel mailing list > lyx-devel@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-devel > -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Recent commit causes uncodable character
Am Mon, 21 Feb 2022 22:54:55 -0500 schrieb Scott Kostyshak : > The attached example file used to compile to PDF a couple of days ago. > > Scott Using utf-8 encoding (by setting non-text-fonts) cures it. Works also if using Document->Settings...->Language->Encoding->Unicode(utf8) Kornel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel pgpgnBCbIySrP.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Recent commit causes uncodable character
The attached example file used to compile to PDF a couple of days ago. Scott uncodable-dash-example.23.lyx Description: application/lyx signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
