Kayvan Who is who in that picture?
Andre, Jose, Konni, Alfredo, Francesca (sp?), Lars, me, Angus, Jean-Marc.
Could you mark banner.ppm as BINARY, please?
CVS, by default, tranfers files in text mode.
Regards,
SMiyata
> Kayvan> Who is who in that picture?
> Andre, Jose, Konni, Alfredo, Francesca (sp?), Lars, me, Angus, Jean-Marc.
Could you mark banner.ppm as BINARY, please?
CVS, by default, tranfers files in text mode.
Regards,
SMiyata
So in summary, 'if(kbuflen 1)' is O.K. with the
(B japanese input, right?
(B
(BYes.
(B
(BRegards,
(BSMiyata
Angus Leeming [EMAIL PROTECTED] wrote:
(B
(B Ok, CG. I tried it. xfs uses all my cpu. This is very wrong :-( Can you try
(B things out with LANG=C or something 'normal'. This thing has to work for
(B the rest of the world too, doesn't it?
(B
(BI guess you are trying to scale a bitmap font.
> So in summary, 'if(kbuflen > 1)' is O.K. with the
(B> japanese input, right?
(B
(BYes.
(B
(BRegards,
(BSMiyata
Angus Leeming <[EMAIL PROTECTED]> wrote:
(B
(B> Ok, CG. I tried it. xfs uses all my cpu. This is very wrong :-( Can you try
(B> things out with LANG=C or something 'normal'. This thing has to work for
(B> the rest of the world too, doesn't it?
(B
(BI guess you are trying to scale a bitmap
e of cursor position to the IM server so that it
(Bcan adjust the input location.
(B
(BI guess it is a little bit more complicated than a typical Korean input.
(B
(BRegards,
(BShigeru Miyata
t
(Bdisplays the received string and move the cursor and notifies
(Bthe change of cursor position to the IM server so that it
(Bcan adjust the input location.
(B
(BI guess it is a little bit more complicated than a typical Korean input.
(B
(BRegards,
(BShigeru Miyata
Sorry, I don't have time to look at the source
(Bright now.
(BSo here are only vague general remarks.
(B
(BXIM is designed to be created only once for an X
(Bconnection. Don't create more than one XIM
(Bnor destroy and recreate again and again.
(BXlib can be quite fragile, (especially you
Sorry, I don't have time to look at the source
(Bright now.
(BSo here are only vague general remarks.
(B
(BXIM is designed to be created only once for an X
(Bconnection. Don't create more than one XIM
(Bnor destroy and recreate again and again.
(BXlib can be quite fragile, (especially you
Angus Leeming [EMAIL PROTECTED] wrote:
(B
(B As an aside, I also believe that this could be made to work with
(Bcghan's
(B stuff because every composed char has a unique keysym. (Am I right
(Bhere?)
(B That means fl_XLookupString could be modified to work with far eastern
(B
(B languages
Angus Leeming <[EMAIL PROTECTED]> wrote:
(B
(B> As an aside, I also believe that this could be made to work with
(Bcghan's
(B> stuff because every composed char has a unique keysym. (Am I right
(Bhere?)
(B> That means fl_XLookupString could be modified to work with far eastern
(B
(B>
Angus Leeming [EMAIL PROTECTED] wrote:
(B
(B Incidentally, why do we pass LYX_DIR on the command line and not put
(Bit in
(B config.h? That would also mean that this could go too:
(B
(B support/os2_defines.h:#undef LYX_DIR
(B support/os2_defines.h:#define LYX_DIR
Angus Leeming <[EMAIL PROTECTED]> wrote:
(B
(B> Incidentally, why do we pass LYX_DIR on the command line and not put
(Bit in
(B> config.h? That would also mean that this could go too:
(B>
(B> support/os2_defines.h:#undef LYX_DIR
(B> support/os2_defines.h:#define LYX_DIR
CID-keyed PostScript fonts do support more than 256 glyphs in an
encoding vector. There are patches for dvips and dvipdfm to support
this type of font.
Oh I didn't know that. Thanks for the information, although I have
no time right now to check and play with it.
However, people are *using*
> CID-keyed PostScript fonts do support more than 256 glyphs in an
> encoding vector. There are patches for dvips and dvipdfm to support
> this type of font.
Oh I didn't know that. Thanks for the information, although I have
no time right now to check and play with it.
> However, people are
Philipp Reichmuth wrote:
Would it seem a good idea to merge the CJK patch for support of
multibyte character sets with the main trunk sometime in the near
future (such as for 1.3)?
No. The CJK patch is not something we want to see merged with its
current status, and xforms-0. is not
Philipp Reichmuth wrote:
> Would it seem a good idea to merge the CJK patch for support of
> multibyte character sets with the main trunk sometime in the near
> future (such as for 1.3)?
No. The CJK patch is not something we want to see merged with its
current status, and xforms-0. is not
In-Reply-To: [EMAIL PROTECTED]
Note that the input method code in xforms is supposed to be derived
from lyxlookup.[Ch] (because I am the one who requested support).
Hence it creates Input Context with the style bits
XIMPreeditNothing|XIMStatusNothing
which is a pain in the neck for
In-Reply-To: <[EMAIL PROTECTED]>
> Note that the input method code in xforms is supposed to be derived
> from lyxlookup.[Ch] (because I am the one who requested support).
Hence it creates Input Context with the style bits
XIMPreeditNothing|XIMStatusNothing
which is a pain in the neck for
Andre Poenitz wrote:
What a mess.
But it is "logical" bold, isn't it? So one could hack it in by providing
another 'char' argument for whichFont()... Not nice, though.
Math versions are supposed be orthogonal.
(fontmath.ltx) | normal bold
Andre Poenitz wrote:
> What a mess.
>
> But it is "logical" bold, isn't it? So one could hack it in by providing
> another 'char' argument for whichFont()... Not nice, though.
Math versions are supposed be orthogonal.
(fontmath.ltx) | normal bold
In-Reply-To: [EMAIL PROTECTED]
Andre Poenitz [EMAIL PROTECTED] wrote:
Does anybody know what exactly is going on and why the scaling does not
work?
1.1.6 assumes that the font of the XLFD name
-*-*-*-*-*-*-*-*-*-*-*-*-adobe-fontspecific
is in the Adobe Symbol encoding. While 1.2 asssumes
In-Reply-To: <[EMAIL PROTECTED]>
Andre Poenitz <[EMAIL PROTECTED]> wrote:
> Does anybody know what exactly is going on and why the scaling does not
> work?
1.1.6 assumes that the font of the XLFD name
-*-*-*-*-*-*-*-*-*-*-*-*-adobe-fontspecific
is in the Adobe Symbol encoding. While 1.2
You cannot create math delimiters '/' and '|' with 1.2.0
If you crete a math delimiter '\', then LaTeX is wrong.
When 1.2.0 reads a lyx file created with 1.1.6, then
math delimiters '/' and '|' are lost, and '\' is not displayed
correctly (LaTeX is OK, though).
Regards,
SMiyata
Index:
You cannot create math delimiters '/' and '|' with 1.2.0
If you crete a math delimiter '\', then LaTeX is wrong.
When 1.2.0 reads a lyx file created with 1.1.6, then
math delimiters '/' and '|' are lost, and '\' is not displayed
correctly (LaTeX is OK, though).
Regards,
SMiyata
Index:
In-Reply-To: [EMAIL PROTECTED]
"R. Lahaye" [EMAIL PROTECTED] wrote:
No, wchar.h is also missing on a FreeBSD system,
all others, such as wctype.h etc., are missing as well.
You are wrong. I've never used FreeBSD myself, but I *know*
how they implement multibyte/wide character supports in
In-Reply-To: <[EMAIL PROTECTED]>
"R. Lahaye" <[EMAIL PROTECTED]> wrote:
> No, wchar.h is also missing on a FreeBSD system,
> all others, such as wctype.h etc., are missing as well.
You are wrong. I've never used FreeBSD myself, but I *know*
how they implement multibyte/wide character supports
In-Reply-To: [EMAIL PROTECTED]
[EMAIL PROTECTED] (Lars Gullik =?iso-8859-1?q?Bj=F8nnes?=) wrote:
are there wide string/char support in FreeBSD at all?
Yes. The rune_t concept is a far much superior implementation
of the 32 bit width character support in libc than the traditional
wchar_t
In-Reply-To: <[EMAIL PROTECTED]>
[EMAIL PROTECTED] (Lars Gullik =?iso-8859-1?q?Bj=F8nnes?=) wrote:
> are there wide string/char support in FreeBSD at all?
Yes. The rune_t concept is a far much superior implementation
of the 32 bit width character support in libc than the traditional
wchar_t
In-Reply-To: [EMAIL PROTECTED]
Andre Poenitz [EMAIL PROTECTED] wrote:
Fallback to X symbols does not really seem to work (i.e. I get \sum in red
if I take away the latex fonts from the fontpath?)
Have you update "~/.lyx/symbols" accordingly?
Anyway I have a question. LyX reads the symbols
In-Reply-To: <[EMAIL PROTECTED]>
Andre Poenitz <[EMAIL PROTECTED]> wrote:
> Fallback to X symbols does not really seem to work (i.e. I get \sum in red
> if I take away the latex fonts from the fontpath?)
Have you update "~/.lyx/symbols" accordingly?
Anyway I have a question. LyX reads the
In-Reply-To: [EMAIL PROTECTED]
Andre Poenitz [EMAIL PROTECTED] wrote:
and the support for \mathscr (\usepackage{eucal}) is problematic since
it changes the meaning of \mathcal as well.
How?
It seems \usepackage{euscript} is preferred over \usepackage{eucal}.
Anyway,
w/o
In-Reply-To: <[EMAIL PROTECTED]>
Andre Poenitz <[EMAIL PROTECTED]> wrote:
> > and the support for \mathscr (\usepackage{eucal}) is problematic since
> > it changes the meaning of \mathcal as well.
>
> How?
It seems \usepackage{euscript} is preferred over \usepackage{eucal}.
Anyway,
w/o
In-Reply-To: [EMAIL PROTECTED]
Andre Poenitz [EMAIL PROTECTED] wrote:
Index: math_charinset.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_charinset.C,v
retrieving revision 1.9
diff -u -p -r1.9
In-Reply-To: <[EMAIL PROTECTED]>
Andre Poenitz <[EMAIL PROTECTED]> wrote:
> Index: math_charinset.C
> ===
> RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_charinset.C,v
> retrieving revision 1.9
> diff -u -p -r1.9
Eran Tromer [EMAIL PROTECTED] wrote:
Perhaps it would be possible to create the file under another name and
rename it when done?
This does not work on OS/2 and probably not on Win32, either.
This is actually an ANSI vs. POSIX issue.
Regards,
SMiyata
Eran Tromer <[EMAIL PROTECTED]> wrote:
> Perhaps it would be possible to create the file under another name and
> rename it when done?
This does not work on OS/2 and probably not on Win32, either.
This is actually an ANSI vs. POSIX issue.
Regards,
SMiyata
[EMAIL PROTECTED] wrote:
But I cannot read the User's Guide (which is pretty
crucial for someone with my background). When I
try to open it, Lyx displays the message "Loading
font into X server" in its gray message window at
the bottom, and it stays like this indefinitely (20 minutes).
<[EMAIL PROTECTED]> wrote:
> > But I cannot read the User's Guide (which is pretty
> > crucial for someone with my background). When I
> > try to open it, Lyx displays the message "Loading
> > font into X server" in its gray message window at
> > the bottom, and it stays like this indefinitely
Dekel Tsur [EMAIL PROTECTED] wrote:
I'm relieved to see you are safe.
Regards,
SMiyata
Dekel Tsur <[EMAIL PROTECTED]> wrote:
I'm relieved to see you are safe.
Regards,
SMiyata
Aditya Gilra [EMAIL PROTECTED] wrote:
I have some experience in C/Java programming,
but I've never contributed to an open-source project
before though I'd certainly like to.
Pl. inform how to proceed and which parts of the code
to look at for Hindi rendering.
Sorry, I actually do not
Aditya Gilra <[EMAIL PROTECTED]> wrote:
> I have some experience in C/Java programming,
> but I've never contributed to an open-source project
> before though I'd certainly like to.
>
> Pl. inform how to proceed and which parts of the code
> to look at for Hindi rendering.
Sorry, I actually do
Aditya Gilra [EMAIL PROTECTED] wrote:
Could you inform how long it is before lyx supports
hindi/devanagari pages in unicode. I learn that
unicode support is present but I couldn't see how
in 1.1.6 . Do I need to get the development version
for it.
It is unlikely to be supported unless
Aditya Gilra <[EMAIL PROTECTED]> wrote:
> Could you inform how long it is before lyx supports
> hindi/devanagari pages in unicode. I learn that
> unicode support is present but I couldn't see how
> in 1.1.6 . Do I need to get the development version
> for it.
It is unlikely to be supported
I wrote:
Since I cannot compile LyX any more here, I would like Windows developers
to submit the final patch.
Thanks to a help from Ilya Zakharevich, I modified syscall() of EMX and
I can compile LyX again on OS/2. Well, almost.
In buffer.C, bitset is included before "LString.h", which
I wrote:
> Since I cannot compile LyX any more here, I would like Windows developers
> to submit the final patch.
Thanks to a help from Ilya Zakharevich, I modified syscall() of EMX and
I can compile LyX again on OS/2. Well, almost.
In buffer.C, is included before "LString.h", which breaks
Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote:
It seems to me that at the time SMiyata submitted it more for comments
than actual inclusion. Anyway, I think we really need something like
that.
Yes, but one of the reason was that I cannot test the code on systems
other than OS/2.
- pay
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> It seems to me that at the time SMiyata submitted it more for comments
> than actual inclusion. Anyway, I think we really need something like
> that.
Yes, but one of the reason was that I cannot test the code on systems
other than OS/2.
> -
Baruch Even [EMAIL PROTECTED] wrote:
It seems like we can start using namespaces freely, at least as far as
the developers go. There was no yelling, and so far it seems that no
mercenary had an attempt on my life.
Had I a time to contribute to the LyX development, I would have yelled.
gcc
Baruch Even <[EMAIL PROTECTED]> wrote:
> It seems like we can start using namespaces freely, at least as far as
> the developers go. There was no yelling, and so far it seems that no
> mercenary had an attempt on my life.
Had I a time to contribute to the LyX development, I would have yelled.
Juergen Vigna [EMAIL PROTECTED] wrote:
And I still don't understand _why_ this is needed.
You will!
Diff attached (I was about to commit you just beat me for about 5 minutes
with your mail ;)
Sorry for a very late reply. But I forgot to tell you one thing.
You have to #include time.h
[EMAIL PROTECTED] (Lars Gullik Bj\o nnes) wrote:
because of?
In the case LFUN_DATE_INSERT in Dispatch() switch, time() and
localtime() are used.
(and I hope ctime will do)
Of course ctime will do. Sorry.
Regards,
SMiyata
Juergen Vigna <[EMAIL PROTECTED]> wrote:
> > And I still don't understand _why_ this is needed.
>
> You will!
>
> Diff attached (I was about to commit you just beat me for about 5 minutes
> with your mail ;)
Sorry for a very late reply. But I forgot to tell you one thing.
You have to
[EMAIL PROTECTED] (Lars Gullik Bj\o nnes) wrote:
> because of?
In the case LFUN_DATE_INSERT in Dispatch() switch, time() and
localtime() are used.
> (and I hope will do)
Of course will do. Sorry.
Regards,
SMiyata
I think I know what's going on.
When you are moving the cursor in a big tabular inset,
InsetTabular::moveRight() etc. calls
InsetTabular::ActivateCellInset() when the cursor moves into a
new cell, which then calls
InsetText::Edit() which then calls
InsetText::SetFont() which then calls
I think I know what's going on.
When you are moving the cursor in a big tabular inset,
InsetTabular::moveRight() etc. calls
InsetTabular::ActivateCellInset() when the cursor moves into a
new cell, which then calls
InsetText::Edit() which then calls
InsetText::SetFont() which then calls
I wrote:
LyXParagraph::GetChar(wchar_t) is necessary.
Sorry, it was a typo.
wchar_t LyXParagraph::GetChar() is necessary.
After all CJK are really easy to typeset languages.
What we consider a single character in everyday life
corresponds to a single wide character in the sense of
encodings.
A further correction:
After all CJK are really easy to typeset languages.
What we consider a single character in everyday life
corresponds to a single wide character in the sense of
encodings.
Jamo might be an exception. But I presume you are predominantly
using Johab.
Regards,
I wrote:
> LyXParagraph::GetChar(wchar_t) is necessary.
Sorry, it was a typo.
wchar_t LyXParagraph::GetChar() is necessary.
After all CJK are really easy to typeset languages.
What we consider a single character in everyday life
corresponds to a single wide character in the sense of
encodings.
A further correction:
> After all CJK are really easy to typeset languages.
> What we consider a single character in everyday life
> corresponds to a single wide character in the sense of
> encodings.
Jamo might be an exception. But I presume you are predominantly
using Johab.
Regards,
[EMAIL PROTECTED] wrote:
Attached is my recent attempt of CJK-LyX patch againt lyx-1.1.6. It is
very incomplete, especially in the "lyxfont::width" part in "font.C". I
hope you have time to examine the codes and give me any resolution, hints,
or comments.
I have migrated my development
Dekel Tsur [EMAIL PROTECTED] wrote:
I agree. The first step for the integration of CJK support is to change the
internal text representation to UCS-4 (namely change LyXParagraph::value_type
to wchar), and change the encoding of LyX files to UTF-8.
sizeof(wchar_t) need not be 4. I've heard
<[EMAIL PROTECTED]> wrote:
> Attached is my recent attempt of CJK-LyX patch againt lyx-1.1.6. It is
> very incomplete, especially in the "lyxfont::width" part in "font.C". I
> hope you have time to examine the codes and give me any resolution, hints,
> or comments.
I have migrated my
Dekel Tsur <[EMAIL PROTECTED]> wrote:
> I agree. The first step for the integration of CJK support is to change the
> internal text representation to UCS-4 (namely change LyXParagraph::value_type
> to wchar), and change the encoding of LyX files to UTF-8.
sizeof(wchar_t) need not be 4. I've
Baruch Even [EMAIL PROTECTED] wrote:
There is also Pango at http://www.pango.org/
Which is supposed to handle various languages including bidirectional
and the various strange languages around.
It's task is ordering and shaping of characters, it is build into GTK 2,
but it is written in a
Dekel Tsur [EMAIL PROTECTED] wrote:
Pango might be useful, but it might be too much work to make LyX use it.
We first need to switch to 16/32-bit internal text representation. Only
after that we should consider whether to use Pango.
LyXParagraph::value_type is used only in the class
Baruch Even <[EMAIL PROTECTED]> wrote:
> There is also Pango at http://www.pango.org/
> Which is supposed to handle various languages including bidirectional
> and the various strange languages around.
>
> It's task is ordering and shaping of characters, it is build into GTK 2,
> but it is
Dekel Tsur <[EMAIL PROTECTED]> wrote:
> Pango might be useful, but it might be too much work to make LyX use it.
> We first need to switch to 16/32-bit internal text representation. Only
> after that we should consider whether to use Pango.
LyXParagraph::value_type is used only in the class
Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote:
Herbert, did you solve this problem?? It could maybe be a wrong
language description somewhere... Do you use greek? Do you have your
own language file?
It is that lyxlex does not respect newlines. In 1.1.6 languages file
looked like
# name
([EMAIL PROTECTED](B (J(Lars(B (JGullik(B (JBj(B\o nnes) wrote:
(JWhy(B (Jdo(B (Jyou(B (Jneed(B (Jthe(B (Jargc(B (Jcheck?(B
(J(and(B (Jisn't(B (Jargc(B (Jalways(B (J!0?)(B
As I say, it is a hack. In order to build some global
instances of classes, e.g. lyxrc,
Amir Karger [EMAIL PROTECTED] wrote:
pardon me for asking, but I can't help noticing that almost every letter is
mapped to "t". That's a pretty strange keymap! How does the thai alphabet
work?
???
Anyway, if you want ot get a headache, try
http://www.unicode.org/unicode/uni2book/ch09.pdf
I
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> Herbert, did you solve this problem?? It could maybe be a wrong
> language description somewhere... Do you use greek? Do you have your
> own language file?
It is that lyxlex does not respect newlines. In 1.1.6 languages file
looked like
# name
([EMAIL PROTECTED](B (J(Lars(B (JGullik(B (JBj(B\o nnes) wrote:
> (JWhy(B (Jdo(B (Jyou(B (Jneed(B (Jthe(B (Jargc(B (Jcheck?(B
> (J(and(B (Jisn't(B (Jargc(B (Jalways(B (J!0?)(B
As I say, it is a hack. In order to build some global
instances of classes, e.g. lyxrc,
Amir Karger <[EMAIL PROTECTED]> wrote:
> pardon me for asking, but I can't help noticing that almost every letter is
> mapped to "t". That's a pretty strange keymap! How does the thai alphabet
> work?
???
Anyway, if you want ot get a headache, try
Appearently, I have to attract more attention.
[EMAIL PROTECTED] (Lars Gullik Bj\onnes) wrote:
+#ifdef __EMX__
+ ::unlink(to.c_str());
+#endif
Why not lyx::unlink(to); ?
Simply, I overlooked it.
To me it look good and certainly a step in the right direction.
I have
Appearently, I have to attract more attention.
[EMAIL PROTECTED] (Lars Gullik Bj\onnes) wrote:
> +#ifdef __EMX__
> + ::unlink(to.c_str());
> +#endif
>
> Why not lyx::unlink(to); ?
Simply, I overlooked it.
> To me it look good and certainly a step in the right direction.
>
>
Herbert Voss [EMAIL PROTECTED] wrote:
exporting to tex gives the following lyx-command:
%% LyX specific LaTeX commands.
\providecommand{\LyX}{L\kern-.1667em\lower.25em\hbox{Y}\kern-.125emX\@}
greek
%% User specified LaTeX commands.
Herbert Voss <[EMAIL PROTECTED]> wrote:
> exporting to tex gives the following lyx-command:
>
> %% LyX specific LaTeX commands.
> \providecommand{\LyX}{L\kern-.1667em\lower.25em\hbox{Y}\kern-.125emX\@}
> greek
>
> %% User specified LaTeX
I haven't modified my code to use traits as suggested by
Lars. However it seems to work all right.
Please take a look, comment, critisize, and help me write
a clean code. Please do not apply every thing blindly.
BTW I had to modify the type of BufferView::Pimpl::Position::par_pos
from int to
I haven't modified my code to use traits as suggested by
Lars. However it seems to work all right.
Please take a look, comment, critisize, and help me write
a clean code. Please do not apply every thing blindly.
BTW I had to modify the type of BufferView::Pimpl::Position::par_pos
from int to
[EMAIL PROTECTED] (Lars Gullik Bj$Bøn(Jnes) wrote:
What class os? where can I find it?
I've wrote something like this.
The idea comes from a post on this group by "Ruurd A Reitsma"
[EMAIL PROTECTED].
Do you think this a bad idea?
Regards,
SMiyata
os_specific.tar.gz
I apologize if my wording did sound (quite intentionary) harsh.
Dekel Tsur [EMAIL PROTECTED] wrote:
- if a user doesn't read the documentation of TeX/LyX,
then s/he won't get a optimal outputs;
This is an important issue. Even though I wrote a comprehensive explanation
of
Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote:
There is no real differenciation between PS and compouter modern
fonts. Where would you put malvern, concrete or cmbright fonts in your
dichotomy? All the fonts should be mixed, ps or not ps.
Sorry for nitpicking, but Adobe standarized the names
Sorry it had nothing to do with static member initialization.
I removed an infinite loop in my code and LyX starts without
crash.
[EMAIL PROTECTED] (Lars Gullik Bj~nnes) wrote:
No. But we should perhaps do it with traits instead?
struct unix_traits {
static)
void
[EMAIL PROTECTED] (Lars Gullik Bj$Bøn(Jnes) wrote:
> What class os? where can I find it?
I've wrote something like this.
The idea comes from a post on this group by "Ruurd A Reitsma"
<[EMAIL PROTECTED]>.
Do you think this a bad idea?
Regards,
SMiyata
os_specific.tar.gz
I apologize if my wording did sound (quite intentionary) harsh.
Dekel Tsur <[EMAIL PROTECTED]> wrote:
> >- if a user doesn't read the documentation of TeX/LyX,
> > then s/he won't get a optimal outputs;
>
> This is an important issue. Even though I wrote a comprehensive explanation
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> There is no real differenciation between PS and compouter modern
> fonts. Where would you put malvern, concrete or cmbright fonts in your
> dichotomy? All the fonts should be mixed, ps or not ps.
Sorry for nitpicking, but Adobe standarized the
Sorry it had nothing to do with static member initialization.
I removed an infinite loop in my code and LyX starts without
crash.
[EMAIL PROTECTED] (Lars Gullik Bj~nnes) wrote:
> No. But we should perhaps do it with traits instead?
>
> struct unix_traits {
> static)
>
In John Levon [EMAIL PROTECTED]'s SIG, I found:
"Voodoo Programming: Things programmers do that they know shouldn't work but
they try anyway, and which sometimes actually work, such as recompiling
everything."
- Karl Lehenbauer
That's exactly what I am doing! Seriously, I slowly
Dekel Tsur [EMAIL PROTECTED] wrote:
On Thu, Jan 25, 2001 at 05:26:56PM +0100, Marcus Beyer wrote:
AFAIK the support of bitmap fonts has only two important effects:
1. Many new LyX users have do make the "ugly-fonts-experience",
at least when they publish their documents to the web,
In John Levon <[EMAIL PROTECTED]>'s SIG, I found:
> "Voodoo Programming: Things programmers do that they know shouldn't work but
> they try anyway, and which sometimes actually work, such as recompiling
> everything."
> - Karl Lehenbauer
That's exactly what I am doing! Seriously, I
Dekel Tsur <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 25, 2001 at 05:26:56PM +0100, Marcus Beyer wrote:
> > AFAIK the support of bitmap fonts has only two important effects:
> > 1. Many new LyX users have do make the "ugly-fonts-experience",
> >at least when they publish their documents to the
Here is an update of two OS/2 related files. Please
replace the old ones in CVS with them.
And PLEASE PLEASE PLEASE include autogen.sh in the distribution.
Regards,
SMiyata
1.1.6-os2-support.tar.gz
Here is an update of two OS/2 related files. Please
replace the old ones in CVS with them.
And PLEASE PLEASE PLEASE include autogen.sh in the distribution.
Regards,
SMiyata
1.1.6-os2-support.tar.gz
Amir Karger [EMAIL PROTECTED] wrote:
Otherwise, you'd have to write it so that it automatically displayed what
the person's personal bindings were at that time, or something.
Why don't you write a perl script to parse users' lyxrc, preference, ui and
bind files, and to update UserGuide.lyx?
Amir Karger <[EMAIL PROTECTED]> wrote:
> Otherwise, you'd have to write it so that it automatically displayed what
> the person's personal bindings were at that time, or something.
Why don't you write a perl script to parse users' lyxrc, preference, ui and
bind files, and to update
Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote:
Bunzip2 tells me that the file is corrupted. Could you resend it,
please?
Sorry. I hope it's OK this time.
Regards,
SMiyata
os2-stuff.tar.gz
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> Bunzip2 tells me that the file is corrupted. Could you resend it,
> please?
Sorry. I hope it's OK this time.
Regards,
SMiyata
os2-stuff.tar.gz
1 - 100 of 335 matches
Mail list logo
