Re: [PATCH] microtype

[Pavel Sanda]

Pavel Sanda wrote:
> PhilipPirrip wrote:
> > Even Fonts section should be OK, as this makes use and/or changes features 
> > of individual glyphs and whole fonts.
> 
> Yes, my life would be easier then. But no hard opinion on the issue.

I let it in fonts, but no opposition in case others want to
push it into layout.

Pavel

Require C++11 for 2.3?

[Scott Kostyshak]

Dear all,

Are we going to require C++11 starting with LyX 2.3.0? From what I
understand, this will make several things easier.

Scott


signature.asc
Description: PGP signature

One official build system?

[Scott Kostyshak]

Dear all,

The following email thread (3 years ago) suggests that we would like to
move to one official build system in the long-run across all platforms,
but that there were barriers to using CMake:
http://marc.info/?i=kmrd28$e1k$1%20()%20ger%20!%20gmane%20!%20org

Have those issues been resolved?

Is the opinion among currently active LyX developers also that we would
like to move to CMake as the official build system?

Is CMake currently used for our official builds on Mac and Win?

I don't know much about build systems and I don't have a strong opinion
on this. I just start this conversation now because of:

(1) the recent discussion about making the release process easier/faster
(2) it seems like a conversation that should be had at the beginning of
a major release cycle

From what I understand, most developers on Linux use autotools. I can't
tell if this is because that is what most developers have experience
with or if it is because autotools has other advantages.

Scott


signature.asc
Description: PGP signature

Re: Tarballs for LyX 2.2.0 are on FTP

[Scott Kostyshak]

On Tue, May 31, 2016 at 10:26:57PM +0200, Georg Baum wrote:
> Guillaume Munch wrote:

> - Have a build server that does automatic builds on a regular basis for all 
> three platforms (Linux, OS X, windows) and makes binary packages and build 
> logs available.

This would be a great way to get feedback from users early so we could
be confident there are not regressions. This could also reduce the time
between e.g. alpha and beta. It seems that there are often a lot of bugs
reported by Windows and Mac users for alpha. It would also be a way for
many LyX users to get involved and help. Here is a recent article
detailing additional benefits:
https://www.chevrel.org/carnet/?post/2016/05/19/Let-s-give-Firefox-Nightly-some-love

Scott


signature.asc
Description: PGP signature

Re: A tiny cedilla anomaly

[Scott Kostyshak]

On Tue, May 03, 2016 at 02:47:43PM +0100, Guillaume Munch wrote:
> Le 03/05/2016 06:09, Stephan Witt a écrit :
> > Am 03.05.2016 um 03:04 schrieb Guillaume Munch :
> > > 
> > > Le 03/05/2016 01:40, Scott Kostyshak a écrit :
> > > > On Sun, May 01, 2016 at 08:38:58AM +0200, Stephan Witt wrote:
> > > > > Am 01.05.2016 um 04:06 schrieb Scott Kostyshak :
> > > > > > 
> > > > > > On Sun, May 01, 2016 at 01:28:56PM +1200, Andrew Parsloe wrote:
> > > > > > > On 1/05/2016 11:33 a.m., Jean-Marc Lasgouttes wrote:
> > > > > > > > Le 27/04/2016 03:22, Andrew Parsloe a écrit :
> > > > > > > > > Having just skimmed through an article on Wikipedia about 
> > > > > > > > > cedillas, I
> > > > > > > > > gather a cedilla is never attached to the letter 'i'. 
> > > > > > > > > Nonetheless, when
> > > > > > > > > I do attach one (using european.kmap,  then ',' followed by 
> > > > > > > > > 'i'),
> > > > > > > > > everything looks fine in the main LyX window but in the 
> > > > > > > > > Source Pane, LyX
> > > > > > > > > format, the cedilla gets attached to the following letter. 
> > > > > > > > > For instance,
> > > > > > > > > writing'aei̧ou' with a cedilla under the 'i', all is fine in 
> > > > > > > > > the main LyX
> > > > > > > > > window (and the pdf) but when viewed in the Source Pane, the 
> > > > > > > > > cedilla is
> > > > > > > > > located under the 'o'. A quick experiment suggests 'i' is the 
> > > > > > > > > only
> > > > > > > > > letter for which this happens. It doesn't happen in 2.1.4 so 
> > > > > > > > > it appears
> > > > > > > > > to be a (tiny) regression.
> > > > > > > > 
> > > > > > > > The source pane in under the responsability of Qt, AFAIK. It 
> > > > > > > > might be
> > > > > > > > that you see a bug in Qt itself. What is the Qt version that 
> > > > > > > > your LyX
> > > > > > > > uses?
> > > > > > > > 
> > > > > > > > JMarc
> > > > > > > It's Uwe's windows version of rc1, hence Qt 5.6 as I understand. 
> > > > > > > (There
> > > > > > > isn't anything about Qt version in the About LyX tabs. It would 
> > > > > > > be a good
> > > > > > > addition to the information there.)
> > > > > > 
> > > > > > I thought we did have it. In Help > About, for me it says:
> > > > > > 
> > > > > > Qt Version (run-time): 5.6.0
> > > > > > Qt Version (compile-time): 5.6.0
> > > > > 
> > > > > This is visible for development version only.
> > > > 
> > > > I see. Is the concern that we will confuse the user? Or that the
> > > > information is useless because we should remember which Qt version was
> > > > used for each release we provide?
> > 
> > The idea was: it’s useful for developers only because one shouldn’t be 
> > unsure
> > about the Qt-version of the released LyX package. But it’s easy to change 
> > and
> > if in practice it’s interesting to know - why not. Patch is attached.
> > 
> > > 
> > > Here, it is in About > Build Info in release mode.
> > 
> > Yes, I was not precise enough. It depends on the location of the source tree
> > in a git clone or not.
> > 
> 
> Patch looks sensible and reasonable.
> 
> 

