Abdelrazak Younes wrote:
Jürgen Spitzmüller wrote:
If we had access to something like python's unicodedata in C++, we
could also add nice tooltips displaying the name of the glyph.
Ideas welcome.
Ideas in no particular order:
- The information brought by QFontDatabase::writingSystem() seem
Jürgen Spitzmüller wrote:
Jürgen Spitzmüller wrote:
If we allowed all unicode symbols, be it in utf8 inputenc or XeTeX
(which we do not support yet properly), this would ask for trouble,
since neither in inputenc nor with XeTeX you can just insert any
unicode char without further ado.
having
[EMAIL PROTECTED] wrote:
Author: dov
Date: Thu Feb 7 23:46:47 2008
New Revision: 22854
URL: http://www.lyx.org/trac/changeset/22854
Log:
compilation fix
Modified:
lyx-devel/trunk/src/frontends/qt4/GuiSymbols.cpp
Modified: lyx-devel/trunk/src/frontends/qt4/GuiSymbols.cpp
URL:
http://www.l
Pavel Sanda wrote:
I don't know for sure but I guess it should be done within LyX. For Mac,
the method I've outlined above should probably work. I see that Firefox is
able to hide all window decoration under Windows so I guess it is possible
to do it for LyX too.
thats worth studying, becaus
Pavel Sanda wrote:
hi,
i notoriously dont get Abdels commits to my mailbox,
while the others are ok. But i see they are on gmane
so i wonder whats going on. anybode else suffer from
this?
but i dont see them in native mailman archive. Abdel you
are not subscribed to this list?
No I am not.
> hi,
>
> i notoriously dont get Abdels commits to my mailbox,
> while the others are ok. But i see they are on gmane
> so i wonder whats going on. anybode else suffer from
> this?
but i dont see them in native mailman archive. Abdel you
are not subscribed to this list?
pavel
hi,
i notoriously dont get Abdels commits to my mailbox,
while the others are ok. But i see they are on gmane
so i wonder whats going on. anybode else suffer from
this?
pavel
> I don't know for sure but I guess it should be done within LyX. For Mac,
> the method I've outlined above should probably work. I see that Firefox is
> able to hide all window decoration under Windows so I guess it is possible
> to do it for LyX too.
thats worth studying, because firefox is
Jürgen Spitzmüller wrote:
> If we allowed all unicode symbols, be it in utf8 inputenc or XeTeX (which
> we do not support yet properly), this would ask for trouble, since neither
> in inputenc nor with XeTeX you can just insert any unicode char without
> further ado.
having written this, there is
Abdelrazak Younes wrote:
> Imagine that I want to use XeteX and I set the encoding to utf8, I
> should be allowed to access all unicode symbols, independently of the
> unicodesymbols file, which would then be unneeded, right?
I don't think so. I never used XeTeX, but I think you have to declare a
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
Juergen,
It is not clear to me how I can use this dialog. My encodings is set to
"Language Default" so I guess this is "latin-1". If I want to use
characters not in this subset, do I have to set the document encoding to
'utf8'? Or is this langu
I'm currently writing a thesis with many sub sections and am tired of figuring
out when I create a new section whether it is a Chapter, Section, Subsection or
Subsubsection etc, and then I'm even more tired of finding it in the list and
having to be careful to chose the numbered or unnumbered on
On Thu, Feb 07, 2008 at 09:40:16AM +0100, [EMAIL PROTECTED] wrote:
> Hi,
>
> I'd like to suggest that we add a step to the release procedure, namely
> that we generate the documentation as PDFs. I've prepared a location for
> these files in a directory structure on aussie under the directory
>
>
Abdelrazak Younes wrote:
> Juergen,
>
> It is not clear to me how I can use this dialog. My encodings is set to
> "Language Default" so I guess this is "latin-1". If I want to use
> characters not in this subset, do I have to set the document encoding to
> 'utf8'? Or is this language dependent? But
Juergen,
It is not clear to me how I can use this dialog. My encodings is set to
"Language Default" so I guess this is "latin-1". If I want to use
characters not in this subset, do I have to set the document encoding to
'utf8'? Or is this language dependent? But why do we limit the symbols
av
José Matos wrote:
On Sunday 03 February 2008 16:09:08 Jürgen Spitzmüller wrote:
I've set up a symbols dialog for trunk. The dialog displays all characters
that can be used in the given encoding (at cursor position), including
those from the unicodesymbols list. It's quite similar to the symbols
On Sunday 03 February 2008 16:09:08 Jürgen Spitzmüller wrote:
> I've set up a symbols dialog for trunk. The dialog displays all characters
> that can be used in the given encoding (at cursor position), including
> those from the unicodesymbols list. It's quite similar to the symbols
> dialogs you k
[EMAIL PROTECTED] wrote:
> correct download dutch dict
status.15x, please.
Jürgen
Edwin Leuven wrote:
> jürgen, what about branch?
put it in.
Jürgen
Uwe Stöhr wrote:
> i suspect something like the attached is needed...
Your patch is obviously correct. Please put it in.
jürgen, what about branch?
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
You should have used QChar::category(c) instead of QChar(c).category().
I'll fix that and commit it with my other cleanup if you don't mind.
yes, go ahead.
I've done that but it seems that there are some bugs with
Dialog::checkStatus(). The
Hi,
Sven, I just read your answer regarding my question on where to download the
latest development version of lyx. I just downloaded the trunk from the svn.
Unfortunately, there are no binaries included. Don't you ever create nightly
builds or something? I haven't got MSVC++ etc. installed on my
Abdelrazak Younes wrote:
> You should have used QChar::category(c) instead of QChar(c).category().
> I'll fix that and commit it with my other cleanup if you don't mind.
yes, go ahead.
Jürgen
Abdelrazak Younes wrote:
You should have used QChar::category(c) instead of QChar(c).category().
I'll fix that and commit it with my other cleanup if you don't mind.
Hum, you also did not take into account potential ucs4 characters, I
corrected that too.
Abdel.
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
I've done that now. Please have a look at it, you will see that you'll
need less code and you'll have a more powerful dialog.
I've done that, but I found it rather clumsy (probably because it didn't fully
understand it). For instance, the but
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
I see that you insisted on implementing initialiseParams() and
clearParams(), that's why. You are still 'tainted' by the serialization
way ;-)
How would the new approach look?
Something like this (untested yet).
Abdel.
Index: GuiSymbols.cpp
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
I see that you insisted on implementing initialiseParams() and
clearParams(), that's why. You are still 'tainted' by the serialization
way ;-)
How would the new approach look?
I am working on it.
Abdel.
Abdelrazak Younes wrote:
> I see that you insisted on implementing initialiseParams() and
> clearParams(), that's why. You are still 'tainted' by the serialization
> way ;-)
How would the new approach look?
Jürgen
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
Right, but in this case I think the whole dialog should be disabled
instead.
No. The dialog can also be used as a ressource of information (about what
symbols are available), which should be possible in a read-only document
(same applies to
Abdelrazak Younes wrote:
> Right, but in this case I think the whole dialog should be disabled
> instead.
No. The dialog can also be used as a ressource of information (about what
symbols are available), which should be possible in a read-only document
(same applies to the paragraph dialog)
Jür
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
I've done that now. Please have a look at it, you will see that you'll
need less code and you'll have a more powerful dialog.
I've done that, but I found it rather clumsy (probably because it didn't fully
understand it).
I see that you insi
I worked through all the distributions from ver1.5.x downwards until I
could reach backward compatibility.
The highest version which could still open all my tables and work
without error was:
Version 1.3.5-1.2
I mention this in case someone want to look at the problem and need the
last work
Abdelrazak Younes wrote:
> I've done that now. Please have a look at it, you will see that you'll
> need less code and you'll have a more powerful dialog.
I've done that, but I found it rather clumsy (probably because it didn't fully
understand it). For instance, the button enabling has to be imp
Which packages do I need to import .doc-files?
--
Viele Grüße,
Hartmut
Hungerhilfe: http://www.thehungersite.com
Kampagne gegen den Ausverkauf der Deutschen Bahn:
http://www.bahn-fuer-alle.de
Das heutige Motto:
Executive ability is prominent in your make-up.
Pavel Sanda wrote:
I guess that keeping trace of the menuBar pointer (via a static variable
outside the ctor) and try to hide it could work.
One has to try...
so to complete this menubar hiddening under mac and window decoration under ms
win
should be done. do you think its part of lyx assig
>> If I remember well, it should be no big deal switching
>> to package subfig. The macro is called \subfloat[...]{...}
>> instead of \subfigure ...
>
> However, we wanted to switch to a collapsable (and proper captions) with
> subfig.
>
> Having said that, I agree that this should be done for 1.6
> I guess that keeping trace of the menuBar pointer (via a static variable
> outside the ctor) and try to hide it could work.
>
> One has to try...
so to complete this menubar hiddening under mac and window decoration under ms
win
should be done. do you think its part of lyx assignment or should
> which probably does what you want. It may make more sense however to
> have a version that requires a reference directory as argument.
just a question .. does this somehow interfere with the new embeding stuff
in 1.6?
pavel
Vasek Smidl <[EMAIL PROTECTED]> writes:
> Yeah, I think it is the latter.
> In changeset/3881 the detection is:
> (IsFileReadable(MakeAbsPath(params().filename, buf->filePath()))
>
> while now it is:
>isFileReadable(params().filename);
>
> So it is checked by a different function, (lowerca
Pavel Sanda <[EMAIL PROTECTED]> writes:
>
> > I came across the situation when some of my older lyx files could no longer
> > compile under new versions of LyX.
Well, the file is about 5 years old, and I haven't tried to compile it since, so
the problem may actually be there quite a long time.
Herbert Voss wrote:
> If I remember well, it should be no big deal switching
> to package subfig. The macro is called \subfloat[...]{...}
> instead of \subfigure ...
However, we wanted to switch to a collapsable (and proper captions) with
subfig.
Having said that, I agree that this should be don
Jean-Marc Lasgouttes schrieb:
Herbert Voss <[EMAIL PROTECTED]> writes:
subfigure is deprecated anmd in the obsolete part of CTAN...
So we are supposed to use subfig instead, right? The manual says that
spacing is different. Anything else to watch out for?
If I remember well, it should be no
Helge Hafting <[EMAIL PROTECTED]> writes:
> Downloaded, did the autogen.sh and configure stuff.
> Compiling:
> make[2]: *** No rule to make target `es/biblio/alphadin.bst', needed
> by `all-am'. Stop.
I do not see that here. Strange.
BTW Uwe, why do we need to distribute this bst file at all? Ar
Andre Poenitz <[EMAIL PROTECTED]> writes:
>> But forwarding spam is a good way to get blacklisted.
>
> Even if each developer forwards his own mail only to a 'safe' account?
Don't know.
JMarc
Herbert Voss <[EMAIL PROTECTED]> writes:
> subfigure is deprecated anmd in the obsolete part of CTAN...
So we are supposed to use subfig instead, right? The manual says that
spacing is different. Anything else to watch out for?
JMarc
Hi,
I'd like to suggest that we add a step to the release procedure, namely
that we generate the documentation as PDFs. I've prepared a location for
these files in a directory structure on aussie under the directory
/home/lyx/www/pmwiki/uploads/LyX/Documentation
This directory struct
Uwe Stöhr wrote:
> Nice idea. I committed it (http://www.lyx.org/trac/changeset/22811). What
> about branch? With this we are now ready to add the examples files, I
> think.
Yes, you can add this to branch as well.
Jürgen
Uwe Stöhr wrote:
> There was a bug in there: "wrapfig" must be loaded after "float".
> Attached is the corrected patch.
looks good.
Jürgen
48 matches
Mail list logo
