"# Support for right-to-left languages: If you wish to write in Hebrew
under Mac OS X, there's only one word processing option: Mellel. Support
is not limited to BiDi (bidirectional) algorithm support, but also
extends to many improvements to this algorithm, including handling of
dashes, main and
On Sat, Apr 05, 2003 at 07:34:13PM -0600, [EMAIL PROTECTED] wrote:
> I'm imagining inline notes, with greyed text
Try using the Comment environment.
> But it get's better. I use the sections to outline with, so the TOC viewer,
> could easily become a outline editor, which allowed drag and drop
Hi. I'd like to share with everyone a what WYSIWYM means to me.
When I add yellow "notes" to my document, That's WYSIWYM to me. But I don't
use yellow notes, because they are yellow, and stand out, becoming
distracting as i try to type. my notes are usually what to add at the end
of the secti
On Sun, Apr 06, 2003 at 12:22:46AM +0200, Lars Gullik Bj?nnes wrote:
> | We so do not need threads.
>
> Would simplify things...
No it wouldn't, it would significantly complicate things. As Angus has
already pointed out, we already have asynchronous notification
architecture, and all that is rea
John Levon <[EMAIL PROTECTED]> writes:
| On Sat, Apr 05, 2003 at 11:22:15AM +0200, Lars Gullik Bj?nnes wrote:
|
| > I'd rather introduce some threads to lyx, and just say that all
| > platforms that does not have treading just gets the sync behaviour
| > instead.
|
| We so do not need threads.
Angus Leeming <[EMAIL PROTECTED]> writes:
| Maybe. But we already have a mechanism for non-blocking forking of processes
| which will tell us when the process has finished. So we could
| for (;;) {
| fork latex run and subsequently
| receive notification of its finish
| p
On Sat, Apr 05, 2003 at 10:11:01PM +0100, John Levon wrote:
> OK Angus, I experimented some more and succeeded in getting it working.
> Please test current CVS.
The patch is a little broken ...
john
OK Angus, I experimented some more and succeeded in getting it working.
Please test current CVS.
JMarc, not sure if you want this for 1.3 or not. Right-arrow is quite
annoying ...
regards
john
? a.diff
? qfont_metrics.map.C
Index: ChangeLog
=
On Fri, Apr 04, 2003 at 02:35:22PM +0200, Christian Ridderstr?m wrote:
> advanced_mode.png - An "Simple mode" button is added
> simple_mode.png- Reduced version + "Advanced mode" button
I've resisted the temptation to add "Advanced" rockers for some time,
as it just makes it too
On Fri, Apr 04, 2003 at 10:19:20AM +0100, Bal? wrote:
> I have some time today I will try to take a look into it.
Thanks.
> So the test I expect to apply is something like this
>
> if first_line != \layout
> add \layout Standard
Sounds about right, just not sure how that looks in p
On Sat, Apr 05, 2003 at 04:36:20PM +, Angus Leeming wrote:
> What is the rationale behind the use of different keys to trigger this for
> the two frontends? xforms uses TAB whereas Qt uses the right arrow key;
> something I found out only by looking at the source!
'Tab' is the key used for
On Sat, Apr 05, 2003 at 11:24:26AM +0200, Lars Gullik Bj?nnes wrote:
> and you have proposal comming for that, right?
I guess so !
john
On Sat, Apr 05, 2003 at 11:22:15AM +0200, Lars Gullik Bj?nnes wrote:
> I'd rather introduce some threads to lyx, and just say that all
> platforms that does not have treading just gets the sync behaviour
> instead.
We so do not need threads.
regards
john
On Sat, Apr 05, 2003 at 11:19:49AM +0200, Lars Gullik Bj?nnes wrote:
> | > And talking about error boxes, what about nuking them and implementing
> | > instead an error log window doubly linked with the document (i.e. cliking
> | > on a log line puts the cursor within problem in the document, nav
What is the rationale behind the use of different keys to trigger this for
the two frontends? xforms uses TAB whereas Qt uses the right arrow key;
something I found out only by looking at the source!
--
Angus
Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | I suspect that you'll be able to use it as-is meaning that all you
> | really have to do is:
> | 1. Rename it to something sensible ;-)
> | 2. Move the latex parsing stuff in Dekel's Converter into a separate
> | functio
John Levon <[EMAIL PROTECTED]> writes:
| On Fri, Apr 04, 2003 at 10:20:35PM +0200, Michael Schmitt wrote:
|
| > suitable for manual editing. Being able to search for emphasized text
| > etc. would be a BIG step towards a comfortable text processor. If this
|
| This will definitely not happen u
Angus Leeming <[EMAIL PROTECTED]> writes:
| I suspect that you'll be able to use it as-is meaning that all you really
| have to do is:
| 1. Rename it to something sensible ;-)
| 2. Move the latex parsing stuff in Dekel's Converter into a separate
| function.
I do not think that latex running sh
John Levon <[EMAIL PROTECTED]> writes:
| On Fri, Apr 04, 2003 at 08:21:37PM +0200, Alfredo Braunstein wrote:
|
| > And talking about error boxes, what about nuking them and implementing
| > instead an error log window doubly linked with the document (i.e. cliking
| > on a log line puts the curso
Garst R. Reese wrote:
> Curious, I tried it again and indeed it did not work. Either your kharma
> or my stupidity is mind boggling :) Works after your patch tho.
I think that the bug only appears if you have increment/decrement on the
toolbar or something. Have you changed the toolbar lately may
20 matches
Mail list logo
