Re: serious Problems with UserGuide on current macOS
On 2017-08-27, mn wrote: > On 27.08.17 22:41, Guenter Milde wrote: The UserGuide currently is a real trouble maker. >> Can you have a look at the used fonts in this document? ... > I experimented with the fonts. LatinModern (the default) gives the same > result as using Libertine or even XeTeX fonts. Fine, so we can rule out fonts as the reason. ... >>> I can confirm strange behavior on macOS 10.12.5 with LyX 2.2.3. >>>1. Launch LyX 2.2.3 >>>2. Open User's Guide from Help Menu >>>3. Render >>> - All pages will be white (no text shown). I do not see >>> beachballing, but the PDF is useless. >> Is there an error message or warning from LaTeX? ... > There are a few warnings but these will likeley not lead anywhere. > The PDF displays fine in Adobe Reader, is in vector and therefore the > bug just has to be in macOS itself. > The question is why it rears its ugly head in Apple's PDFKit? > What makes UserGuide so special? > People have called this document a "Preview-Killer". Joel sent a log file and I see a lot of warnings like: pdfTeX warning: pdflatex (file ./2_Applications_LyX_2_2_3_app_Contents_Resource s_images_buffer-write.pdf): PDF inclusion: multiple pdfs with page group included in a single page OTOH, these warnings are not present in the LaTeX log here on Debian. They seem to be triggered by the SVG icons like (in LyX source): \begin_inset Info type "icon" arg "buffer-new" \end_inset which use an *.svgz image converted to PDF. Maybe the converter called by LyX produces faulty/unsuited PDFs and once they are included, they trigger the problems in viewers that are not sufficiently "robust"? ... > Also note: the downloadable version of the PDF hosted on lyx.org > triggers the same symptoms. It may be generated on a Mac or with the same SVG-converter, too. I could send you a PDF copy of the UserGuide generated here without the above pdfTeX warnings. Günter
Re: serious Problems with UserGuide on current macOS
Dear Joel, thanks for the fast answer. On 2017-08-27, Joel Kulesza wrote: > On Sun, Aug 27, 2017 at 2:41 PM, Guenter Milde wrote: >> On 2017-08-27, Joel Kulesza wrote: >> > On Sat, Aug 26, 2017 at 12:04 PM, mn wrote: >> >> The UserGuide currently is a real trouble maker. >> Can you have a look at the used fonts in this document? > As Mike indicated, all defaults in User's Guide. By "default", you mean "unchanged", right? A look in the log file revealed that the used font is Latin Modern. The manuals changed the font setting to Latin Modern in the 2.3 development cycle. Before there was some preamble code. So I wanted to rule out this change as a reason. (The LyX [Default] does not set up a font and LaTeX selects a Computer Modern substitute (EC or CM-Super).) ... >> I am not sure about "low res", but raster is expected: >> This is the normal behaviour of LyX for ages. See >> http://www.lyx.org/trac/ticket/7334 >> and http://www.lyx.org/trac/ticket/9741. > As a first step in every LyX setup I recommend to >> set Document>Settings>Fonts>Roman to LatinModern in the default template. >> >8. Launch LyX 2.2.3 >> >9. Type "test" >> >10. Render >> > - The text in the PDF is vector. >> Maybe you already changed the font default in this version? > See attached comparisons. Both were generated by creating a new document, > typing test, and rendering. "test_raster" came after rendering the user's > guide. "test_vector" came after quitting both LyX and Preview. Note that > in both screenshots I zoomed in to show the detail. I see, so the difference in the test documents is not about compiling with 2.2 vs. 2.3, right? So we can rule out bitmap fonts. (To be sure, you could check the used fonts in the test files with "File>Properties>Fonts", "Document>Info" or similar.) Thanks, Günter
Re: LyX version 2.3.0 (beta 1)
On Sun, Aug 27, 2017 at 03:23:42AM +0200, Pavel Sanda wrote: > Scott Kostyshak wrote: > > Public release of LyX version 2.3.0beta1 > > Scott, did you put on lyx wiki the release steps you are using when releasing > tarballs? > (If not, can you share it there?) I just updated the wiki with the basic steps I am doing. I will try to keep it updated as I make corrections (as it seems I should in the case of merging strings). https://wiki.lyx.org/Devel/ReleaseProcedure#toc1 I hope to eventually organize all of my notes. I have some that are organized as "only for alpha1", "only for beta1", etc., and other informal things to check (e.g. for pre-releases use a different, scarier, form of ANNOUNCE). > It seems strings were not properly remerged for beta. I think I have a fundamental misunderstanding. I thought that strings were supposed to be remerged before asking translators for translations. Then the translator returns the po file, and the po and the corresponding gmo files are committed. What is the purpose of remerging strings before a release? I was spoiled during 2.2.0 because I think Georg and Uwe took care of all translation-related issues. That ended up being a mistake because I realize that it is important for the release manager to know all parts of the process, so I'm trying to learn. Scott signature.asc Description: PGP signature
Re: serious Problems with UserGuide on current macOS
On Sun, Aug 27, 2017 at 3:53 PM, mn wrote: > On 27.08.17 22:41, Guenter Milde wrote: > > >>> The UserGuide currently is a real trouble maker. > > > > Can you have a look at the used fonts in this document? > > > The fonts used are just the defaults as set by opening the guide from > help menu. > > I experimented with the fonts. LatinModern (the default) gives the same > result as using Libertine or even XeTeX fonts. > > Also note: the downloadable version of the PDF hosted on lyx.org > triggers the same symptoms. > > > >> I can confirm strange behavior on macOS 10.12.5 with LyX 2.2.3. Steps > to > >> reproduce: > > > >>1. Launch LyX 2.2.3 > >>2. Open User's Guide from Help Menu > >>3. Render > >> - All pages will be white (no text shown). I do not see > >> beachballing, but the PDF is useless. > > > > Is there an error message or warning from LaTeX? > > What fonts are used (eventually paste the LaTeX log) > > > There are a few warnings but these will likeley not lead anywhere. > The PDF displays fine in Adobe Reader, is in vector and therefore the > bug just has to be in macOS itself. > > The question is why it rears its ugly head in Apple's PDFKit? > What makes UserGuide so special? > People have called this document a "Preview-Killer". > > >>4. New Document > >>5. Type "test" > >>6. Render > >> - The text in the PDF is not vector, but very low res raster > > > > I am not sure about "low res", but raster is expected: > > This is the normal behaviour of LyX for ages. See > http://www.lyx.org/trac/ticket/7334 > > and http://www.lyx.org/trac/ticket/9741. > > As a first step in every LyX setup I recommend to > > set Document>Settings>Fonts>Roman to LatinModern in the default template. > > > >>8. Launch LyX 2.2.3 > >>9. Type "test" > >>10. Render > >> - The text in the PDF is vector. > > > > Maybe you already changed the font default in this version? > > > > No. > > Just to clarify for those not on macOS or a version <10.12.x: > The text in UserGuide _and_ other PDFs is of course still _all_ in > vector format, as a quick view of the same PDF in Adobe Reader will > confirm. > > But once the bug is triggered – then thereafter – it is indeed in a much > degraded quality that is very pixelated. > That is likely because the OS renders text in an intermediate or lowres > view for scrolling and this representation then stays on screen instead > of the viewer finalizing the hires rendering of the same text. > Mike, Do you want to create a ticket in the tracker on this and then we can continue the discussion there? - Joel
Re: serious Problems with UserGuide on current macOS
On 27.08.17 22:41, Guenter Milde wrote: >>> The UserGuide currently is a real trouble maker. > > Can you have a look at the used fonts in this document? > The fonts used are just the defaults as set by opening the guide from help menu. I experimented with the fonts. LatinModern (the default) gives the same result as using Libertine or even XeTeX fonts. Also note: the downloadable version of the PDF hosted on lyx.org triggers the same symptoms. >> I can confirm strange behavior on macOS 10.12.5 with LyX 2.2.3. Steps to >> reproduce: > >>1. Launch LyX 2.2.3 >>2. Open User's Guide from Help Menu >>3. Render >> - All pages will be white (no text shown). I do not see >> beachballing, but the PDF is useless. > > Is there an error message or warning from LaTeX? > What fonts are used (eventually paste the LaTeX log) > There are a few warnings but these will likeley not lead anywhere. The PDF displays fine in Adobe Reader, is in vector and therefore the bug just has to be in macOS itself. The question is why it rears its ugly head in Apple's PDFKit? What makes UserGuide so special? People have called this document a "Preview-Killer". >>4. New Document >>5. Type "test" >>6. Render >> - The text in the PDF is not vector, but very low res raster > > I am not sure about "low res", but raster is expected: > This is the normal behaviour of LyX for ages. See > http://www.lyx.org/trac/ticket/7334 > and http://www.lyx.org/trac/ticket/9741. > As a first step in every LyX setup I recommend to > set Document>Settings>Fonts>Roman to LatinModern in the default template. > >>8. Launch LyX 2.2.3 >>9. Type "test" >>10. Render >> - The text in the PDF is vector. > > Maybe you already changed the font default in this version? > No. Just to clarify for those not on macOS or a version <10.12.x: The text in UserGuide _and_ other PDFs is of course still _all_ in vector format, as a quick view of the same PDF in Adobe Reader will confirm. But once the bug is triggered – then thereafter – it is indeed in a much degraded quality that is very pixelated. That is likely because the OS renders text in an intermediate or lowres view for scrolling and this representation then stays on screen instead of the viewer finalizing the hires rendering of the same text. greetings Mike
Re: serious Problems with UserGuide on current macOS
On 2017-08-27, Joel Kulesza wrote: > [-- Type: text/plain, Encoding: quoted-printable --] > On Sat, Aug 26, 2017 at 12:04 PM, mn wrote: >> The UserGuide currently is a real trouble maker. Can you have a look at the used fonts in this document? > I can confirm strange behavior on macOS 10.12.5 with LyX 2.2.3. Steps to > reproduce: >1. Launch LyX 2.2.3 >2. Open User's Guide from Help Menu >3. Render > - All pages will be white (no text shown). I do not see > beachballing, but the PDF is useless. Is there an error message or warning from LaTeX? What fonts are used (eventually paste the LaTeX log) >4. New Document >5. Type "test" >6. Render > - The text in the PDF is not vector, but very low res raster I am not sure about "low res", but raster is expected: This is the normal behaviour of LyX for ages. See http://www.lyx.org/trac/ticket/7334 and http://www.lyx.org/trac/ticket/9741. As a first step in every LyX setup I recommend to set Document>Settings>Fonts>Roman to LatinModern in the default template. >8. Launch LyX 2.2.3 >9. Type "test" >10. Render > - The text in the PDF is vector. Maybe you already changed the font default in this version? Günter
Re: serious Problems with UserGuide on current macOS
On Sat, Aug 26, 2017 at 12:04 PM, mn wrote: > The UserGuide currently is a real trouble maker. > > This is likely not the fault of LyX or LaTeX. > > Nevertheless, this is confirmed to happen – not on all but – on the > clear majority of macOS Sierra systems tested. The bug has to lay within > Sierra. > > So at least this is a heads up. > Default PDF export on 10.12.6 opened in default PDF viewer Preview.app > is likely fail. > > greetings > Mike > All, I can confirm strange behavior on macOS 10.12.5 with LyX 2.2.3. Steps to reproduce: 1. Launch LyX 2.2.3 2. Open User's Guide from Help Menu 3. Render - All pages will be white (no text shown). I do not see beachballing, but the PDF is useless. 4. New Document 5. Type "test" 6. Render - The text in the PDF is not vector, but very low res raster 7. Quit LyX & Preview 8. Launch LyX 2.2.3 9. Type "test" 10. Render - The text in the PDF is vector. Regards, Joel
Re: Complaints about LyX on Mac
On Sun, Aug 27, 2017 at 04:09:41PM +0200, Enrico Forestieri wrote: > > I think that it suffices using a QCoreApplication instead of QApplication. No, I was wrong. A QGuiApplication is necessary for using QPixmap. -- Enrico
Re: Complaints about LyX on Mac
On Sun, Aug 27, 2017 at 02:48:14PM +0200, Stephan Witt wrote: > Am 27.08.2017 um 14:35 schrieb Stephan Witt : > > > > Thank you for your ideas… your hint regarding the change for #9778 was > > useful too. I’m not 100% sure how it works now. Before the fix for #9778, no converter was taken into account if the SVG format could be handled directly by Qt. After the fix, a converter for SVG is instead used even if it would not be necessary. So, SVG is directly handled by Qt only when no other converter is found. > > I tried to make your proposal working and it looks not bad. ATM, I see the > > following open tasks: > > 1. It converts SVG but not SVGZ - should be possible to improve > > 2. It should be a console application like tex2lyx > > 3. If bundled with LyX it should considered as a fallback only > > > > I can take care for 2 and 3. For 1 a hint or a solution would be fine. > > Sorry, the problem 1 was my fault. The SVGZ file was not there as I tried > it to convert. If I type the proper file name it works. :-| Fine. I would have been surprised if it didn't work. > So, 2 and 3 are open tasks. I think that it suffices using a QCoreApplication instead of QApplication. It was a 5 mins hack and I didn't pay too much attention to details. -- Enrico
Re: Complaints about LyX on Mac
Am 27.08.2017 um 14:35 schrieb Stephan Witt : > > Am 27.08.2017 um 12:01 schrieb Enrico Forestieri : >> >> On Sat, Aug 26, 2017 at 08:14:57PM +0200, Stephan Witt wrote: >>> >>> ATM, I don’t have a solution for this problem. The inclusion of ImageMagick >>> as part of the LyX bundle doesn’t look attractive. Much work and not a good >>> system design. And definitively not possible for the LyX 2.3.0 release. >> >> I wonder whether a home-made ImageMagick can help. The attached very small >> program converts any image format known to Qt5 to the format specified by >> the extension of the output file. > > Thank you for your ideas… your hint regarding the change for #9778 was useful > too. > I’m not 100% sure how it works now. (I have problems to test all these things, > on my system are so much tools installed - it’s difficult to get a virgin > state). > > After moving all SVG2PNG conversion tools away LyX presents the svgz icons on > screen - I had expected it to fail because of the #9778 change. Is it only a > „trick“ to force external conversion if possible? > > I tried to make your proposal working and it looks not bad. ATM, I see the > following open tasks: > 1. It converts SVG but not SVGZ - should be possible to improve > 2. It should be a console application like tex2lyx > 3. If bundled with LyX it should considered as a fallback only > > I can take care for 2 and 3. For 1 a hint or a solution would be fine. Sorry, the problem 1 was my fault. The SVGZ file was not there as I tried it to convert. If I type the proper file name it works. :-| So, 2 and 3 are open tasks. Stephan.
Re: Complaints about LyX on Mac
Am 27.08.2017 um 12:01 schrieb Enrico Forestieri : > > On Sat, Aug 26, 2017 at 08:14:57PM +0200, Stephan Witt wrote: >> >> ATM, I don’t have a solution for this problem. The inclusion of ImageMagick >> as part of the LyX bundle doesn’t look attractive. Much work and not a good >> system design. And definitively not possible for the LyX 2.3.0 release. > > I wonder whether a home-made ImageMagick can help. The attached very small > program converts any image format known to Qt5 to the format specified by > the extension of the output file. Thank you for your ideas… your hint regarding the change for #9778 was useful too. I’m not 100% sure how it works now. (I have problems to test all these things, on my system are so much tools installed - it’s difficult to get a virgin state). After moving all SVG2PNG conversion tools away LyX presents the svgz icons on screen - I had expected it to fail because of the #9778 change. Is it only a „trick“ to force external conversion if possible? I tried to make your proposal working and it looks not bad. ATM, I see the following open tasks: 1. It converts SVG but not SVGZ - should be possible to improve 2. It should be a console application like tex2lyx 3. If bundled with LyX it should considered as a fallback only I can take care for 2 and 3. For 1 a hint or a solution would be fine. Thanks, Stephan
Re: Change bars module
Jürgen Spitzmüller wrote: > Am Sonntag, den 27.08.2017, 13:20 +0200 schrieb Pavel Sanda: > > Why not. Do you have in mind anything else than just dumping the macro > > definition from the module directly to tex output when showing changes in > > output is enabled? > > No. It's probably trivial. But it's a file format change, and we need to take > care of conversion/reversion. I think too, added to https://www.lyx.org/trac/ticket/10750 so we won't forget. Pavel
Re: Change bars module
Am Sonntag, den 27.08.2017, 13:20 +0200 schrieb Pavel Sanda: > Why not. Do you have in mind anything else than just dumping the > macro definition > from the module directly to tex output when showing changes in output > is enabled? No. It's probably trivial. But it's a file format change, and we need to take care of conversion/reversion. Jürgen > > Pavel signature.asc Description: This is a digitally signed message part
Re: Change bars module
Jürgen Spitzmüller wrote: > > I stumbled upon the change bars module we include in LyX now and find it > > pretty bad UI that we do not include this option as part of normal menu for > > change tracking and hide it somewhere in module listing -- many people will > > miss that. Apparently this module goes back to 2015so we can't just let > > the module disappear, but what about menu item which will just turn on/off > > the module for the docuemnt? > > This strikes me like just another intermediate solution. I would rather > implement the change bars natively for 2.4.0 and keep the module as is for > now (2.3.x). Why not. Do you have in mind anything else than just dumping the macro definition from the module directly to tex output when showing changes in output is enabled? Pavel
Re: Complaints about LyX on Mac
On Sat, Aug 26, 2017 at 08:14:57PM +0200, Stephan Witt wrote:
>
> ATM, I don’t have a solution for this problem. The inclusion of ImageMagick
> as part of the LyX bundle doesn’t look attractive. Much work and not a good
> system design. And definitively not possible for the LyX 2.3.0 release.
I wonder whether a home-made ImageMagick can help. The attached very small
program converts any image format known to Qt5 to the format specified by
the extension of the output file.
--
Enrico
/*
set cflags=`env PKG_CONFIG_PATH=/usr/local/qt5/lib/pkgconfig pkg-config
--cflags Qt5Widgets`
set libs=`env PKG_CONFIG_PATH=/usr/local/qt5/lib/pkgconfig pkg-config --libs
--static Qt5Widgets`
g++ -std=gnu++11 $cflags qsvg2png.cpp -o qsvg2png $libs
*/
#include
#include
int main(int argc, char **argv)
{
if (argc != 3) {
std::cerr << "Usage: " << argv[0]
<< " input.svgz output.png" << std::endl;
return 1;
}
QApplication app(argc, argv);
QPixmap pm;
if (!pm.load(QString::fromLocal8Bit(argv[1]))) {
std::cerr << "Cannot load image " << argv[1] << std::endl;
return 1;
}
if (!pm.save(QString::fromLocal8Bit(argv[2]))) {
std::cerr << "Cannot save converted image to " << argv[2] << std::endl;
return 1;
}
return 0;
}
Re: Change bars module
Am Sonntag, den 27.08.2017, 03:48 +0200 schrieb Pavel Sanda: > Hi, > > I stumbled upon the change bars module we include in LyX now and find > it pretty > bad UI that we do not include this option as part of normal menu for > change > tracking and hide it somewhere in module listing -- many people will > miss that. > Apparently this module goes back to 2015so we can't just let the > module > disappear, but what about menu item which will just turn on/off the > module for > the docuemnt? This strikes me like just another intermediate solution. I would rather implement the change bars natively for 2.4.0 and keep the module as is for now (2.3.x). Jürgen > > Pavel signature.asc Description: This is a digitally signed message part
