On 2016-01-09, Scott Kostyshak wrote: > I have gone through this thread and tried to make a summary of the questions > and discussion for Uwe. Please add more questions if you have any or edit my > misinterpretation of the question/comment.
> The following letters refer to the person that asked the question. > G=Georg > R=Richard > S=Scott > S1. Would it be reasonable to build beta1 installers with both Qt 5.5.1 > and 5.6.0beta1? > S2. Can you make the installers from *only* the tar ball (and not use the > git directory at all)? Note that if there is a technical reason why this is > difficult if you ask on the list I am guessing someone can help. > S3. Richard has been committing updates to po files. Can you confirm that all > translation updates we have received have been merged? Has anyone emailed > updates to you privately? > R4. Do we also want to try releasing an installer built with mingw? > (G response: IMO, we only need to release one installer. The mingw and MSVC > builds behave exactly the same (modulo bugs). So the question is rather > whether > we do trust MSVC or mingw, and who does the build: If it is Uwe, it will be > MSVC, otherwise it will probably be mingw. > G5. Not a question but a prerequisite IMHO: The 2.2.0 release should also > build > the prerequisite from the sources Peter added, using exactly the same > compiler as is used to build LyX. > S6. Can you still reproduce these two tickets? > http://www.lyx.org/trac/ticket/9892 > http://www.lyx.org/trac/ticket/9900 > If so, do you think they are beta blockers? > That is part of the reason why I am curious about Qt 5.6.0beta1 (see question > S1). Maybe it makes those issues go away somehow. GM1: could we add a line \@ifpackageloaded{fontspec}{\unaccentedoperators}{} to the user-preamble of doc/es/UserGuide.lyx? This would work around a bug in babel-spanish preventing compilation with non-TeX fonts without affecting the default pdflatex output. GM2: may we define alternative "non-TeX fonts" in the manuals containing characters missing in the default LatinModern Unicode fonts? Again, this would help compilation with non-TeX fonts without affecting the default output. Günter
