On 2016-12-07, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> 2016-12-07 13:27 GMT+01:00 Guenter Milde:
>> Suggestion
>> ==
>> Let the “quote” LFUN insert literal Unicode characters
> Sound like a good idea (but probably needs good testing).
The
On 12/07/2016 06:15 AM, Jean-Marc Lasgouttes wrote:
>
> - why is the slowness visible on Ubuntu 16.10 (Qt 4.8.7) but not
> Ubuntu 12.04 (Qt 4.8.1)?
And more weirdly: I have never seen this kind of problem on Fedora with
Qt 4.8.7.
Richard
On 2016-12-07, Jean-Marc Lasgouttes wrote:
> Le 07/12/2016 à 13:27, Guenter Milde a écrit :
...
>> The Quotes inset shows a number of problems that could easily be solved
>> by using literal Unicode characters instead
>> Most important:
>> * Adjoining closing Single + double quote becomes
Am Mittwoch, den 07.12.2016, 14:02 +0100 schrieb Jean-Marc Lasgouttes:
> I agree that currently the quote inset is not very helpful (only
> franch
> spacing is important here). If however some smart quote handling
> gets
> introduced, then the inset will be mandatory.
What I'd like to see
On 12/07/2016 12:33 PM, Richard Heck wrote:
> On 12/07/2016 07:17 AM, Guenter Milde wrote:
>> ["Followup-To:" nach gmane.editors.lyx.devel gesetzt.]
>> On 2016-12-07, Jürgen Spitzmüller wrote:
>>> 2016-12-07 0:17 GMT+01:00 Richard Heck :
commit
Am Mittwoch, den 07.12.2016, 17:49 + schrieb Guenter Milde:
> > What bugs would remain once this switch to unicode is done in the
> > inset?
> > Except of course that the code is still complicated.
>
> Data loss when converting to a "listings" or ERT or URL inset.
>
On 12/07/2016 07:17 AM, Guenter Milde wrote:
> ["Followup-To:" nach gmane.editors.lyx.devel gesetzt.]
> On 2016-12-07, Jürgen Spitzmüller wrote:
>> 2016-12-07 0:17 GMT+01:00 Richard Heck :
>>> commit 39e3fabffb52b78b08be3fa562cd6ce7c8dce2e5
>>> Author: Richard Heck
Am Mittwoch, den 07.12.2016, 17:53 + schrieb Guenter Milde:
> +1 "the right thing" for non-TeX fonts
> +1 "the right thing" for HTML (LyX generates utf8-encoded HTML
> documents)
Macros/HTML tags are not "the wrong thing".
> +1 no need to query "fontenc": Unicode charaters are replaced by
>
On 2016-12-07, Jürgen Spitzmüller wrote:
> 2016-12-07 13:27 GMT+01:00 Guenter Milde :
>> * Adjoining closing Single + double quote becomes double + single quote
>> (for English, Swedish and German, LaTeX export as ''').
>> * French double quotes are converted to << >> in
Am Mittwoch, den 07.12.2016, 17:28 + schrieb Guenter Milde:
> The only possible problem would be to make sure that the
> unicodesymbols
> replacements are done *after* coverting the Quote inset to a quote
> character.
Can you assure that the opening/closing quote mechanism will still work
Le 07/12/2016 à 17:01, Enrico Forestieri a écrit :
On Wed, Dec 07, 2016 at 12:06:41PM +0100, Jean-Marc Lasgouttes wrote:
I did not mean a security tab, but a "general" one that could contain:
- converter file cache
- security
- overwrite on export (from Output|general)
I don't like this
On 2016-12-07, Guenter Milde wrote:
> ["Followup-To:" nach gmane.editors.lyx.devel gesetzt.]
> On 2016-12-07, Jürgen Spitzmüller wrote:
>> 2016-12-07 0:17 GMT+01:00 Richard Heck :
>>> commit 39e3fabffb52b78b08be3fa562cd6ce7c8dce2e5
>>> Author: Richard Heck
>>>
Am Mittwoch, den 07.12.2016, 21:14 + schrieb Guenter Milde:
> If quotes come in pairs, it can be implemented similar to brackets.
> (Also for brackets there is a chance of mismatch due to other uses
> like
> 1) in enumerations
> 2) in smilies :-)
> )
Really? Do you have a patch for that?
Am Mittwoch, den 07.12.2016, 23:09 + schrieb Guenter Milde:
> However, given that other non-ASCII characters are exported as-is,
> too
> using literal characters for typographical quotes makes the generated
> document's source more consistent and easier to read.
>
> Also:
> +1 get rid of the
On 2016-12-07, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 07.12.2016, 17:28 + schrieb Guenter Milde:
>> The only possible problem would be to make sure that the
>> unicodesymbols replacements are done *after* coverting the Quote inset
>> to a quote character.
> Can you assure that the
On Wed, Dec 07, 2016 at 10:35:06PM +0100, Cor Blom wrote:
> Op 03-12-16 om 22:51 schreef Scott Kostyshak:
> > > The other thing is that on screen, when I type a rtl text in a ltr
> > > documents, I have to mark that word as e.g. Hebrew before the sequence is
> > > right. I would be nice to have
On 07/12/2016 18:58, Richard Heck wrote:
- why is the slowness visible on Ubuntu 16.10 (Qt 4.8.7) but not
Ubuntu 12.04 (Qt 4.8.1)?
I'm having the issue on Ubuntu 16.10 with Qt 4.8.7.
tommaso@tommylap:~/lyx-trunk-ws/lyx$ dpkg -l | grep libqt4 | grep -v 386
ii libqt4-dbus:amd64
Op 03-12-16 om 22:51 schreef Scott Kostyshak:
The other thing is that on screen, when I type a rtl text in a ltr
documents, I have to mark that word as e.g. Hebrew before the sequence is
right. I would be nice to have that done automatically. Xetex does it right,
even if it is not marked as rtl.
Le 7 décembre 2016 23:06:11 CET, Guenter Milde a écrit :
>On 2016-12-07, Jürgen Spitzmüller wrote:
>> Am Mittwoch, den 07.12.2016, 17:28 + schrieb Guenter Milde
>
>> What about extended features such as quote balancing check or
>> automatic nesting (of inner/outer quotes)?
On 06/12/2016 23:12, Tommaso Cucinotta wrote:
I'll try to profile later, unless others made progress on this already.
valgrind --tool=callgrind reports, without recompiling with -g, the following:
libfreetype.so.6.12.3 77.14%
libQtGui.so.4.8.7 8.10%
...
~46 million calls to smth in
On 2016-12-07, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Mittwoch, den 07.12.2016, 17:53 + schrieb Guenter Milde:
>> +1 "the right thing" for non-TeX fonts
>> +1 "the right thing" for HTML (LyX generates utf8-encoded HTML
>> documents)
>
On 2016-12-07, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Mittwoch, den 07.12.2016, 19:58 + schrieb Guenter Milde:
>> I am not sure the Quote inset brings benefits for this feature.
> I doubt it is possible to implement it without the inset.
If
On Wed, Dec 07, 2016 at 06:15:02PM +0100, Jean-Marc Lasgouttes wrote:
>
> Yes, your patch make the separation clearer (although I am not sure that I
> like the oval rect).
I thought it would have helped in distingushing the sections, but this is
a mere detail.
> But the fact that this converter
On 2016-12-07, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 07.12.2016, 14:02 +0100 schrieb Jean-Marc Lasgouttes:
> What I'd like to see eventually is some kind of quote balancing check,
> such that if you enter a closing quote, the text back to the respective
> opening quote is highlighted. Same
On 06/12/2016 23:48, Scott Kostyshak wrote:
On Tue, Dec 06, 2016 at 11:12:56PM +0100, Tommaso Cucinotta wrote:
Hi there,
I haven't seen this, and I use LyX 2.2 on Ubuntu daily. Which Qt version
are you using?
tommaso@tommylap:~$ ldd `which lyx` | grep -i qt
libQtGui.so.4 =>
On 2016-12-06, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Mittwoch, den 30.11.2016, 12:28 + schrieb Guenter Milde:
>> File format change?
> definitely.
>> IMV, this cannot be improved with a file format change, hence we
>> don't
>> need one.
>
Hi,
try adding
#include
to Encoding.cpp.
-
Jan
On Wed, 7 Dec 2016, at 00:36, Uwe Stöhr wrote:
> With today's master I get this compilation error:
>
> Encoding.cpp
> D:\LyXGit\Master\src\Encoding.cpp(267): error C3861: 'back_inserter':
> identifier not found
Le 07/12/2016 à 13:27, Guenter Milde a écrit :
Dear LyX developers,
I am asking for comments and suggestions regarding Ticket #10451:
The Quotes inset shows a number of problems that could easily be solved
by using literal Unicode characters instead
Most important:
* Adjoining closing
2016-12-07 0:17 GMT+01:00 Richard Heck :
> commit 39e3fabffb52b78b08be3fa562cd6ce7c8dce2e5
> Author: Richard Heck
> Date: Tue Dec 6 17:54:32 2016 -0500
>
> Verbatim, etc, can be used with IOP articles.
> Fixes #10505.
>
> (cherry picked from commit
["Followup-To:" nach gmane.editors.lyx.devel gesetzt.]
On 2016-12-07, Jürgen Spitzmüller wrote:
> 2016-12-07 0:17 GMT+01:00 Richard Heck :
>> commit 39e3fabffb52b78b08be3fa562cd6ce7c8dce2e5
>> Author: Richard Heck
>> Date: Tue Dec 6 17:54:32 2016 -0500
>>
Le 06/12/2016 à 17:37, Tommaso Cucinotta a écrit :
Creating a separate prefs tab might be meaningful if we had more
security settings
not related exclusively to converters, but keeping things together
within a single
converters pane has the advantage of linking clearly the security
checkboxes
Le 07/12/2016 à 11:32, Tommaso Cucinotta a écrit :
On 06/12/2016 23:48, Scott Kostyshak wrote:
On Tue, Dec 06, 2016 at 11:12:56PM +0100, Tommaso Cucinotta wrote:
Hi there,
I haven't seen this, and I use LyX 2.2 on Ubuntu daily. Which Qt version
are you using?
tommaso@tommylap:~$ ldd `which
2016-12-07 10:45 GMT+01:00 Guenter Milde :
> However, the parsing error is harmless as the workaround is already "the
> right thing". Just try:
>
It does not matter if it works by accident or not. The file format is
"corrupted" and needs to be corrected on conversion.
>
Dear LyX developers,
I am asking for comments and suggestions regarding Ticket #10451:
The Quotes inset shows a number of problems that could easily be solved
by using literal Unicode characters instead.
Most important:
* Adjoining closing Single + double quote becomes double + single quote
2016-12-07 13:27 GMT+01:00 Guenter Milde:
> Suggestion
> ==
>
> Let the “quote” LFUN insert literal Unicode characters
>
Sound like a good idea (but probably needs good testing).
> Use the Quotes inset for "dynamic quotes" (the remaining
> part of #1499) and Unicode for "static
Le 07/12/2016 à 12:15, Jean-Marc Lasgouttes a écrit :
I'll post a new version to try soon.
Here is a patch to play with. It is not perfect, but I would be
interested to know whether it improves performance with Qt4.
JMarc
From 186d439af023942a6171a6a8ce5bafaa2c6715e0 Mon Sep 17 00:00:00
On 12/07/2016 04:44 PM, Tommaso Cucinotta wrote:
> On 06/12/2016 23:12, Tommaso Cucinotta wrote:
>> I'll try to profile later, unless others made progress on this already.
>
> valgrind --tool=callgrind reports, without recompiling with -g, the
> following:
>
> libfreetype.so.6.12.377.14%
>
On 08/12/2016 00:36, Richard Heck wrote:
On 12/07/2016 04:44 PM, Tommaso Cucinotta wrote:
More info at: http://retis.sssup.it/~tommaso/callgrind.out.17492.gz
Is it possible this has something to do with what screen fonts are being
used?
The recompiled & Qt 4.8.7-linked version, with -g
On Wed, Dec 07, 2016 at 12:06:41PM +0100, Jean-Marc Lasgouttes wrote:
>
> I did not mean a security tab, but a "general" one that could contain:
>
> - converter file cache
> - security
> - overwrite on export (from Output|general)
I don't like this further fragmentation. I like the fact that we
On 12/07/2016 06:46 PM, Tommaso Cucinotta wrote:
> On 08/12/2016 00:36, Richard Heck wrote:
>> On 12/07/2016 04:44 PM, Tommaso Cucinotta wrote:
>>> More info at: http://retis.sssup.it/~tommaso/callgrind.out.17492.gz
>>
>> Is it possible this has something to do with what screen fonts are being
>>
2016-12-07 13:27 GMT+01:00 Guenter Milde :
> * Adjoining closing Single + double quote becomes double + single quote
> (for English, Swedish and German, LaTeX export as ''').
>
> * French double quotes are converted to << >> in the LaTeX file and to
> double inverted
Am Mittwoch, den 07.12.2016, 19:58 + schrieb Guenter Milde:
> I am not sure the Quote inset brings benefits for this feature.
I doubt it is possible to implement it without the inset.
> +1 it may distinguish single closing quote and apostrophe.
>
> -1 it may still mix them, when the
42 matches
Mail list logo