Le 18/12/2016 à 12:21, Jürgen Spitzmüller a écrit :
Would you like to have a go? After all, inset-forall is your child ;-)
This particular child was born in 2009, and I'd say that in lfun-years,
it is very much adult. But in memory of the good old days, I'll try to
have a look.
JMarc
Am Sonntag, den 18.12.2016, 20:36 + schrieb Guenter Milde:
> We could also take the symbol from T1
Good idea.
> or the typewriter font:
IMHO mixing fonts is not a good idea.
I think I'll go for
\DeclareTextSymbolDefault{\textquotedbl}{T1}
Thanks,
Jürgen
signature.asc
Description: This i
On 2016-12-18, Jürgen Spitzmüller wrote:
> Am Montag, den 12.12.2016, 11:01 + schrieb Guenter Milde:
>> > > As opposed to that, I would rather introduce a plain quote style
>> > > and ditch the straight quote special char
>> Seconded. This could also solve the issue with the currently missing
Am Montag, den 12.12.2016, 11:01 + schrieb Guenter Milde:
> > > As opposed to that, I would rather introduce a plain quote style
> > > and
> > > ditch the straight quote special char
>
> Seconded. This could also solve the issue with the currently missing
> straight single quote/apostrophe.
Am Sonntag, den 18.12.2016, 12:18 +0100 schrieb Jean-Marc Lasgouttes:
> Le 18/12/2016 à 11:33, Jürgen Spitzmüller a écrit :
> > Am Sonntag, den 18.12.2016, 11:20 +0100 schrieb Jürgen Spitzmüller:
> > > That would have to be more upstream (selection-forall, in line
> > > with
> > > buffer-forall)
>
Le 18/12/2016 à 11:33, Jürgen Spitzmüller a écrit :
Am Sonntag, den 18.12.2016, 11:20 +0100 schrieb Jürgen Spitzmüller:
That would have to be more upstream (selection-forall, in line with
buffer-forall)
inset-forall-select, for that matter.
Or change inset-forall to operate on selection when
Am Sonntag, 18. Dezember 2016 um 11:33:16, schrieb Jürgen Spitzmüller
> Am Sonntag, den 18.12.2016, 11:20 +0100 schrieb Jürgen Spitzmüller:
> > That would have to be more upstream (selection-forall, in line with
> > buffer-forall)
>
> inset-forall-select, for that matter.
>
> Jürgen
Sounds goo
Am Sonntag, den 18.12.2016, 11:20 +0100 schrieb Jürgen Spitzmüller:
> That would have to be more upstream (selection-forall, in line with
> buffer-forall)
inset-forall-select, for that matter.
Jürgen
signature.asc
Description: This is a digitally signed message part
Am Sonntag, den 18.12.2016, 11:11 +0100 schrieb Kornel Benko:
> Yes, this works too, thanks. Could we please get also a function for
> a selected region?
That would have to be more upstream (selection-forall, in line with
buffer-forall)
Jürgen
>
> Kornel
signature.asc
Description: This i
Am Sonntag, 18. Dezember 2016 um 10:42:17, schrieb Jürgen Spitzmüller
> Am Sonntag, den 18.12.2016, 10:38 +0100 schrieb Kornel Benko:
> > Playing with quotes for a while now.
> > It seems impossible to change quotes for a whole selected region at
> > once.
> > From my POV, that would be nice. Or
Am Sonntag, den 18.12.2016, 10:38 +0100 schrieb Kornel Benko:
> Playing with quotes for a while now.
> It seems impossible to change quotes for a whole selected region at
> once.
> From my POV, that would be nice. Or did I miss something?
This might be possible via Adv S&R.
For a whole document,
Am Samstag, 10. Dezember 2016 um 17:26:44, schrieb Jürgen Spitzmüller
> Am Samstag, den 10.12.2016, 16:27 +0100 schrieb Jürgen Spitzmüller:
> > > With non-TeX fonts and babel, \guillemotleft, \gullemotright,
> > > \guilsinglleft, and \guilsinglright are taken from CM: this results
> > > in
> > >
Am Donnerstag, den 15.12.2016, 13:13 + schrieb Guenter Milde:
> How about the following patch that simplifies the code a bit by using
> the
> same characters for text, docbook and html export?
> Tested and works here.
I'll let the docbook/xhtml folks decide on this.
Jürgen
signature.asc
Desc
On 2016-12-15, Jürgen Spitzmüller wrote:
...
> OK, I removed that spacing in master. Let's see what happens.
Thank you.
How about the following patch that simplifies the code a bit by using the
same characters for text, docbook and html export?
Tested and works here.
With your recent work on ma
Am Mittwoch, den 14.12.2016, 17:27 + schrieb Guenter Milde:
> // the preceding space is important here
> // FIXME: really? (doesn't make a difference
> // with recent babel-french)
> qstr = "
>> Dear Jürgen,
On 2016-12-13, Jürgen Spitzmüller wrote:
> 2016-12-13 10:34 GMT+01:00 Guenter Milde :
>> > The specific babel macros (e.g., \og, \fg for French) should be used.
>> This is not required, if the Babel configuration command
>> \frenchbsetup{og=«, fg=»} is included after the \usepac
2016-12-13 10:34 GMT+01:00 Guenter Milde :
> Dear Jürgen,
>
> On 2016-12-13, Jürgen Spitzmüller wrote:
> > Am Montag, den 12.12.2016, 22:12 + schrieb Guenter Milde:
>
> >> Unfortunately, with LuaTeX
> ...
> >> the padding of guillemets seems to be "sticky".
>
> > That's https://github.com/reut
Den 09. des. 2016 11:46, skrev Jean-Marc Lasgouttes:
And pardon me for failing to be impressed by the modernity of people
having unicode keyboards (how many keys does your keyboard have?) and
selection of a character in a list or 65535 others in some GUI where I
have to guess what is the ca
Dear Jürgen,
On 2016-12-13, Jürgen Spitzmüller wrote:
> Am Montag, den 12.12.2016, 22:12 + schrieb Guenter Milde:
>> Unfortunately, with LuaTeX
...
>> the padding of guillemets seems to be "sticky".
> That's https://github.com/reutenauer/polyglossia/issues/68
Yes, so it is hopefully worked
Am Montag, den 12.12.2016, 20:41 + schrieb Guenter Milde:
> Would it also be possible to override the "open/close" automatism?
> Currently, I have to
> write something,
> insert a quote,
> go back and delete what was written,
> go behind the quote again
> if I want a closing quote f
Am Montag, den 12.12.2016, 22:12 + schrieb Guenter Milde:
> Characters. Unfortunately, with LuaTeX it does this not only for
> French,
> but also English or German text --- I consider this a Polyglossia
> bug.
>
> English «is ‹fine›».
> French «‹is› fine» spaced as it should.
> English a
Dear Jürgen,
spacing/padding of French quotes is a wide field...
On 2016-12-11, Jürgen Spitzmüller wrote:
> Am Samstag, den 10.12.2016, 19:44 + schrieb Guenter Milde:
>> More interestingly, it also put spaces between single guillemots!
> Yes, sure. This is what polyglossia does as well (wit
On 2016-12-12, Jürgen Spitzmüller wrote:
>> >> As opposed to that, I would rather introduce a plain quote style and
>> >> ditch the straight quote special char
...
>> >> (and a language/style option "RequirePlainQuote").
>> Do we really require a separate option or could we just use the new
>> "s
2016-12-12 12:01 GMT+01:00 Guenter Milde :
> On 2016-12-11, Jürgen Spitzmüller wrote:
>
> >> As opposed to that, I would rather introduce a plain quote style and
> >> ditch the straight quote special char
>
> Seconded. This could also solve the issue with the currently missing
> straight single qu
On 2016-12-11, Jürgen Spitzmüller wrote:
>> As opposed to that, I would rather introduce a plain quote style and
>> ditch the straight quote special char
Seconded. This could also solve the issue with the currently missing
straight single quote/apostrophe.
>> (and a language/style option "Requi
Am Sonntag, den 11.12.2016, 10:18 +0100 schrieb Jürgen Spitzmüller:
> > Once we are at adding new quote styles, a separate style for Hebrew
> > seems
> > better suited than auto-converting any Quote-inset to straight
> > quotes
> > in
> > Hebrew.
>
> As opposed to that, I would rather introduce a
Am Samstag, den 10.12.2016, 19:44 + schrieb Guenter Milde:
> > Hm, interestingly enough,
> > \guillemotleft French \guillemotright
> > outputs the proper spacing with fontspec/LuaTeX.
>
> More interestingly, it also put spaces between single guillemots!
Yes, sure. This is what polyglossia do
On 2016-12-09, Jean-Marc Lasgouttes wrote:
> Le 07/12/2016 à 18:49, Guenter Milde a écrit :
>> The current behaviour of "insert-quote" LFUN is usually called "smart
>> quotes". This can be done without Quote insets.
> Sure. What the Quote inset brings us, as Juergen pointed out already, is
> som
On 2016-12-10, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Samstag, den 10.12.2016, 16:27 +0100 schrieb Jürgen Spitzmüller:
>> > No auto-spaces around quotes with polyglossia
>> The only supported way here seem to be literal glyphs.
Do you mean literal
Am Samstag, den 10.12.2016, 16:27 +0100 schrieb Jürgen Spitzmüller:
> > With non-TeX fonts and babel, \guillemotleft, \gullemotright,
> > \guilsinglleft, and \guilsinglright are taken from CM: this results
> > in
> > non-matching characters if the document font is not CM. (Exception:
> > correct «»
Am Samstag, den 10.12.2016, 16:27 +0100 schrieb Jürgen Spitzmüller:
> > No auto-spaces around quotes with polyglossia
>
> The only supported way here seem to be literal glyphs. I suggest we
> output those if polyglossia is used.
Hm, interestingly enough,
\guillemotleft French \guillemotright
out
Am Samstag, den 10.12.2016, 13:39 + schrieb Guenter Milde:
> With non-TeX fonts and babel, \guillemotleft, \gullemotright,
> \guilsinglleft, and \guilsinglright are taken from CM: this results
> in
> non-matching characters if the document font is not CM. (Exception:
> correct «» if the text la
Am Samstag, den 10.12.2016, 14:45 + schrieb Guenter Milde:
> Qould you apply the same fix to HTML export?
Done.
Jürgen
signature.asc
Description: This is a digitally signed message part
On 2016-12-10, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Samstag, den 10.12.2016, 13:39 + schrieb Guenter Milde:
>> On screen, the spaces are shown
>>
>> * for all quotes, not just guillemets.
> Fixed in master.
Thanks a lot.
Qould you apply
Am Samstag, den 10.12.2016, 13:39 + schrieb Guenter Milde:
> On screen, the spaces are shown
>
> * for all quotes, not just guillemets.
Fixed in master.
Jürgen
signature.asc
Description: This is a digitally signed message part
Am Samstag, den 10.12.2016, 13:39 + schrieb Guenter Milde:
> On screen, the spaces are shown
>
> * if the document language is set to French but not if only the text
> language is French.
Not as of e8c932ff.
Jürgen
signature.asc
Description: This is a digitally signed message part
On 2016-12-09, Jean-Marc Lasgouttes wrote:
> Le 08/12/2016 à 00:09, Guenter Milde a écrit :
>> * consistency: currently, if a user sees a guillemot « on screen, it
>> can be a literal character or a Quote inset and the LaTeX export can
>> be
>> "«" or "\guillemotleft" (depending on the "inp
Le 08/12/2016 à 00:09, Guenter Milde a écrit :
* consistency: currently, if a user sees a guillemot « on screen, it can be
a literal character or a Quote inset and the LaTeX export can be
"«" or "\guillemotleft" (depending on the "inputencoding")
"<<" (for Quote inset, even if « is support
Le 07/12/2016 à 18:49, Guenter Milde a écrit :
The current behaviour of "insert-quote" LFUN is usually called "smart
quotes". This can be done without Quote insets.
Sure. What the Quote inset brings us, as Juergen pointed out already, is
some semantics. But it is not semantics that we really e
Dear Jean-Marc,
On 2016-12-08, Jean-Marc Lasgouttes wrote:
> Le 08/12/2016 à 00:09, Guenter Milde a écrit :
>> * consistency: currently, if a user sees a guillemot « on screen, it can be
>> a literal character or a Quote inset and the LaTeX export can be
>> "«" or "\guillemotleft" (depending
Dear Jürgen,
On 2016-12-08, Jürgen Spitzmüller wrote:
> 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 cons
Le 08/12/2016 à 00:09, Guenter Milde a écrit :
* consistency: currently, if a user sees a guillemot « on screen, it can be
a literal character or a Quote inset and the LaTeX export can be
"«" or "\guillemotleft" (depending on the "inputencoding")
"<<" (for Quote inset, even if « is support
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? I
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 d
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)
> Macros/HTM
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)?
>
In French, guille
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 openi
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 quo
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 apostrop
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
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.
> http://www.lyx.org/trac/ti
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
reli
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 the LaTeX file and to
>
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 double
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
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 eventu
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 question/interrogation mar
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 Single
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 quotes":
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
61 matches
Mail list logo
