Re: UTF-8 in string literals and translation strings in particular

Please, do not scatter the messages that much, and make the discussion easy to follow. Recalling the subject of the discussion: Le 08/10/2015 01:55, Cyrille Artho a écrit : Why not apply a variant of that hack as using "sed" to all the language/menu strings in the repository? Of course the

Re: UTF-8 in string literals and translation strings in particular

Le 08/10/2015 11:58, Guillaume Munch a écrit : Please, do not scatter the messages that much, and make the discussion easy to follow. I will reply only to some of the arguments for the sake of efficiency. Le 07/10/2015 00:23, Pavel Sanda a écrit : To clarify, I'm not against having ellipsis

Re: UTF-8 in string literals and translation strings in particular

Am 08.10.2015 um 16:02 schrieb Jean-Marc Lasgouttes : >>> I have to admit that I did not understand Abdel's idea %-| >> >> I understood it that way: to present the ellipsis character in the UI >> there is no need to put that character with unicode in the source code. >> It is

Fwd: Some buttons on Maths palette don't work!

This is really interesting. LyX 2.2.0 fixes some problem on latest Mac OS "El Capitan". I guess the fix is there because of the change to Qt5. We should start with the release process of the thing, IMHO. Stephan Anfang der weitergeleiteten Nachricht: > Von: jken...@ssc.wisc.edu > Betreff: Aw:

Re: UTF-8 in string literals and translation strings in particular

Am 08.10.2015 um 15:45 schrieb Jean-Marc Lasgouttes : > Le 08/10/2015 11:58, Guillaume Munch a écrit : >> Please, do not scatter the messages that much, and make the discussion >> easy to follow. > > I will reply only to some of the arguments for the sake of efficiency. > …

Re: UTF-8 in string literals and translation strings in particular

I have to admit that I did not understand Abdel's idea %-| I understood it that way: to present the ellipsis character in the UI there is no need to put that character with unicode in the source code. It is possible to translate the sequence "..." to the character "…" within the I18N process. I

Re: segmentation fault, lyx2.2.0dev @ Fedora 23 with Qt 5.5.0

Dear Guillaume, I finished my search for the bug yesterday, by checking out a few suspicious commits in the last 30 days, and to my great surprise even the latest commit worked. I really don't know what happened. I had it all built in a separate directory (that I even cleaned several times),

Re: segmentation fault, lyx2.2.0dev @ Fedora 23 with Qt 5.5.0

Le 06/10/2015 15:41, PhilipPirrip a écrit : Thanks, Kornel. I'll check these later. I went back in time, September 28 18:13 commit 39343d65af worked. Moving forward, will let you know when things went bad and send you the backtrace. Dear Philip, I cannot reproduce it with my own

Re: LyX on high resolution displays

On 09/13/2015 09:39 PM, Scott Kostyshak wrote: Here's a screenshot: >http://wiki.lyx.org/uploads/Playground/LyX_screenshot_HiDPI_13inch_display_3200x1800_2015-09-13_Qt5.png Ouch that indeed does not look good. I feel like this is a Qt bug. Unless our .ui files are not well-defined, Qt is

Re: UTF-8 in string literals and translation strings in particular

Am Donnerstag, 8. Oktober 2015 um 16:14:49, schrieb Stephan Witt > Am 08.10.2015 um 16:02 schrieb Jean-Marc Lasgouttes : > > >>> I have to admit that I did not understand Abdel's idea %-| > >> > >> I understood it that way: to present the ellipsis character

Lyx fundamental problem in interpreting new document classes?

Dear LYX Developers, I want to draw your attention to two questions posted on stackoverflow. I think they are similar/related. I wonder if this is a fundamental Lyx limit or the end users have not used Lyx properly. Your help is greatly appreciated.

Re: segmentation fault, lyx2.2.0dev @ Fedora 23 with Qt 5.5.0

Le 08/10/2015 15:27, PhilipPirrip a écrit : Dear Guillaume, I finished my search for the bug yesterday, by checking out a few suspicious commits in the last 30 days, and to my great surprise even the latest commit worked. I really don't know what happened. I had it all built in a separate

Re: UTF-8 in string literals and translation strings in particular

Le 08/10/2015 16:46, Kornel Benko a écrit : Am Donnerstag, 8. Oktober 2015 um 16:14:49, schrieb Stephan Witt I think the idea was to let the translators do it manually where it is appropriate. And to do it for english this way too. I think that too. I did it for sk.po, it

Re: UTF-8 in string literals and translation strings in particular

