Re: mathed110.diff
On Fri, Aug 03, 2001 at 06:37:06PM +0200, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | > Why are you removing {} when I try to add them?
> |
> | I did not see you adding anything.
>
> I am on a small campaign to add more {} espaecially for the
> "if-one-liners" and also for "for" and "while", while I am at it.
I've already warned you your compaign means nothing if you don't
change the coding style document !
;)
john
--
"They didn't know what the symbols and paradoxes meant. Instead of following
the finger that points to the moon, they sat down and worshipped the finger
itself. Instead of following the map, they thought it was the territory and
tried to live in it. Instead of reading the menu they tried to eat it. Dig ?"
- Miss Portinari
Re: XML configuration
Jose Abilio Oliveira Matos a écrit : > [...] > > > I will try to see how to use it to detect where the NW's DocBook XSLs are for the > > db2lyx config (same as the java catalog classes use). > > Good. I've written this small C program to resolve ids from catalogs. It shows that with xml2/xslt we don't need any java stuff, for the configuration and for the running time. > > And you, have you tried to use any XSLT on your machine? > > It took me most of this week to update my computer (I had to reorder the > partition table, and so), I will test it as soon as I come from vacations. I > will also add db2lyx to CVS repository. There is some work to be done to > integrate the configure part, but not too much hopefully... > > My root partition was almost full so I didn't had any left space to > install any new package. Glups... Reinstall is a nightmare for me. > -- > José BG catresolve.tar.gz
russian po-file
I had done to retranslate internationalization file ru.po for russian language. It compatible now with LyX version 1.1.6fix3. Please take it for commit from http://null.ru/people/lyx/ru.po.gz I should like to translate it in future for version 1.2.0 and so on. Also there is corrected keyboard map at http://null.ru/people/lyx/koi8-r.kmap.gz It corrected for last standart "de facto" of russian keyboard layout. -- Lav GNU! Linux! LaTeX! LyX! -- Lav Vitaly Lipatov GNU! Linux! LaTeX! LyX!
Re: serbian.kmap
Vladimir Vrzic wrote:
>
> Also, I have a question: is it possible to make the keymap in such way
> that some keys that are usually not capslock-sensitive become
> capslock-sensitive ("[", "]", "\" for example)?
Simply use Shift_Lock instead of Caps_Lock, for example I have the
following lines in my ~/.Xmodmap:
keysym Num_Lock = Shift_Lock
add Lock = Shift_Lock
So I can use the NumLock key to toggle keypad mode and to lock the
shift mode.
-- marcenuc
Re: [ANNOUNCE] LyX 1.1.6fix2
On Sun, May 27, 2001 at 08:07:00AM -0700, Kayvan A. Sylvan wrote: > > Is there an rpm2deb utility somewhere? http://kitenet.net/programs/alien/ -- marcenuc
Re: Math Editor
Am Freitag, 3. August 2001 13:23 schrieb Dekel Tsur: > On Fri, Aug 03, 2001 at 12:30:01PM +0200, Jean-Marc Lasgouttes wrote: > > > "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes: > > >> > > >> There is one minor thing, which is somewhat inconvenient (but I > > >> think easy to fix): I know the latex code of a lot of math symbols > > >> displayed by lyx, but not all of them. Thus I have to use the math > > >> panel for only a single symbol in a formula. I think it would be > > >> very useful, if the latex code of the symbol would be displayed as > > >> a hint, if the mouse positioned over it. > > > > Andre> I put it on the list, but don't expect a solution soon... > > Andre> Do we have such "hints" somewhere else in LyX? > > > > What we have is the tooltips on the toolbar and the help in > > preferences. What you could do however is display the name of the > > symbol in the minibuffer when it is inserted from math panel. > > We already do this. > > (however, the minibuffer code is currently broken in CVS). I am using lyx1.1.6fix3. Wow, I it works! I simply did not notice this. Andre, you may really put it with low priority on your list, it may only improve the GUI not the functionality. Thanks. Rainer.
Re: compiling lyx
On Thu, Aug 02, 2001 at 11:28:01AM +0200, Edwin Leuven wrote:
> ps. yes I can use the rpm.
>
> pps. but I like to replace
>
> \begin{tabular}{
>
> with
>
> \begin{tabular*}{\textwidth}{@{\extracolsep{\fill}}
>
> in the source so that my tables line out on the textwidth.
Why changing the LyX source ??
You can just put
\renewenvironment{tabular}[1]
{\begin{tabular*}{\columnwidth}{@{\extracolsep{\fill}}#1}}
{\end{tabular*}}
in the preamble.
Re: Management of bug reports
On Thu, Aug 02, 2001 at 04:37:34PM +0200, Andre Poenitz wrote: > > this is perfectly acceptable for you to do this as a bug reporter. Any > > bugs that last will hopefully end up on the tracker via me (that's /my/ > > job) > > I can see a problem with people like me who do not check the bug tracking > thingy regularly. I certainly would have a look at some src/BUGS or > src/mathed/BUGS file, since this is just six or seven keystrokes away... This won't be a problem, I can easily make sure you/lyx-devel are notified of any bugs ... john -- "They didn't know what the symbols and paradoxes meant. Instead of following the finger that points to the moon, they sat down and worshipped the finger itself. Instead of following the map, they thought it was the territory and tried to live in it. Instead of reading the menu they tried to eat it. Dig ?" - Miss Portinari
Let's try again to change the matrix dialog without being flamed (c:
Dears developpers (c: A few years ago, I send a mail about changing the matrix dialog in a more intuitive way. It was not not a good idea because the dialog size should remain small in order to use lyx on small screens. Anyway I have still the same idea. So I have changed the matrix dialog carefully preserving its size. I think it is more intuitive and as such that it is a good idea(tm)(r)(c). Is it acceptable in this way ? Cordially Emmanuel |\ _,,,---,,_ Emmanuel GUREGHIAN ZZZzz /,`.-'`'-. ;-;;,_ mailto:[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) Magic: 13000 Internal Form Definition File (do not change) Number of forms: 2 Unit of measure: FL_COORD_PIXEL SnapGrid: 2 === FORM === Name: form_maths_matrix Width: 280 Height: 170 Number of Objects: 8 class: FL_BOX type: UP_BOX box: 0 0 280 170 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_DEFAULT_SIZE lcol: FL_BLACK label: shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: callback: argument: class: FL_VALSLIDER type: VERT_NICE_SLIDER box: 10 30 32 88 boxtype: FL_DOWN_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Rows shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: slider_rows callback: C_FormBaseDeprecatedInputCB argument: 0 bounds: 1 20 precision: 0 return: FL_RETURN_END_CHANGED class: FL_VALSLIDER type: HOR_NICE_SLIDER box: 52 30 214 30 boxtype: FL_DOWN_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Columns shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: slider_columns callback: C_FormBaseDeprecatedInputCB argument: 0 bounds: 1 20 precision: 0 return: FL_RETURN_END_CHANGED class: FL_CHOICE type: NORMAL_CHOICE box: 60 90 90 30 boxtype: FL_FRAME_BOX colors: FL_COL1 FL_BLACK alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Vertical align|#V shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: choice_valign callback: C_FormBaseDeprecatedInputCB argument: 0 class: FL_INPUT type: NORMAL_INPUT box: 178 90 90 30 boxtype: FL_DOWN_BOX colors: FL_COL1 FL_MCOL alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Horizontal align|#H shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: input_halign callback: C_FormBaseDeprecatedInputCB argument: 0 class: FL_BUTTON type: RETURN_BUTTON box: 10 130 80 30 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: OK shortcut: ^M resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: button_ok callback: C_FormBaseDeprecatedOKCB argument: 0 class: FL_BUTTON type: NORMAL_BUTTON box: 100 130 80 30 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Apply|#A shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: button_apply callback: C_FormBaseDeprecatedApplyCB argument: 0 class: FL_BUTTON type: NORMAL_BUTTON box: 190 130 80 30 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Cancel|^[ shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: button_cancel callback: C_FormBaseDeprecatedCancelCB argument: 0 === FORM === Name: form_maths_matrix Width: 280 Height: 170 Number of Objects: 8 class: FL_BOX type: UP_BOX box: 0 0 280 170 boxtype: FL_UP_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_CENTER style: FL_NORMAL_STYLE size: FL_DEFAULT_SIZE lcol: FL_BLACK label: shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: callback: argument: class: FL_VALSLIDER type: VERT_NICE_SLIDER box: 12 28 28 132 boxtype: FL_DOWN_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Rows shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: slider_rows callback: C_FormBaseDeprecatedInputCB argument: 0 bounds: 1 20 precision: 0 return: FL_RETURN_END_CHANGED class: FL_VALSLIDER type: HOR_NICE_SLIDER box: 52 26 124 32 boxtype: FL_DOWN_BOX colors: FL_COL1 FL_COL1 alignment: FL_ALIGN_TOP style: FL_NORMAL_STYLE size: FL_NORMAL_SIZE lcol: FL_BLACK label: Columns shortcut: resize: FL_RESIZE_ALL gravity: FL_NoGravity FL_NoGravity name: slid
Re: Management of bug reports
> I also think that before we can release a "pre" we have to fix all open > bugs! See you next year then... ;-} > I'm on the way to fix my share, but that is quite large and I would > be really happy if someone could also have a look at reported bugs. IMO > we are now in some sort of FREEZE where we should try to fix bugs and not > introduce new features which produce new bugs! So let's start stabilizizing > the tree. I am (more or less) doing so already since Bolzano... Andre' -- André Pönitz . [EMAIL PROTECTED]
