On Thu, Jan 25, 2024 at 12:40:07PM -0500, Richard Kimberly Heck wrote:
That does make me wonder whether there are other versions of this
problem. Are there other cases where we generate files in this way?
I think we will discover that very quickly ;)
--
Enrico
--
lyx-devel mailing list
On 1/25/24 04:29, Enrico Forestieri wrote:
On Thu, Jan 25, 2024 at 09:31:00AM +0100, Enrico Forestieri wrote:
Converting the file to utf-8 encoding everything works fine.
Fixed at 48a065e8
Thanks!
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
On 1/25/24 04:35, José Matos wrote:
On Thu, 2024-01-25 at 09:31 +0100, Enrico Forestieri wrote:
After investigating this I now know why. Capturing the generated
script in a file reveals that it is actually encoded in a 8 bit
encoding on Windows, despite the fact that the first line of the
On Thu, 2024-01-25 at 10:29 +0100, Enrico Forestieri wrote:
> On Thu, Jan 25, 2024 at 09:31:00AM +0100, Enrico Forestieri wrote:
> >
> > Converting the file to utf-8 encoding everything works fine.
>
> Fixed at 48a065e8
>
> --
> Enrico
Thank you. :-)
--
José Abílio
--
lyx-devel mailing list
On Thu, 2024-01-25 at 09:31 +0100, Enrico Forestieri wrote:
> After investigating this I now know why. Capturing the generated
> script in a file reveals that it is actually encoded in a 8 bit
> encoding on Windows, despite the fact that the first line of the
> script says it is encoded in utf-8.
On Thu, Jan 25, 2024 at 09:31:00AM +0100, Enrico Forestieri wrote:
Converting the file to utf-8 encoding everything works fine.
Fixed at 48a065e8
--
Enrico
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Tue, Jan 23, 2024 at 09:15:30PM +0100, Enrico Forestieri wrote:
On Tue, Jan 23, 2024 at 02:58:37PM -0500, Richard Kimberly Heck wrote:
On 1/23/24 14:51, Enrico Forestieri wrote:
On Mon, Jan 22, 2024 at 06:21:42PM -0500, Richard Kimberly Heck wrote:
The conversion script has:
infile =
On Tue, Jan 23, 2024 at 02:58:37PM -0500, Richard Kimberly Heck wrote:
On 1/23/24 14:51, Enrico Forestieri wrote:
On Mon, Jan 22, 2024 at 06:21:42PM -0500, Richard Kimberly Heck wrote:
The conversion script has:
infile = "C:/Users/Thibaut/Desktop/p k .pdf"
when the input file was:
On Mon, Jan 22, 2024 at 06:21:42PM -0500, Richard Kimberly Heck wrote:
The conversion script has:
infile = "C:/Users/Thibaut/Desktop/p k .pdf"
when the input file was: ~\Desktop\píkà.pdf. The accented characters
have been stripped. This is not a surprise, though, since
toFilesystemEncoding
On Mon, Jan 22, 2024 at 06:21:42PM -0500, Richard Kimberly Heck wrote:
On 1/22/24 17:53, Thibaut Cuvelier wrote:
On Mon, 22 Jan 2024 at 23:00, Richard Kimberly Heck
wrote:
On 1/22/24 16:53, didiergab...@free.fr wrote:
I also realize that I can no longer load images whose names
On 1/22/24 17:53, Thibaut Cuvelier wrote:
On Mon, 22 Jan 2024 at 23:00, Richard Kimberly Heck
wrote:
On 1/22/24 16:53, didiergab...@free.fr wrote:
I also realize that I can no longer load images whose names
contain accents. In any case, that’s what’s happening with the
file I
On Mon, 22 Jan 2024 at 23:53, Thibaut Cuvelier wrote:
> On Mon, 22 Jan 2024 at 23:00, Richard Kimberly Heck
> wrote:
>
>> On 1/22/24 16:53, didiergab...@free.fr wrote:
>>
>> I also realize that I can no longer load images whose names contain accents.
>> In any case, that’s what’s happening with
On 1/22/24 16:53, didiergab...@free.fr wrote:
I also realize that I can no longer load images whose names contain
accents. In any case, that’s what’s happening with the file I just
sent you. If I rename the file: SchemaCinematique.pdf to
SchemaCinématique.pdf then I can read “Error converting
13 matches
Mail list logo