Le 08/10/2015 14:45, Jean-Marc Lasgouttes a écrit : I will reply only to some of the arguments for the sake of efficiency. As we usually say, I lacked the time to make it shorter... The problem with the patch is that it does not have a clear goal. The discussion would have been much easier

Re: UTF-8 in string literals and translation strings in particular

Am Donnerstag, 8. Oktober 2015 um 17:35:46, schrieb Guillaume Munch > Le 08/10/2015 16:46, Kornel Benko a écrit : > > Am Donnerstag, 8. Oktober 2015 um 16:14:49, schrieb Stephan Witt > > > >> > >> I think the idea was to let the translators do it manually where >

Re: Release manager for LyX 2.2

Pavel Sanda wrote: > Hi all, > > it is very clear that we need to move forward with the release process. > > After the discussion with the former and current managers we agreed that > Scott Kostyshak has our trust for the role of release manager of 2.2. He > has good understanding of the code

Re: Release manager for LyX 2.2

On Wed, Oct 07, 2015 at 11:08:21AM +0200, Jean-Marc Lasgouttes wrote: > Le 07/10/2015 11:04, Pavel Sanda a écrit : > >Hi all, > > > >it is very clear that we need to move forward with the release process. > > > >After the discussion with the former and current managers we agreed that > >Scott >

Re: LyX on high resolution displays

Guillaume Munch wrote: > Hi, > > > Note that under Linux+Qt5, there's this bug: > > http://www.lyx.org/trac/ticket/9731 > > presumably fixed in Qt5.6: > > https://codereview.qt-project.org/#/c/126136/ > > 1) Is your testing environment still Linux? > 2) Does the slowness disappear if you

Re: Compiling LyX on Windows with more recent Visual Studio versions

David Hyde wrote: > Hi there, > > > I'm interested in compiling LyX on Windows. I've read through the > INSTALL.Win32 file and was able to get LyX to compile from source using > Visual C++ Express 2010, following the instructions in that file. Great! > I'm > wondering though, is it possible

Re: UTF-8 in string literals and translation strings in particular

On Thu, Oct 08, 2015 at 09:48:52PM +0200, Jean-Marc Lasgouttes wrote: > Le 08/10/15 03:19, Cyrille Artho a écrit : > >It's possible to embed characters from a font in an SVG graph; this > >could be used to avoid problems with fonts that do not have all math > >characters. > > I seem to remember

Re: UTF-8 in string literals and translation strings in particular

Jean-Marc Lasgouttes wrote: > The problem with the patch is that it does not have a clear goal. The > discussion would have been much easier if you had splitted it in 3 from > the start: > > 1/ easy use of utf8 in docstring > 2/ allow utf8 in translattable strings > 3/ use … instead of ... in UI

Re: UTF-8 in string literals and translation strings in particular

Le 08/10/2015 22:11, Georg Baum a écrit : Jean-Marc Lasgouttes wrote: The problem with the patch is that it does not have a clear goal. The discussion would have been much easier if you had splitted it in 3 from the start: 1/ easy use of utf8 in docstring 2/ allow utf8 in translattable

Re: LyX on high resolution displays

PhilipPirrip wrote: > Is 2.2 going to be a Qt5 app by default (or is it up to packagers)? 2.2 will support both qt4 and qt5, where qt4 support is probably most important for older linux distros. The windows and Mac binaries are likely to be compiled with qt5. Georg

Re: Release manager for LyX 2.2

On Thu, Oct 8, 2015 at 10:17 PM, Enrico Forestieri wrote: > On Wed, Oct 07, 2015 at 11:08:21AM +0200, Jean-Marc Lasgouttes wrote: >> Le 07/10/2015 11:04, Pavel Sanda a écrit : >> >Hi all, >> > >> >it is very clear that we need to move forward with the release process. >> > >>

Re: UTF-8 in string literals and translation strings in particular

On 08/10/2015 16:14, Stephan Witt wrote: Am 08.10.2015 um 16:02 schrieb Jean-Marc Lasgouttes : I have to admit that I did not understand Abdel's idea %-| I understood it that way: to present the ellipsis character in the UI there is no need to put that character with

Re: UTF-8 in string literals and translation strings in particular

On 08/10/2015 11:58, Guillaume Munch wrote: I think that my solution is vastly superior to these proposed alternatives that misrepresent the problem, and that I have lifted the technical objections and the burden for translators. I think I mostly agree with you at this point. That being said

Re: UTF-8 in string literals and translation strings in particular

Le 08/10/15 03:19, Cyrille Artho a écrit : It's possible to embed characters from a font in an SVG graph; this could be used to avoid problems with fonts that do not have all math characters. I seem to remember (but git log is your friend) that these icon started their life with embedded