Doesn't seem like there is any disagreement. I would say commit.

Thanks,

Scott


signature.asc
Description: PGP signature

Re: [PATCH] microtype

[Georg Baum]

Pavel Sanda wrote:

> Georg Baum wrote:
>> > I just blindly copied what was there for other on-off packages, because
>> > I have little clue what tex2lyx code does and zero comments in critical
>> > sections does not help. I know it's not your fault ;)
>> 
>> Actually the other packages are not on-off, they are off-auto-on. This is
>> needed for all packages automatically loaded by math commands. It is not
>> needed for microtype, since ther is no automatism.
> 
> Oh, I see, so "2" is actually value for tri-state variable on-off-auto,
> correct?

Exactly. See the enum Package in BufferParams.h.

>> The minimum thing you need to do is to write the format corresponding to
>> LYX_FORMAT_TEX2LYX (see attached). The actual recognition of a loaded
>> microtype package can be done later (this is the reason why you need a
>> TODO entry).
> 
> Sure, I can do that.

You did it already in your patch :-)


Georg

Re: checkbox to filter font list by document language

[Jean-Marc Lasgouttes]

Le 02/06/16 à 20:41, Scott Kostyshak a écrit :

You are right, LyX deserves a better font selection dialog. I had a
quick look: there is the QFontDialog widget which has a writing system
selection menu. See https://doc.qt.io/qt-5/qfontdialog.html and
qtbase/examples/widgets/dialogs/standarddialogs/.


I am not sure I understand. It seems that the dialog is useful for 
selecting font, style and size. This is not exactly what we need.


Usually what is used is a combox that shows the font. Is it 
possible/easy with qt?


JMarc

Re: #9368: Apostrophe a problem in file name

[Michael Maltenfort]

