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
lyx-d
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
http://lists.lyx.org/mailman/listinfo/
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
script
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 = "C
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: ~\Desktop
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 h
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
cont
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
Am Sonntag, dem 21.01.2024 um 09:53 +0100 schrieb Pavel Sanda:
> It surprised me that TeX -> Tex stylechange passed your muster,
> it's usually me who is on the punk side of things :)
This is a problem in the bib file. The English alpha.bst sentence-cases
titles (the German alphadin.bst doesn't),
On Sat, Jan 20, 2024 at 03:46:21PM +0100, Jürgen Spitzmüller wrote:
> > I tried and must admit that Bibliography 2 in UG looks aesthetically
> > way better with alphadin though.
>
> I think alpha serves the purpose. After all, it is a base style.
It surprised me that TeX -> Tex stylechange passed
Am Freitag, dem 19.01.2024 um 13:55 +0100 schrieb Pavel Sanda:
> On Fri, Jan 19, 2024 at 09:19:56AM +0100, Jürgen Spitzmüller wrote:
> > I suggest to use alpha.bst instead (which is part of base).
> > alphadin is a
> > special German format anyway.
>
> I tried and must admit that Bibliography 2 in
On Fri, Jan 19, 2024 at 09:19:56AM +0100, Jürgen Spitzmüller wrote:
> I suggest to use alpha.bst instead (which is part of base). alphadin is a
> special German format anyway.
I tried and must admit that Bibliography 2 in UG looks aesthetically way
better with alphadin though.
Pavel
--
lyx-devel
Am Do., 18. Jan. 2024 um 23:23 Uhr schrieb Richard Kimberly Heck <
rikih...@gmail.com>:
> Let's drop it.
>
I suggest to use alpha.bst instead (which is part of base). alphadin is a
special German format anyway.
Jürgen
> Riki
>
>
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.l
On Thu, 2024-01-18 at 23:30 +0100, Pavel Sanda wrote:
> I am completely fine if you want to ditch that.
>
> Pavel
I agree.
--
José Abílio
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Thu, Jan 18, 2024 at 08:58:59PM +0100, Jürgen Spitzmüller wrote:
> Anyway, even if it wouldn't, I'd rather use a standard style before
> shipping our own bst just for the sake of exemplifying in docs.
I am completely fine if you want to ditch that.
Pavel
--
lyx-devel mailing list
lyx-devel@li
On 1/18/24 14:58, Jürgen Spitzmüller wrote:
Am Donnerstag, dem 18.01.2024 um 20:22 +0100 schrieb Pavel Sanda:
Actually I am not sure it's part of TL proper, it's packaged here in
texlive-bibtex-extra package. Anyway Uwe put it in tree very long
time ago when TL/Miktex distributions would be very
Am Donnerstag, dem 18.01.2024 um 20:22 +0100 schrieb Pavel Sanda:
> Actually I am not sure it's part of TL proper, it's packaged here in
> texlive-bibtex-extra package. Anyway Uwe put it in tree very long
> time ago when TL/Miktex distributions would be very different.
CTAN says it's part of TeXLi
On Thu, Jan 18, 2024 at 05:48:07PM +0100, Jürgen Spitzmüller wrote:
> Am Donnerstag, dem 18.01.2024 um 14:15 +0100 schrieb Pavel Sanda:
> > 1) Debian sid gives small warning about alphadin.bst having non-utf chars.
> > It's
> > exactly one accented char in comment which I was about to fix, but
Am Donnerstag, dem 18.01.2024 um 17:47 +0100 schrieb Pavel Sanda:
> > So we're not displaying the used style when it's read-only?
>
> Looks like that. P
Strange, but also in 2.3 AFAICS, so no regression.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/l
Am Donnerstag, dem 18.01.2024 um 14:15 +0100 schrieb Pavel Sanda:
> 1) Debian sid gives small warning about alphadin.bst having non-utf
> chars. It's
> exactly one accented char in comment which I was about to fix, but
> then I saw
> that we ship alphadin.bst from 1999, while my TL 2020 cont
On Thu, Jan 18, 2024 at 11:04:16AM -0500, Richard Kimberly Heck wrote:
> On 1/18/24 08:15, Pavel Sanda wrote:
> >2) Open User Guide. Click on bilbiography at the bottom of the document.
> >Style field is empty.
> >Now disable read-only status of the UG via Document menu and do the same
> >
On 1/18/24 08:15, Pavel Sanda wrote:
2) Open User Guide. Click on bilbiography at the bottom of the document.
Style field is empty.
Now disable read-only status of the UG via Document menu and do the same as
above.
Style field suddenly becomes "biblio/alphadin" (which is correct).
On Thu, Jan 11, 2024 at 11:14:01AM -0500, Richard Kimberly Heck wrote:
> Please build binaries.
We forget to kill few remnants of QT4:
- INSTALL.cmake: Kornel can you update what you know there? Perhaps adding some
Qt6 related nught help as well?
- INSTALL.MacOSX: Stephan could you have look wha
On Thu, Jan 11, 2024 at 11:14:01AM -0500, Richard Kimberly Heck wrote:
> Please build binaries.
1) Debian sid gives small warning about alphadin.bst having non-utf chars. It's
exactly one accented char in comment which I was about to fix, but then I
saw
that we ship alphadin.bst from 1999,
Am Do., 11. Jan. 2024 um 17:14 Uhr schrieb Richard Kimberly Heck:
> Here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please build binaries.
>
Done for Windows, uploaded as usual.
--
Eugene
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Thu, 2024-01-11 at 11:14 -0500, Richard Kimberly Heck wrote:
> Here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please build binaries.
>
> Riki
Built for Centos-stream+epel-next 8; Centos-stream+epel-next 9; Centos-
stream 8; Centos-stream 9; Epel 8; Epel 9; Fedora 38; Fedora 39; Fedo
On 1/11/24 17:37, Jean-Marc Lasgouttes wrote:
Le 11/01/2024 à 23:13, Richard Kimberly Heck a écrit :
Is it intentional that there is extra padding at the top of math
displays in this version of LyX? 2.3.7 on the left, 2.4.0rc1 on the
right:
No, that is not intentional, and I see it, too. Than
Le 11/01/2024 à 23:13, Richard Kimberly Heck a écrit :
Is it intentional that there is extra padding at the top of math
displays in this version of LyX? 2.3.7 on the left, 2.4.0rc1 on the right:
No, that is not intentional, and I see it, too. Thanks for the report.
We'll track it down.
As yo
On 1/11/24 13:23, Alexander Dunlap wrote:
On Thu, Jan 11, 2024, at 11:14 AM, Richard Kimberly Heck wrote:
Here:
http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
Please build binaries.
Riki
Is it intentional that there is extra padding at the top of math
displays in this version of LyX? 2.3.7 on t
I see one for ARM, would a universal one be forthcoming?
I have a mixed setup and am salivating :-)-O
el
On 2024-01-11 18:14, Richard Kimberly Heck wrote:
> Here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please build binaries.
>
> Riki
>
>
--
To email me replace 'nospam' with 'el
On Thu, Jan 11, 2024, at 1:45 PM, Jean-Marc Lasgouttes wrote:
> Le 11/01/2024 à 19:23, Alexander Dunlap a écrit :
> > Is it intentional that there is extra padding at the top of math
> > displays in this version of LyX? 2.3.7 on the left, 2.4.0rc1 on the right:
>
> Yes, this is the spacing that h
Le 11/01/2024 à 19:23, Alexander Dunlap a écrit :
Is it intentional that there is extra padding at the top of math
displays in this version of LyX? 2.3.7 on the left, 2.4.0rc1 on the right:
Yes, this is the spacing that happens when a math inset is at the start
of a paragraph. Actually, it is
On Thu, Jan 11, 2024, at 11:14 AM, Richard Kimberly Heck wrote:
> Here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please build binaries.
>
> Riki
Is it intentional that there is extra padding at the top of math displays in
this version of LyX? 2.3.7 on the left, 2.4.0rc1 on the right:
Le 11/01/2024 à 17:34, Pavel Sanda a écrit :
On Thu, Jan 11, 2024 at 11:14:01AM -0500, Richard Kimberly Heck wrote:
Please build binaries.
Compiles and runs on oldstable debian. P
Same on Debian stable.
I just commited on master an update of French Intro.lyx, I hope it was possible
to do s
On Thu, Jan 11, 2024 at 11:14:01AM -0500, Richard Kimberly Heck wrote:
> Please build binaries.
Compiles and runs on oldstable debian. P
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Le 13/09/2017 à 11:44, Stephan Witt a écrit :
Because the converter machine uses external tools to create the image files in
an appropriate format for export?
For the on-screen rendering LyX uses it’s Qt-pixmap converters.
Excellent point. So in the longer term, we could also make the built-i
Am 13.09.2017 um 11:17 schrieb Jean-Marc Lasgouttes :
>
> Le 13/09/2017 à 02:10, Stephan Witt a écrit :
>>> (And, if I remember right, converting to a bitmap is also supported by QT.)
>> Yes, that’s the way I’m trying to go. A small utility based on Qt to convert
>> SVG (or SVGZ) to PNG (or JPEG)
Le 13/09/2017 à 02:10, Stephan Witt a écrit :
(And, if I remember right, converting to a bitmap is also supported by QT.)
Yes, that’s the way I’m trying to go. A small utility based on Qt to convert
SVG (or SVGZ) to PNG (or JPEG).
There is something that may have been stated but that I misse
Am 12.09.2017 um 09:19 schrieb Guenter Milde :
>
> On 14.08.17, Stephan Witt wrote:
>> Am 14.08.2017 um 14:46 schrieb Guenter Milde :
>>> On 2017-08-14, Stephan Witt wrote:
Am 14.08.2017 um 09:43 schrieb Jean-Pierre Chrétien
:
>>>
>
> 1) opening splash.lyx, gets a message
>>>
>>>
On 12.04.2014 09:29, Murat Yildizoglu wrote:
More tests :
Close LyX, Re open it. Reopen the document.
Add a new table
Merge the heading rows
fill the table
let autosave -> no problem
add a new line
copy another line on it
let the autosave> no problem.
So, I have difficulty to locate the factor
On 04/12/2014 03:29 AM, Murat Yildizoglu wrote:
More tests :
Close LyX, Re open it. Reopen the document.
Add a new table
Merge the heading rows
fill the table
let autosave -> no problem
add a new line
copy another line on it
let the autosave> no problem.
So, I have difficulty to locate the fact
More tests :
Close LyX, Re open it. Reopen the document.
Add a new table
Merge the heading rows
fill the table
let autosave -> no problem
add a new line
copy another line on it
let the autosave> no problem.
So, I have difficulty to locate the factor that triggers this hanging.
Sorry for not bei
More test:
I have merged two cells, waited fro the autobackup, no problem
I have added a new line and copied an old line on it, no problem either.
The auto-bacup takes place.
Vincent van Ravesteijn
11 avril 2014
12:58
Do you remember
that you used the move column/row fe
I have difficulty to
provoke the bug, as you can see. It seems to happen after having done a
specific modification in the document.
The tables are correctly saved, only the stuff added after having
inserted the tables are lost when this happens.
Jürgen Spitzmüller a écrit:
2014-04-11 12:21
Vincent van Ravesteijn a écrit:
Do you remember that you used the move column/row feature?
I am not completely sure, but I do not think that I have used it.
If I remember correctly, I have just copied some lines over others.
I could maybe try to check it and tell you: I have moved a
2014-04-11 12:21 GMT+02:00 Murat Yildizoglu :
> Well to test, I have
> - saved my file
> - moved a table between single-multiple columns areas
> - continued to work hoping to trigger and autosave
>
> but have not observed the crash yet.
>
If it is indeed a loop, it might be helpful if you could t
Do you remember that you used the move column/row feature?
If we do not set the mutlicol properties correctly, we might for loop over
a columns but never find the end Or something like that.
Vincent
On Fri, Apr 11, 2014 at 11:56 AM, Vincent van Ravesteijn wrote:
>
>
> On Fri, Apr 11, 2014 at 11:49 AM, Murat Yildizoglu wrote:
>>
>> Before the crash I have indeed moved some tables in the document between a
>> sigle column and a double column areas.
>> But it has not crashed immediately. I have
Well to test, I have
- saved my file
- moved a table between single-multiple columns areas
- continued to work hoping to trigger and autosave
but have not observed the crash yet.
Vincent van Ravesteijn
11 avril 2014
11:56
Before the crash I have
indeed moved some tables
11/04/2014 12:09, Murat Yildizoglu:
Ok, be careful, if it crashes when you save it, you're sort of losing
text.
Further:
-- the example that Uwe added to the bug report was also a table using
multi-columns
When I had this crash first, I was not using at all the multi-column
module in this docume
Vincent van Ravesteijn
11 avril 2014
11:56
Before the crash I have
indeed moved some tables in the document between a sigle column and a
double column areas.
But it has not crashed immediately. I have started to write some
supplementary text, and I have the impression t
On Fri, Apr 11, 2014 at 11:49 AM, Murat Yildizoglu wrote:
> Before the crash I have indeed moved some tables in the document between a
> sigle column and a double column areas.
> But it has not crashed immediately. I have started to write some
> supplementary text, and I have the impression that
Before the crash I have
indeed moved some tables in the document between a sigle column and a
double column areas.
But it has not crashed immediately. I have started to write some
supplementary text, and I have the impression that it crashed either
during an automatic save or when I clicked CMD
On Fri, Apr 11, 2014 at 11:43 AM, Murat Yildizoglu wrote:
> Sorry Stephen, there is no recent file in this folder, only some old
> reports for Skype and other softs.
> I had to kill LyX each time, after having waited some time. Maybe the
> report has not been written?
> Can it be written somewher
On Fri, Apr 11, 2014 at 11:39 AM, Stephan Witt wrote:
> Am 11.04.2014 um 11:27 schrieb Murat Yildizoglu :
>
>> Hi,
>>
>> I am testing the RC1. I am working on a simple document, but Lyx seems to
>> crash randomly, and to cause a panic in my processors.
>> I have been able to observe this crash on
Sorry Stephen, there is no
recent file in this folder, only some old reports for Skype and other
softs.
I had to kill LyX each time, after having waited some time. Maybe the
report has not been written?
Can it be written somewhere else?
I cannot see anything relevant in the system Library/Logs
Am 11.04.2014 um 11:27 schrieb Murat Yildizoglu :
> Hi,
>
> I am testing the RC1. I am working on a simple document, but Lyx seems to
> crash randomly, and to cause a panic in my processors.
> I have been able to observe this crash once after having launched LyX from
> the terminal, but there
Sorry,
I have sent to you a backup instead of the emergency file :-(
Murat Yildizoglu
11 avril 2014
11:27
Hi,
I am testing the RC1. I am working on a simple document, but Lyx seems
to crash randomly, and to cause a panic in my processors.
I have been able to observe
Neal Becker wrote:
On Monday 04 August 2008, Abdelrazak Younes wrote:
Neal Becker wrote:
I see a number of characters in inverse video, for no apparant reason.
Do you have a system with CJK input method enabled?
Abdel.
Dunno. I'm not _using_ any special input method
> No, my own doc.
This is a LaTeX problem, so not LyX's fault. But you can send me a SMALL version of the file and i
could have a look what is wrong.
regards Uwe
Uwe Stöhr wrote:
> What document is this, one of the LyX docs?
>
No, my own doc.
What document is this, one of the LyX docs?
regards Uwe
On Monday 04 August 2008, Abdelrazak Younes wrote:
> Neal Becker wrote:
> > I see a number of characters in inverse video, for no apparant reason.
>
> Do you have a system with CJK input method enabled?
>
> Abdel.
Dunno. I'm not _using_ any special input method.
Neal Becker wrote:
I see a number of characters in inverse video, for no apparant reason.
Do you have a system with CJK input method enabled?
Abdel.
Neal Becker wrote:
> And they are somewhat random. I redisplayed that window and now the UW is
> not show with inverse video, but now some other character elsewhere is.
have never seen something like this.
you can try to put some example file doing this to bugzilla,
but i guess it would be hard
Neal Becker wrote:
> Pavel Sanda wrote:
>
>> Neal Becker wrote:
>>> I see a number of characters in inverse video, for no apparant reason.
>>
>> could you provide some screenshot?
>>
>> pavel
And they are somewhat random. I redisplayed that window and now the UW is not
show with inverse vide
Neal Becker wrote:
> I see a number of characters in inverse video, for no apparant reason.
could you provide some screenshot?
pavel
71 matches
Mail list logo