> ... the button will go "dead" and not respond to
> mouse-over anymore. And you see that _only_ the paragraph the text
> cursor is in, gets repainted.
Good catch. I will have a look.
This is fixed now. I also made the buttonframe the same color as
button background since these two colors do n
On Wed, Dec 06, 2006 at 04:30:09PM +0100, Jean-Marc Lasgouttes wrote:
> > "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
> >> I would be very interested, but I will need a windows user to do
> >> that for me, since I cannot really test. Anyway caching ascent and
> >> descent looks l
Normally when you move the mouse over the button, it will change colour
when moving in / moving out, as intended. At the same time you see
(debug output) how every visible paragraph is repainted.
I intended to use single-paragraph repaint, but this was proved
impossible right now. A lots of repa
there were some complaints about the bulletpanel in Status.15x:
* The UI for bullet selection in the documents settings looks weird
(Joost 4/11/06):
There is a big listbox just to select one of the four levels.
Isn't this supposed to be a drop-down list or something like that?
* The bullet
> You should be more confident in the python capabilities:
>
> http://plastex.sourceforge.net/
I had a look (without actually running anything) at plastex today and it
looks pretty good. It's probably even closer to a real TeX parser than
tex2lyx.
It indeed looks promising. It sounds like all w
Trying out the new button look, I run into the following bug:
Normally when you move the mouse over the button, it will change colour
when moving in / moving out, as intended. At the same time you see
(debug output) how every visible paragraph is repainted.
However, if you do the following: 1) g
On Wednesday 06 December 2006 6:23 pm, Andre Poenitz wrote:
> Somewhere in a forest in Poland with not enough non-fish food for a few
> days...
Pragmatic, as always. :-)
That is why I like to meet other developers, I would not fully understand
what you said unless I knew you face to face. :-
Andre Poenitz wrote:
On Tue, Dec 05, 2006 at 09:09:03PM +0100, Georg Baum wrote:
Am Dienstag, 5. Dezember 2006 18:18 schrieb Andre Poenitz:
Couldn't we introduce some convenience functions here?
if (orig_from_name.exists())) {
Yes. I did not do it so far because we have too man
On Tue, Dec 05, 2006 at 09:09:03PM +0100, Georg Baum wrote:
> Am Dienstag, 5. Dezember 2006 18:18 schrieb Andre Poenitz:
> > Couldn't we introduce some convenience functions here?
> >
> > if (orig_from_name.exists())) {
>
> Yes. I did not do it so far because we have too many convenie
On Sun, Dec 03, 2006 at 02:46:56AM +, Enrico Forestieri wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> > But you understand that lyx2lyx reads LyX format whereas tex2lyx reads
> > .tex and that _reading_ is the difficult part?
>
> You should be more confident in the python capabilitie
On Tue, Dec 05, 2006 at 08:07:03PM +, José Matos wrote:
> On Tuesday 05 December 2006 6:58 pm, Andre Poenitz wrote:
> > Andre', who has been seen eating fish.
>
> Now I am impressed. Honestly. ;-)
Somewhere in a forest in Poland with not enough non-fish food for a few
days...
Andre'
[EMAIL PROTECTED] wrote:
It sounds like there are some potential areas where some caching could
take place and since QFontMetrics is heavily used it may have a
postitive effect overall so I've created task 142225 for our developers
who will look into this further. You can track this task using t
Looks like Qt will do the caching itself in the future.
Abdel.
--- Begin Message ---
Hi Abdel,
On Monday, 04. des 2006 22:00 Abdelrazak Younes wrote:
> > We do some caching, but it is not possible to cache the results of
> > width() and boundingRect() as these values are dependent on the text
On Wednesday 06 December 2006 4:37 pm, Juergen Spitzmueller wrote:
> Juergen Spitzmueller wrote:
> > > Do we need any special package to support them? I guess not but I am
> > > just asking.
> >
> > Most of them are covered by textcomp, AFAICS.
>
> In fact, _all_ of them are covered by textcomp,
Juergen Spitzmueller wrote:
> You're right, I mixed up things completely. Attached is the correct patch,
> which allows the use of € for all encodings.
Committed (with corrected column count, thanks to Stephan Witt p.c.)
Jürgen
Juergen Spitzmueller wrote:
> > Do we need any special package to support them? I guess not but I am
> > just asking.
>
> Most of them are covered by textcomp, AFAICS.
In fact, _all_ of them are covered by textcomp, so adding support will be a
breeze. And BTW, they were not supported until now
On Wed, Dec 06, 2006 at 03:27:52PM +, José Matos wrote:
> On Wednesday 06 December 2006 12:55 pm, Jean-Marc Lasgouttes wrote:
> >
> > At least french will want it too.
>
> And if we go that way Portuguese as well.
Also add italian to the list.
--
Enrico
José Matos wrote:
> I would prefer 2). Unless someone has a real reason against.
OK. I'll wait a few days and apply then if there are no objections.
> Do we have support for the other characters available in latin1 but not
> in latin9?
Not yet.
> Do we need any special package to support th
> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
>> I would be very interested, but I will need a windows user to do
>> that for me, since I cannot really test. Anyway caching ascent and
>> descent looks like a good idea.
Enrico> Jean-Marc are you looking at this? I had a quick loo
On Wednesday 06 December 2006 12:55 pm, Jean-Marc Lasgouttes wrote:
>
> At least french will want it too.
And if we go that way Portuguese as well.
> JMarc
--
José Abílio
On Wednesday 06 December 2006 2:05 pm, Juergen Spitzmueller wrote:
> Georg Baum wrote:
> > > So this change would be OK in principle?
> >
> > With me yes.
>
> So José, what is your take on this? We have two options now:
> 1. Do the change for those languages where we have positive feedback from a
>
Enrico> Doh! They resemble the same kind of buttons chimera had, if
Enrico> someone remembers that ancient browser ;-)
Modern or ancient, who knows? :-) Anyway, calling them buttons was not
appropriate in the first place since these things (?) contain
typesetting information, and the operations
Georg Baum wrote:
> > So this change would be OK in principle?
>
> With me yes.
So José, what is your take on this? We have two options now:
1. Do the change for those languages where we have positive feedback from a
user, that is (by now): the German variants, French, Norwegian, and leave the
On Fri, Dec 01, 2006 at 10:40:59PM +0100, Jean-Marc Lasgouttes wrote:
> > "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>
> Abdelrazak> Good news for Windows and Mac users, this bug is now
> Abdelrazak> fixed: http://bugzilla.lyx.org/show_bug.cgi?id=2900
>
> Abdelrazak> Jean-M
Juergen Spitzmueller wrote:
> Don't get me wrong, I appreciate your expertise, the more so as you have
> the most knowledge in this area. So I was just wondering why you are
> wondering ;-)
Only general caution, because I have been bitten by seemingly simple changes
that turned out to have more i
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> (but if you insist, I'll change only the German varieties and
Juergen> leave the others to their users).
At least french will want it too.
JMarc
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Juergen Spitzmueller wrote:
>> iso8859-1 has the EURO sign (while iso8859-1 doesn't;
Juergen> _iso8859-15_ has the EURO sign (while iso8859-1 doesn't;
And it has \oe too.
JMarc
Georg Baum wrote:
> Juergen Spitzmueller wrote:
> > (but if you insist, I'll change only the German varieties and leave the
> > others to their users).
>
> I don't insist, I was just wondering. If you like to change all languages
> please go ahead.
Don't get me wrong, I appreciate your expertise,
I strongly recommend to replace the default entry of
Tools->Preferences->Converters->"LaTeX (plain) -> HTML"->Converter:
htlatex $$i
by
htlatex $$i '' 'symbol/!'
because then special characters will be automatically converted into something
like unicode, e. g. ä ==> ä
This can be interpreted by
Helge Hafting wrote:
> I was thinking of opening old documents with the new lyx, but
> I guess lyx won't change the encoding of old documents then?
It will (not really, lyx2lyx will do that), but at the same time the
document contents will be converted from the old encoding to utf8.
> User's wou
Georg Baum wrote:
latin9 is just another name for iso8859-15.
Good, I misunderstood then. Thanks for explaining.
Oh well, latin9 don't seem to loose us anything useful.
Perhaps lyx2lyx should convert any "3/4" "1/4" and "1/2" glyphs to
nicefrac though?
That falls in the "try to be t
Helge Hafting wrote:
> Just wonder why we don't go for iso8859-15, which is supposed to be
> iso8859-1 with the euro added. Or is latex support for iso8859-15
> weaker?
latin9 is just another name for iso8859-15.
> Oh well, latin9 don't seem to loose us anything useful.
> Perhaps lyx2lyx shoul
Juergen Spitzmueller wrote:
> (but if you insist, I'll change only the German varieties and leave the
> others to their users).
I don't insist, I was just wondering. If you like to change all languages
please go ahead.
>> Unfortunately this change does also affect the conversion from pre
>> unic
On Sun, Dec 03, 2006 at 01:00:08AM +0100, Enrico Forestieri wrote:
> On Sat, Dec 02, 2006 at 10:08:15PM +0100, Georg Baum wrote:
>
> > Am Samstag, 2. Dezember 2006 17:01 schrieb John Levon:
> > > On Sat, Dec 02, 2006 at 05:00:33PM +0100, Enrico Forestieri wrote:
> > >
> > > > > That is OK with me
Juergen Spitzmueller wrote:
Georg Baum wrote:
I am not sure whether it is a good idea to do the change for all languages,
since the euro sign is not the only change in latin1 vs. latin9.
I know. But the changes are still marginal:
http://www.cs.tut.fi/~jkorpela/latin9.html
I woul
Juergen Spitzmueller wrote:
> What do you have in mind? A file format change? I don't see another way to
> decide which encoding was actually used. And how do you handle the case
> where a user changed the languages file himself (which several have done to
> get the euro afaik)? And if he sends me
Georg Baum wrote:
> I am not sure whether it is a good idea to do the change for all languages,
> since the euro sign is not the only change in latin1 vs. latin9.
I know. But the changes are still marginal:
http://www.cs.tut.fi/~jkorpela/latin9.html
> I would prefer to ask native speakers.
This
Juergen Spitzmueller wrote:
> iso8859-1 has the EURO sign (while iso8859-1 doesn't;
_iso8859-15_ has the EURO sign (while iso8859-1 doesn't;
Jürgen
Juergen Spitzmueller wrote:
> Juergen Spitzmueller wrote:
>> > We should do it, especially since it can be overridden now.
>>
>> Good. I'll prepare a separate patch.
>
> Attached is the patch against languages.
I am not sure whether it is a good idea to do the change for all languages,
since the
Martin Vermeer wrote:
> Remind me what is the rationale for this? iso8859-1 works well for me.
iso8859-1 has the EURO sign (while iso8859-1 doesn't; it has a general and
less useful "currency" symbol at that code point).
Jürgen
On Wed, Dec 06, 2006 at 11:22:22AM +0100, Juergen Spitzmueller wrote:
> Juergen Spitzmueller wrote:
> > > We should do it, especially since it can be overridden now.
> >
> > Good. I'll prepare a separate patch.
>
> Attached is the patch against languages. There are also some places in the
> sourc
Juergen Spitzmueller wrote:
> > We should do it, especially since it can be overridden now.
>
> Good. I'll prepare a separate patch.
Attached is the patch against languages. There are also some places in the
source where iso8859-1 is declared as default language (e.g. lyxrc.C and
language.C). Sh
Georg Baum wrote:
> I don't understand that logic. I always thought that you could directly
> enter the euro symbol as a character if you use latin9, so why do you
> output \texteuro? I would expect to output \texteuro for all encodings
> except of latin9, cp1251 and utf8.
You're right, I mixed up
Juergen Spitzmueller wrote:
> Index: src/paragraph_pimpl.C
> ===
> --- src/paragraph_pimpl.C(Revision 16185)
> +++ src/paragraph_pimpl.C(Arbeitskopie)
> @@ -651,6 +651,21 @@ void Paragraph::Pimpl::simpleTeXSpecialC
>
> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
Enrico> On Wed, Dec 06, 2006 at 01:52:57PM +1800, Bo Peng wrote:
>> >I am not saying this is bad, but this is surely changed behaviour.
>>
>> The original button is some sort of 3-D button. Now it is a simple
>> frame. Depending on p
Jean-Marc Lasgouttes wrote:
> We should do it, especially since it can be overridden now.
Good. I'll prepare a separate patch.
Jürgen
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> José Matos wrote:
>> > What do others think about this?
>>
>> Since is not too complicate the fix should go before 1.5.
Juergen> Thanks. However, I meant the switch from latin1 to latin9 as
Juergen> default for the co
Georg Baum wrote:
> getChar(i) == 0x20ac
Many thanks, Georg. Here's the patch.
Still missing is chkconfig.ltx and LaTeXConfig.lyx stuff. I'll add those.
OK to commit?
Jürgen
Index: src/LaTeXFeatures.C
===
--- src/LaTeXFeatures.C (Re
Juergen Spitzmueller wrote:
> I found out in the meantime, and I found out that I used the wrong code
> point (it's 0x20ac). The LaTeXFeatures.C thing is clear, I only have to
> figure out now how to detect in validate that we entered a euro sign.
In the last loop, just below the comment
// then
José Matos wrote:
> > What do others think about this?
>
> Since is not too complicate the fix should go before 1.5.
Thanks. However, I meant the switch from latin1 to latin9 as default for the
concerned languages (which can be done in a separate step).
Jürgen
On Wednesday 06 December 2006 9:25 am, Juergen Spitzmueller wrote:
> What do others think about this?
Since is not too complicate the fix should go before 1.5.
> Jürgen
--
José Abílio
Georg Baum wrote:
> That does not work. You need to require it in Paragraph::Pimpl::validate,
> and you need to add textcomp to the simplefeatures list in
> src/LaTeXFeatures.C. Both has nothing to do with unicode!
I found out in the meantime, and I found out that I used the wrong code point
(it'
Juergen Spitzmueller wrote:
> I had a look today what is missing: basically, entering and latexing €
> works with utf8, latin9 and cp1251 (also latin10 and others in theory, but
> they're not in the combo), provided that \usepackage{textcomp} is entered
> manually to the preamble.
>
> I tried to
53 matches
Mail list logo