I too continue to have the problem. I'm using LyX 2.2.0 on a Windows 7 
Enterprise machine with Adobe Acrobat Reader DC 15.016.20045.
When I try to LaTeX my file with a filename apostrophe (one-line file with 
filename Maltenfort's), I get a pop-up window "pdfview.exe has stopped 
working."  The problem goes away if the apostrophe isn't in the filename.  Here 
is what I got from "show problem details":
Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    pdfview.exe
  Application Version:    0.0.0.0
  Application Timestamp:    56ff3a9a
  Fault Module Name:    SHELL32.dll
  Fault Module Version:    6.1.7601.23418
  Fault Module Timestamp:    5708a73f
  Exception Code:    c005
  Exception Offset:    002445f0
  OS Version:    6.1.7601.2.1.0.256.4
  Locale ID:    1033
  Additional Information 1:    0a9e
  Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:    0a9e
  Additional Information 4:    0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288=0x0409

If the online privacy statement is not available, please read our privacy 
statement offline:
  C:\Windows\system32\en-US\erofflps.txt

---Michael

  From: LyX Ticket Tracker 
 To: maltenf...@yahoo.com; lasgout...@lyx.org 
Cc: for...@lyx.org; sp...@lyx.org
 Sent: Wednesday, June 1, 2016 11:44 PM
 Subject: Re: #9368: Apostrophe a problem in file name
  
#9368: Apostrophe a problem in file name
+-
 Reporter:  maltenfort              |      Owner:  lasgouttes
    Type:  defect                  |      Status:  new
 Priority:  low                    |  Milestone:
Component:  general                |    Version:  2.1.2
 Severity:  minor                  |  Resolution:
 Keywords:  os=windows, infoneeded  |
+-

Comment (by skostysh):

 Thanks for checking, Andrew. That error definitely shows that LyX is
 confused. I cannot reproduce so hopefully someone else can figure out
 what's going on.

-- 
Ticket URL: 
The LyX Project 
LyX -- The Document Processor


  

Re: checkbox to filter font list by document language

[Scott Kostyshak]

On Thu, Jun 02, 2016 at 02:41:31PM -0400, Scott Kostyshak wrote:
> On Thu, Jun 02, 2016 at 05:32:31PM +0100, Guillaume Munch wrote:
> > Le 02/06/2016 07:07, Scott Kostyshak a écrit :
> > > Dear all,
> > > 
> > > I have many system fonts installed (the command `fc-list | wc -l`
> > > gives me 1595. Can anyone beat that?). When testing LyX's XeTeX
> > > export with system fonts and various languages, it can be a little
> > > annoying to find a font that has the necessary symbols. What I
> > > usually do is e.g.
> > > 
> > > fc-list :lang=he
> > > 
> > > to list the fonts that support Hebrew.
> > > 
> > > As Xe/LuaTeX are becoming more popular, I wonder if it would be worth
> > > it to make this easier for users. The way we can do this is to have a
> > > checkbox that says "restrict to document language". For example, the
> > > screenshot shows all fonts that support Hebrew. I produced the
> > > screenshot using the attached patch.
> > > 
> > > So all we would need to do is map our list of document languages to
> > > the WritingSystem enum, whose values are listed in the table here:
> > > http://doc.qt.io/qt-4.8/qfontdatabase.html#WritingSystem-enum Could
> > > we do that by adding another field in lib/languages?
> > > 
> > > Does anyone think this would be worth the work? I don't actually
> > > write anything except for English so I don't know. Maybe the way we
> > > have things set up now is not a bother at all.
> > > 
> > > Scott
> > > 
> > 
> > Dear Scott,
> > 
> > You are right, LyX deserves a better font selection dialog. I had a
> > quick look: there is the QFontDialog widget which has a writing system
> > selection menu. See https://doc.qt.io/qt-5/qfontdialog.html and
> > qtbase/examples/widgets/dialogs/standarddialogs/.
> > 
> > The lyx font selection widgets could trigger this dialog instead of the
> > drop-down menu. This should be easy to do. Note that this would also fix
> > other issues, such as not being able to select specific fonts. For
> > instance it is currently impossible to select Source Sans Pro Light.
> > 
> > It does not seem to be possible to initialise the dialog with a specific
> > writing system unlike what you suggest. If you find the motivation, you
> > could implement a custom font selection widget based on
> > qtbase/src/widgets/dialogs/qfontdialog.cpp (no size selection,
> > defaultable writing system, no underlining, etc.). Another idea is to
> > make the widget into a button (QToolButton) that, in addition to opening
> > the font dialog when pressed, also has a drop-down menu showing the
> > recently used fonts. That would be another way to make font selection
> > more convenient.
> > 
> > But, for a quick solution that also addresses other issues, my advice would
> > be to make the button open the QFontDialog.
> > 
> 
> Thanks for taking a look and for the comments, Guillaume. It might be
> nice to do as you suggest and move to QFontDialog. Whenever we can rely
> on Qt it seems like that is the way to go. The preview widget contained
> in that dialog is especially nice. I think what I'll do for now is just
> open an enhancement request and post our ideas there. I do not want to
> undertake such a project at this time.
> 
> Scott

I forgot to say that the preview widget would be especially nice in our
text style dialog.

Scott




signature.asc
Description: PGP signature

Re: checkbox to filter font list by document language

[Scott Kostyshak]

On Thu, Jun 02, 2016 at 05:32:31PM +0100, Guillaume Munch wrote:
> Le 02/06/2016 07:07, Scott Kostyshak a écrit :
> > Dear all,
> > 
> > I have many system fonts installed (the command `fc-list | wc -l`
> > gives me 1595. Can anyone beat that?). When testing LyX's XeTeX
> > export with system fonts and various languages, it can be a little
> > annoying to find a font that has the necessary symbols. What I
> > usually do is e.g.
> > 
> > fc-list :lang=he
> > 
> > to list the fonts that support Hebrew.
> > 
> > As Xe/LuaTeX are becoming more popular, I wonder if it would be worth
> > it to make this easier for users. The way we can do this is to have a
> > checkbox that says "restrict to document language". For example, the
> > screenshot shows all fonts that support Hebrew. I produced the
> > screenshot using the attached patch.
> > 
> > So all we would need to do is map our list of document languages to
> > the WritingSystem enum, whose values are listed in the table here:
> > http://doc.qt.io/qt-4.8/qfontdatabase.html#WritingSystem-enum Could
> > we do that by adding another field in lib/languages?
> > 
> > Does anyone think this would be worth the work? I don't actually
> > write anything except for English so I don't know. Maybe the way we
> > have things set up now is not a bother at all.
> > 
> > Scott
> > 
> 
> Dear Scott,
> 
> You are right, LyX deserves a better font selection dialog. I had a
> quick look: there is the QFontDialog widget which has a writing system
> selection menu. See https://doc.qt.io/qt-5/qfontdialog.html and
> qtbase/examples/widgets/dialogs/standarddialogs/.
> 
> The lyx font selection widgets could trigger this dialog instead of the
> drop-down menu. This should be easy to do. Note that this would also fix
> other issues, such as not being able to select specific fonts. For
> instance it is currently impossible to select Source Sans Pro Light.
> 
> It does not seem to be possible to initialise the dialog with a specific
> writing system unlike what you suggest. If you find the motivation, you
> could implement a custom font selection widget based on
> qtbase/src/widgets/dialogs/qfontdialog.cpp (no size selection,
> defaultable writing system, no underlining, etc.). Another idea is to
> make the widget into a button (QToolButton) that, in addition to opening
> the font dialog when pressed, also has a drop-down menu showing the
> recently used fonts. That would be another way to make font selection
> more convenient.
> 
> But, for a quick solution that also addresses other issues, my advice would
> be to make the button open the QFontDialog.
> 

Thanks for taking a look and for the comments, Guillaume. It might be
nice to do as you suggest and move to QFontDialog. Whenever we can rely
on Qt it seems like that is the way to go. The preview widget contained
in that dialog is especially nice. I think what I'll do for now is just
open an enhancement request and post our ideas there. I do not want to
undertake such a project at this time.

Scott


signature.asc
Description: PGP signature

Re: checkbox to filter font list by document language

[Guillaume Munch]

Le 02/06/2016 07:07, Scott Kostyshak a écrit :

Dear all,

I have many system fonts installed (the command `fc-list | wc -l`
gives me 1595. Can anyone beat that?). When testing LyX's XeTeX
export with system fonts and various languages, it can be a little
annoying to find a font that has the necessary symbols. What I
usually do is e.g.

fc-list :lang=he

to list the fonts that support Hebrew.

As Xe/LuaTeX are becoming more popular, I wonder if it would be worth
it to make this easier for users. The way we can do this is to have a
checkbox that says "restrict to document language". For example, the
screenshot shows all fonts that support Hebrew. I produced the
screenshot using the attached patch.

So all we would need to do is map our list of document languages to
the WritingSystem enum, whose values are listed in the table here:
http://doc.qt.io/qt-4.8/qfontdatabase.html#WritingSystem-enum Could
we do that by adding another field in lib/languages?

Does anyone think this would be worth the work? I don't actually
write anything except for English so I don't know. Maybe the way we
have things set up now is not a bother at all.

Scott



Dear Scott,

You are right, LyX deserves a better font selection dialog. I had a
quick look: there is the QFontDialog widget which has a writing system
selection menu. See https://doc.qt.io/qt-5/qfontdialog.html and
qtbase/examples/widgets/dialogs/standarddialogs/.

The lyx font selection widgets could trigger this dialog instead of the
drop-down menu. This should be easy to do. Note that this would also fix
other issues, such as not being able to select specific fonts. For
instance it is currently impossible to select Source Sans Pro Light.

It does not seem to be possible to initialise the dialog with a specific
writing system unlike what you suggest. If you find the motivation, you
could implement a custom font selection widget based on
qtbase/src/widgets/dialogs/qfontdialog.cpp (no size selection,
defaultable writing system, no underlining, etc.). Another idea is to
make the widget into a button (QToolButton) that, in addition to opening
the font dialog when pressed, also has a drop-down menu showing the
recently used fonts. That would be another way to make font selection
more convenient.

But, for a quick solution that also addresses other issues, my advice 
would be to make the button open the QFontDialog.


Guillaume