Re: Closing quote fubar ?
On Sun, Feb 16, 2003 at 02:06:39PM +0100, Jean-Marc Lasgouttes wrote: John Levon a ?crit: On Fri, Feb 14, 2003 at 03:58:52PM +0100, Jean-Marc Lasgouttes wrote: Because it thinks you use latin1 whereas you really use latin9. So how do we fix it ? I'm stuck. If this char isn't even in latin9 We could test against the current language's encoding. I can do that if you want. InsetLatexAccent::draw can set the language of the font to any language it likes, so if it wants to draw an iso8859-2 char, it can change to an appropriate language. This must require defining dummy languages in languages.C. So this is a mess. The solution: use unicode internally.
Re: Closing quote fubar ?
On Sun, Feb 16, 2003 at 02:06:39PM +0100, Jean-Marc Lasgouttes wrote: > John Levon a ?crit: > >On Fri, Feb 14, 2003 at 03:58:52PM +0100, Jean-Marc Lasgouttes wrote: > > > >>Because it thinks you use latin1 whereas you really use latin9. > > > > > >So how do we fix it ? I'm stuck. If this char isn't even in latin9 > > We could test against the current language's encoding. I can do that if > you want. InsetLatexAccent::draw can set the language of the font to any language it likes, so if it wants to draw an iso8859-2 char, it can change to an appropriate language. This must require defining dummy languages in languages.C. So this is a mess. The solution: use unicode internally.
Re: Closing quote fubar ?
John Levon a écrit: On Fri, Feb 14, 2003 at 03:58:52PM +0100, Jean-Marc Lasgouttes wrote: Because it thinks you use latin1 whereas you really use latin9. So how do we fix it ? I'm stuck. If this char isn't even in latin9 We could test against the current language's encoding. I can do that if you want. Note that font_norm_type is also used in text.C and insetlatexaccent.C. You should maybe take a look at what happens there. Why isn't this set from the language, and how come the user can't set it from the GUI ? I would have thought it was you who decided it should not be set from the GUI (prefs)... I don't really follow what it does. It gives the encoding of the font used on screen with xforms. JMarc
Re: Closing quote fubar ?
On Sun, Feb 16, 2003 at 02:06:39PM +0100, Jean-Marc Lasgouttes wrote: So how do we fix it ? I'm stuck. If this char isn't even in latin9 We could test against the current language's encoding. I can do that if you want. Yes please, maybe I will earn a clue. Why isn't this set from the language, and how come the user can't set it from the GUI ? I would have thought it was you who decided it should not be set from the GUI (prefs)... Not me - it's not in FormPreferences either. It gives the encoding of the font used on screen with xforms. So I don't think it can really apply to Qt, where we use the language's encoding already for display (except in the cases mentioned already ...) john
Re: Closing quote fubar ?
John Levon a écrit: On Sun, Feb 16, 2003 at 02:06:39PM +0100, Jean-Marc Lasgouttes wrote: So how do we fix it ? I'm stuck. If this char isn't even in latin9 We could test against the current language's encoding. I can do that if you want. Yes please, maybe I will earn a clue. Hmm, maybe is it not as easy as I thought, after all :) I'll have to think more about it. I would have thought it was you who decided it should not be set from the GUI (prefs)... Not me - it's not in FormPreferences either. It will be soon :) This is a bug. Actually, font_norm_type is an enum version of LyXRC::font_norm. And the string version is also used in several places for xforms. So I don't think it can really apply to Qt, where we use the language's encoding already for display (except in the cases mentioned already ...) Indeed. So what would be the qt way to know whether a symbol exists in the current font? JMarc
Re: Closing quote fubar ?
On Sun, Feb 16, 2003 at 04:37:48PM +0100, Jean-Marc Lasgouttes wrote: So I don't think it can really apply to Qt, where we use the language's encoding already for display (except in the cases mentioned already ...) Indeed. So what would be the qt way to know whether a symbol exists in the current font? I don't think there's anything like that. Of course, the unicode fonts will likely *have* it, but we cannot *encode* it. john
Re: Closing quote fubar ?
John Levon a écrit: On Fri, Feb 14, 2003 at 03:58:52PM +0100, Jean-Marc Lasgouttes wrote: Because it thinks you use latin1 whereas you really use latin9. So how do we fix it ? I'm stuck. If this char isn't even in latin9 We could test against the current language's encoding. I can do that if you want. Note that font_norm_type is also used in text.C and insetlatexaccent.C. You should maybe take a look at what happens there. Why isn't this set from the language, and how come the user can't set it from the GUI ? I would have thought it was you who decided it should not be set from the GUI (prefs)... I don't really follow what it does. It gives the encoding of the font used on screen with xforms. JMarc
Re: Closing quote fubar ?
On Sun, Feb 16, 2003 at 02:06:39PM +0100, Jean-Marc Lasgouttes wrote: > >So how do we fix it ? I'm stuck. If this char isn't even in latin9 > > We could test against the current language's encoding. I can do that if > you want. Yes please, maybe I will earn a clue. > >Why isn't this set from the language, and how come the user can't set it > >from the GUI ? > > I would have thought it was you who decided it should not be set from > the GUI (prefs)... Not me - it's not in FormPreferences either. > It gives the encoding of the font used on screen with xforms. So I don't think it can really apply to Qt, where we use the language's encoding already for display (except in the cases mentioned already ...) john
Re: Closing quote fubar ?
John Levon a écrit: On Sun, Feb 16, 2003 at 02:06:39PM +0100, Jean-Marc Lasgouttes wrote: So how do we fix it ? I'm stuck. If this char isn't even in latin9 We could test against the current language's encoding. I can do that if you want. Yes please, maybe I will earn a clue. Hmm, maybe is it not as easy as I thought, after all :) I'll have to think more about it. I would have thought it was you who decided it should not be set from the GUI (prefs)... Not me - it's not in FormPreferences either. It will be soon :) This is a bug. Actually, font_norm_type is an enum version of LyXRC::font_norm. And the string version is also used in several places for xforms. So I don't think it can really apply to Qt, where we use the language's encoding already for display (except in the cases mentioned already ...) Indeed. So what would be the qt way to know whether a symbol exists in the current font? JMarc
Re: Closing quote fubar ?
On Sun, Feb 16, 2003 at 04:37:48PM +0100, Jean-Marc Lasgouttes wrote: > >So I don't think it can really apply to Qt, where we use the language's > >encoding already for display (except in the cases mentioned already ...) > > Indeed. So what would be the qt way to know whether a symbol exists in > the current font? I don't think there's anything like that. Of course, the unicode fonts will likely *have* it, but we cannot *encode* it. john
Re: Closing quote fubar ?
On Fri, Feb 14, 2003 at 03:58:52PM +0100, Jean-Marc Lasgouttes wrote: Because it thinks you use latin1 whereas you really use latin9. So how do we fix it ? I'm stuck. If this char isn't even in latin9 Note that font_norm_type is also used in text.C and insetlatexaccent.C. You should maybe take a look at what happens there. Why isn't this set from the language, and how come the user can't set it from the GUI ? I don't really follow what it does. john
Re: Closing quote fubar ?
On Fri, Feb 14, 2003 at 03:58:52PM +0100, Jean-Marc Lasgouttes wrote: > Because it thinks you use latin1 whereas you really use latin9. So how do we fix it ? I'm stuck. If this char isn't even in latin9 > Note that font_norm_type is also used in text.C and > insetlatexaccent.C. You should maybe take a look at what happens > there. Why isn't this set from the language, and how come the user can't set it from the GUI ? I don't really follow what it does. john
Re: Closing quote fubar ?
-BEGIN PGP SIGNED MESSAGE- On Freitag, 14. Februar 2003 02:06, John Levon wrote: ... Hmm... what quote style? Normal english ones. I do no see it. 1.4.0cvs from yesterday. Kornel - -- Kornel Benko [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 iQCVAwUBPkyvcbewfbDGmeqhAQEQXgQAnhkbKZ1TnO7bAikgksqQUdvyHlDaBrvj NszqoFfBV+rkenjcGdi2XNkUPELn7j8vtNPHsqWK/Wl0UOgv7AzA+HSAKDshwIps 0VHCZ84MsgjEa4M2pVQjY9GCSdAK+K1xDWDFDXffLrlq3olfpqq+AbtIpftGSM1S IMNdJsJwbMk= =svwx -END PGP SIGNATURE- attachment: print.gif
Re: Closing quote fubar ?
On Fri, Feb 14, 2003 at 12:39:28AM +, John Levon wrote: Is this some totally surreal bug in some changes I've made, or is anyone else seeing that the closing smart quote no longer looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? Just confirmed - it happens with clean 1.4.0cvs. Something broke. No it didn't. Using iso-8859-15 in lib/languages breaks it. WTF ?? I thought the only difference between -1 and -15 was the Euro ? It is fun that the user has the choice between a euro, and a sensible closing quote... john
Re: Closing quote fubar ?
-BEGIN PGP SIGNED MESSAGE- On Freitag, 14. Februar 2003 14:30, John Levon wrote: On Fri, Feb 14, 2003 at 12:39:28AM +, John Levon wrote: Is this some totally surreal bug in some changes I've made, or is anyone else seeing that the closing smart quote no longer looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? Just confirmed - it happens with clean 1.4.0cvs. Something broke. No it didn't. Using iso-8859-15 in lib/languages breaks it. WTF ?? I thought the only difference between -1 and -15 was the Euro ? Funny, I _am_ using iso-8859-15 in lib/languages. No such effect, even on freshly compiled qt-lyx. Kornel - -- Kornel Benko [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 iQCVAwUBPkz5HrewfbDGmeqhAQFvgQQAlhdJn7bJ7Pb1jz85lLj5uy694G3+6t0k HnbHH3++4Q62W7s/3fzSRoSFUykk0bZrX6lC3ChRebascABRMHG0i333NB8QpLiu gzKNcIyqq5tK69Admg4J6Bx4ZugIZgEUXRT5X+MTfJQPH357ep9PzNmpnQRMxEaO F2Ke7e5hrVw= =ddwd -END PGP SIGNATURE-
Re: Closing quote fubar ?
-BEGIN PGP SIGNED MESSAGE- On Freitag, 14. Februar 2003 14:30, John Levon wrote: Sorry, I should learn to read mails. Confirmed the effect for _single_ closing. Kornel - -- Kornel Benko [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 iQCVAwUBPkz6JbewfbDGmeqhAQFqHAQAuZu6R20nC+05HdzJiHm1w+66Ff8qjFL1 oKiWxp22ZEItO/qCcEZ5WBVf19JRPrLP8kYy3/6EMafUPuqLLBkPv9pnFyvmm9NI A4Q06Dmx6HYye9Hmpn2OS/FyMsN1pASxfFQhY7LTBHNKT8g4WICKUEOvBcRukd2p dqdfHY+LzQg= =htbB -END PGP SIGNATURE-
Re: Closing quote fubar ?
John == John Levon [EMAIL PROTECTED] writes:
John On Fri, Feb 14, 2003 at 12:39:28AM +, John Levon wrote:
Is this some totally surreal bug in some changes I've made, or
is anyone else seeing that the closing smart quote no longer
looks like a quote in current CVS with Qt frontend, but like 2 Z's
??
Just confirmed - it happens with clean 1.4.0cvs. Something broke.
John No it didn't. Using iso-8859-15 in lib/languages breaks it. WTF
John ??
There is the following code in InsetQuote::dispString():
if (lyxrc.font_norm_type == LyXRC::ISO_8859_1
|| lyxrc.font_norm_type == LyXRC::ISO_8859_3
|| lyxrc.font_norm_type == LyXRC::ISO_8859_4
|| lyxrc.font_norm_type == LyXRC::ISO_8859_9) {
if (disp == ')
disp = ´;
else if (disp == '')
disp = ´´;
}
So we use the quote in 0xB4 if encoding is iso-8859-[1349]. So this
relies on the lyxrc setting. Are you saying that it should rely on the
local encoding of the language? It would be easy (pass , but tell me what you
really want.
I am not sure BTW that this idea of using what is an acute character
for right quote was good. Do you feel it looks good? (the look of it
depends a lot of the font, that's why I ask).
John I thought the only difference between -1 and -15 was the Euro ?
John It is fun that the user has the choice between a euro, and a
John sensible closing quote...
No, look at http://czyborra.com/charsets/iso8859.html#ISO-8859-15
They added some french things (\oe \OE) and finnish too.
What they removed is accents and fractions (½). This means BTW that
the insetlatexaccent will not work with latin9. Probably another
reason why it should not be the default...
JMarc
Re: Closing quote fubar ?
On Fri, Feb 14, 2003 at 03:33:11PM +0100, Jean-Marc Lasgouttes wrote:
John No it didn't. Using iso-8859-15 in lib/languages breaks it. WTF
John ??
There is the following code in InsetQuote::dispString():
if (lyxrc.font_norm_type == LyXRC::ISO_8859_1
|| lyxrc.font_norm_type == LyXRC::ISO_8859_3
|| lyxrc.font_norm_type == LyXRC::ISO_8859_4
|| lyxrc.font_norm_type == LyXRC::ISO_8859_9) {
if (disp == ')
disp = ´;
else if (disp == '')
disp = ´´;
}
So we use the quote in 0xB4 if encoding is iso-8859-[1349]. So this
relies on the lyxrc setting.
Which is not even settable in Qt. If it relies on that, why does change
lib/languages make a difference ?
Are you saying that it should rely on the
local encoding of the language? It would be easy (pass , but tell me what you
really want.
I don't know :(
I am not sure BTW that this idea of using what is an acute character
for right quote was good. Do you feel it looks good? (the look of it
depends a lot of the font, that's why I ask).
I don't think it looks great, no.
What they removed is accents and fractions (½). This means BTW that
the insetlatexaccent will not work with latin9. Probably another
reason why it should not be the default...
Oh, that explains the above then. Bugger.
john
Re: Closing quote fubar ?
John == John Levon [EMAIL PROTECTED] writes: So we use the quote in 0xB4 if encoding is iso-8859-[1349]. So this relies on the lyxrc setting. John Which is not even settable in Qt. If it relies on that, why does John change lib/languages make a difference ? Because it thinks you use latin1 whereas you really use latin9. I am not sure BTW that this idea of using what is an acute character for right quote was good. Do you feel it looks good? (the look of it depends a lot of the font, that's why I ask). John I don't think it looks great, no. So a nice way of fixing the problem will probably be to remove the code altogether :) Anyway, there is still some code for « », and we need to make this one work... Note that font_norm_type is also used in text.C and insetlatexaccent.C. You should maybe take a look at what happens there. JMarc
Re: Closing quote fubar ?
-BEGIN PGP SIGNED MESSAGE- On Freitag, 14. Februar 2003 02:06, John Levon wrote: ... > > Hmm... what quote style? > > Normal english ones. I do no see it. 1.4.0cvs from yesterday. Kornel - -- Kornel Benko [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 iQCVAwUBPkyvcbewfbDGmeqhAQEQXgQAnhkbKZ1TnO7bAikgksqQUdvyHlDaBrvj NszqoFfBV+rkenjcGdi2XNkUPELn7j8vtNPHsqWK/Wl0UOgv7AzA+HSAKDshwIps 0VHCZ84MsgjEa4M2pVQjY9GCSdAK+K1xDWDFDXffLrlq3olfpqq+AbtIpftGSM1S IMNdJsJwbMk= =svwx -END PGP SIGNATURE- <>
Re: Closing quote fubar ?
On Fri, Feb 14, 2003 at 12:39:28AM +, John Levon wrote: > > Is this some totally surreal bug in some changes I've made, > > or is anyone else seeing that the closing smart quote no longer > > looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? > > Just confirmed - it happens with clean 1.4.0cvs. Something broke. No it didn't. Using iso-8859-15 in lib/languages breaks it. WTF ?? I thought the only difference between -1 and -15 was the Euro ? It is fun that the user has the choice between a euro, and a sensible closing quote... john
Re: Closing quote fubar ?
-BEGIN PGP SIGNED MESSAGE- On Freitag, 14. Februar 2003 14:30, John Levon wrote: > On Fri, Feb 14, 2003 at 12:39:28AM +, John Levon wrote: > > > Is this some totally surreal bug in some changes I've made, > > > or is anyone else seeing that the closing smart quote no longer > > > looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? > > > > Just confirmed - it happens with clean 1.4.0cvs. Something broke. > > No it didn't. Using iso-8859-15 in lib/languages breaks it. WTF ?? I > thought the only difference between -1 and -15 was the Euro ? Funny, I _am_ using iso-8859-15 in lib/languages. No such effect, even on freshly compiled qt-lyx. Kornel - -- Kornel Benko [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 iQCVAwUBPkz5HrewfbDGmeqhAQFvgQQAlhdJn7bJ7Pb1jz85lLj5uy694G3+6t0k HnbHH3++4Q62W7s/3fzSRoSFUykk0bZrX6lC3ChRebascABRMHG0i333NB8QpLiu gzKNcIyqq5tK69Admg4J6Bx4ZugIZgEUXRT5X+MTfJQPH357ep9PzNmpnQRMxEaO F2Ke7e5hrVw= =ddwd -END PGP SIGNATURE-
Re: Closing quote fubar ?
-BEGIN PGP SIGNED MESSAGE- On Freitag, 14. Februar 2003 14:30, John Levon wrote: Sorry, I should learn to read mails. Confirmed the effect for _single_ closing. Kornel - -- Kornel Benko [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 iQCVAwUBPkz6JbewfbDGmeqhAQFqHAQAuZu6R20nC+05HdzJiHm1w+66Ff8qjFL1 oKiWxp22ZEItO/qCcEZ5WBVf19JRPrLP8kYy3/6EMafUPuqLLBkPv9pnFyvmm9NI A4Q06Dmx6HYye9Hmpn2OS/FyMsN1pASxfFQhY7LTBHNKT8g4WICKUEOvBcRukd2p dqdfHY+LzQg= =htbB -END PGP SIGNATURE-
Re: Closing quote fubar ?
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> On Fri, Feb 14, 2003 at 12:39:28AM +, John Levon wrote:
>> > Is this some totally surreal bug in some changes I've made, > or
>> is anyone else seeing that the closing smart quote no longer >
>> looks like a quote in current CVS with Qt frontend, but like 2 Z's
>> ??
>>
>> Just confirmed - it happens with clean 1.4.0cvs. Something broke.
John> No it didn't. Using iso-8859-15 in lib/languages breaks it. WTF
John> ??
There is the following code in InsetQuote::dispString():
if (lyxrc.font_norm_type == LyXRC::ISO_8859_1
|| lyxrc.font_norm_type == LyXRC::ISO_8859_3
|| lyxrc.font_norm_type == LyXRC::ISO_8859_4
|| lyxrc.font_norm_type == LyXRC::ISO_8859_9) {
if (disp == "'")
disp = "´";
else if (disp == "''")
disp = "´´";
}
So we use the quote in 0xB4 if encoding is iso-8859-[1349]. So this
relies on the lyxrc setting. Are you saying that it should rely on the
local encoding of the language? It would be easy (pass , but tell me what you
really want.
I am not sure BTW that this idea of using what is an acute character
for right quote was good. Do you feel it looks good? (the look of it
depends a lot of the font, that's why I ask).
John> I thought the only difference between -1 and -15 was the Euro ?
John> It is fun that the user has the choice between a euro, and a
John> sensible closing quote...
No, look at http://czyborra.com/charsets/iso8859.html#ISO-8859-15
They added some french things (\oe \OE) and finnish too.
What they removed is accents and fractions (½). This means BTW that
the insetlatexaccent will not work with latin9. Probably another
reason why it should not be the default...
JMarc
Re: Closing quote fubar ?
On Fri, Feb 14, 2003 at 03:33:11PM +0100, Jean-Marc Lasgouttes wrote:
> John> No it didn't. Using iso-8859-15 in lib/languages breaks it. WTF
> John> ??
>
> There is the following code in InsetQuote::dispString():
>
> if (lyxrc.font_norm_type == LyXRC::ISO_8859_1
> || lyxrc.font_norm_type == LyXRC::ISO_8859_3
> || lyxrc.font_norm_type == LyXRC::ISO_8859_4
> || lyxrc.font_norm_type == LyXRC::ISO_8859_9) {
> if (disp == "'")
> disp = "´";
> else if (disp == "''")
> disp = "´´";
> }
>
> So we use the quote in 0xB4 if encoding is iso-8859-[1349]. So this
> relies on the lyxrc setting.
Which is not even settable in Qt. If it relies on that, why does change
lib/languages make a difference ?
> Are you saying that it should rely on the
> local encoding of the language? It would be easy (pass , but tell me what you
> really want.
I don't know :(
> I am not sure BTW that this idea of using what is an acute character
> for right quote was good. Do you feel it looks good? (the look of it
> depends a lot of the font, that's why I ask).
I don't think it looks great, no.
> What they removed is accents and fractions (½). This means BTW that
> the insetlatexaccent will not work with latin9. Probably another
> reason why it should not be the default...
Oh, that explains the above then. Bugger.
john
Re: Closing quote fubar ?
> "John" == John Levon <[EMAIL PROTECTED]> writes: >> So we use the quote in 0xB4 if encoding is iso-8859-[1349]. So this >> relies on the lyxrc setting. John> Which is not even settable in Qt. If it relies on that, why does John> change lib/languages make a difference ? Because it thinks you use latin1 whereas you really use latin9. >> I am not sure BTW that this idea of using what is an acute >> character for right quote was good. Do you feel it looks good? (the >> look of it depends a lot of the font, that's why I ask). John> I don't think it looks great, no. So a nice way of fixing the problem will probably be to remove the code altogether :) Anyway, there is still some code for « », and we need to make this one work... Note that font_norm_type is also used in text.C and insetlatexaccent.C. You should maybe take a look at what happens there. JMarc
Closing quote fubar ?
Is this some totally surreal bug in some changes I've made, or is anyone else seeing that the closing smart quote no longer looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? john
Re: Closing quote fubar ?
On Thu, Feb 13, 2003 at 10:03:26PM +, John Levon wrote: Is this some totally surreal bug in some changes I've made, or is anyone else seeing that the closing smart quote no longer looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? Just confirmed - it happens with clean 1.4.0cvs. Something broke. john
Re: Closing quote fubar ?
John Levon [EMAIL PROTECTED] writes: | On Thu, Feb 13, 2003 at 10:03:26PM +, John Levon wrote: | | Is this some totally surreal bug in some changes I've made, | or is anyone else seeing that the closing smart quote no longer | looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? | | Just confirmed - it happens with clean 1.4.0cvs. Something broke. Hmm... what quote style? if («») and some utf8 locale then it could be rendered completely wrong. But I guess that would be a bit way off... It seems to only exist in the qt frontend. I do not see this with xforms. -- Lgb
Re: Closing quote fubar ?
On Fri, Feb 14, 2003 at 01:46:29AM +0100, Lars Gullik Bj?nnes wrote: John Levon [EMAIL PROTECTED] writes: | On Thu, Feb 13, 2003 at 10:03:26PM +, John Levon wrote: | | Is this some totally surreal bug in some changes I've made, | or is anyone else seeing that the closing smart quote no longer | looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? | | Just confirmed - it happens with clean 1.4.0cvs. Something broke. Hmm... what quote style? Normal english ones. if («») and some utf8 locale then it could be rendered completely wrong. But I guess that would be a bit way off... This has broken since 1.4.0cvs branched. My 1.3.0 build does not show the error. I'm not sure what change has caused this. It seems to only exist in the qt frontend. I do not see this with xforms. Same here. regards john
Closing quote fubar ?
Is this some totally surreal bug in some changes I've made, or is anyone else seeing that the closing smart quote no longer looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? john
Re: Closing quote fubar ?
On Thu, Feb 13, 2003 at 10:03:26PM +, John Levon wrote: > Is this some totally surreal bug in some changes I've made, > or is anyone else seeing that the closing smart quote no longer > looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? Just confirmed - it happens with clean 1.4.0cvs. Something broke. john
Re: Closing quote fubar ?
John Levon <[EMAIL PROTECTED]> writes: | On Thu, Feb 13, 2003 at 10:03:26PM +, John Levon wrote: | | > Is this some totally surreal bug in some changes I've made, | > or is anyone else seeing that the closing smart quote no longer | > looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? | | Just confirmed - it happens with clean 1.4.0cvs. Something broke. Hmm... what quote style? if << >> («») and some utf8 locale then it could be rendered completely wrong. But I guess that would be a bit way off... It seems to only exist in the qt frontend. I do not see this with xforms. -- Lgb
Re: Closing quote fubar ?
On Fri, Feb 14, 2003 at 01:46:29AM +0100, Lars Gullik Bj?nnes wrote: > John Levon <[EMAIL PROTECTED]> writes: > > | On Thu, Feb 13, 2003 at 10:03:26PM +, John Levon wrote: > | > | > Is this some totally surreal bug in some changes I've made, > | > or is anyone else seeing that the closing smart quote no longer > | > looks like a quote in current CVS with Qt frontend, but like 2 Z's ?? > | > | Just confirmed - it happens with clean 1.4.0cvs. Something broke. > > Hmm... what quote style? Normal english ones. > > if << >> («») and some utf8 locale then it could be rendered > completely wrong. But I guess that would be a bit way off... This has broken since 1.4.0cvs branched. My 1.3.0 build does not show the error. I'm not sure what change has caused this. > It seems to only exist in the qt frontend. I do not see this with > xforms. Same here. regards john
