When I copy some text from word to lyx, a few symbols can not be
handled. It took me quite a while to find them all, and here is what I
add to the unicodesymbols file.
χσΣβμ
0x03c7 "$\\chi$" "" ""
0x03b2 "$\\beta$" "" ""
0x03bc "$\\mu$" "" ""
0x03c0 "$\\pi$" "" ""
0x03b8 "$\\theta$" "" ""
0
Bo Peng wrote:
When I copy some text from word to lyx, a few symbols can not be
handled. It took me quite a while to find them all, and here is what I
add to the unicodesymbols file.
χσΣβμ
0x03c7 "$\\chi$" "" ""
0x03b2 "$\\beta$" "" ""
0x03bc "$\\mu$" "" ""
0x03c0 "$\\pi$" "" ""
0x03b8 "$
Bo Peng wrote:
> I guess there are many more Greek letters. My question is: why are
> they not added before? Is it because of the insertion of $$?
This is wrong.
These are Greek characters, not mathematical symbols. Mathematical symbols
have their own code points in unicode. So you use the wrong
> These are Greek characters, not mathematical symbols. Mathematical symbols
> have their own code points in unicode. So you use the wrong symbols in word.
I did not use these characters, someone else did. It may be a bad
practice to use these symbols instead of math symbols, but if lyx can
handle
On Oct 7, 2007, at 4:40 AM, Jürgen Spitzmüller wrote:
Bo Peng wrote:
I guess there are many more Greek letters. My question is: why are
they not added before? Is it because of the insertion of $$?
This is wrong.
These are Greek characters, not mathematical symbols. Mathematical
symbols
have
> But philosophers like myself occasionally use Greek letters (because we quote
ancient Greek) in
> otherwise English texts, and it would be nice to be able to cut-and-paste
these into LyX. So don't
> use this as a reason not to include Greek characters!
You misunderstood Jürgen. The problem is
> 0x03a3 "$\\sum$" "" ""
See my and Jürgen's reply.
> 0xf0c4 "$\\otimes$" "" ""
The unicode range of this character is not defined:
Range: E000–F8FF
The Private Use Area does not contain any character assignments, consequently no character code
charts or namelists are provided for this area
> You misunderstood Jürgen. The problem is that the 0x03xx characters are no
> math characters but real
> Greek ones. That mean they must be takes as they are. You can already copy
> them directly into your
> LyX file. Mark the characters as Greek via the text style dialog as you
> normally do a
Bo Peng schrieb:
Then why do not we use this unicodesymbol file to do this? Something like
0x "" (do not convert) "use package" ""
This is not possible. The unicodesymbols file is made to translate single characters to a command.
As I said, the characters must be taken as they are and no
On Oct 7, 2007, at 1:43 PM, Uwe Stöhr wrote:
Bo Peng schrieb:
Then why do not we use this unicodesymbol file to do this?
Something like
0x "" (do not convert) "use package" ""
This is not possible. The unicodesymbols file is made to translate
single characters to a command. As I said
Bennett Helm wrote:
> But philosophers like myself occasionally use Greek letters (because
> we quote ancient Greek) in otherwise English texts, and it would be
> nice to be able to cut-and-paste these into LyX. So don't use this as
> a reason not to include Greek characters!
But you don't e
Bennett Helm wrote:
> But take your document and change the language encoding to utf8
> (which might be desirable for other reasons). Then typesetting (with
> pdflatex) gives you many "Package inputenc Error: Unicode char \u8:
> not set up for use with LaTeX" errors.
The problem is that LaTe
Jürgen Spitzmüller wrote:
> > But philosophers like myself occasionally use Greek letters (because
> > we quote ancient Greek) in otherwise English texts, and it would be
> > nice to be able to cut-and-paste these into LyX. So don't use this as
> > a reason not to include Greek characters!
>
Bo Peng wrote:
> I did not use these characters, someone else did. It may be a bad
> practice to use these symbols instead of math symbols, but if lyx can
> handle them, why not?
Because the unicodesymbols list cannot deal with what we would need (yet). We
would need to use \textgreek and load ba
> I agree
> that we should support this (as well as cyrillic), but it's not really easy.
> We need to load babel and use the \textgreek macro (which switches the
> encoding, but not the language).
Can we at least make "Some characters of your document... " more
meaningful? Say, "xx characters can
Bo Peng wrote:
> Can we at least make "Some characters of your document... " more
> meaningful?
Yes, would be good.
Jürgen
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
> Bo Peng wrote:
>> I did not use these characters, someone else did. It may be a bad
>> practice to use these symbols instead of math symbols, but if lyx can
>> handle them, why not?
>
> Because the unicodesymbols list cannot deal with what we would
Jean-Marc Lasgouttes wrote:
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
Bo Peng wrote:
I did not use these characters, someone else did. It may be a bad
practice to use these symbols instead of math symbols, but if lyx can
handle them, why not?
Because the unicodesymbols list cannot deal wi
Jean-Marc Lasgouttes wrote:
> Should greek characters be automatically in greek language? I thought
> the two were separated.
No, they shouldn't. The babel docs states that:
"The commands \greektext and \latintext can be used to switch to greek or
latin fonts. These are declarations.
The command
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
> My understanding is that these switches do not change the language (contrary
> to \selectlanguage and similar switches).
>
> However, the \greektext and \textgreek commands are only available
> if babel is loaded with the "greek" option (probably t
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> For proper latex compilation yes. This is the same issue as with CJK,
> hebrew or Arabic. The language _has_ to be set. I was a proponent of
> automatically switching the language at latex export when a given
> unicode range is detected; but Georg (a
Jean-Marc Lasgouttes wrote:
> Looks like bad design, then.
Yes. The problem is that LaTeX was simply not designed for languages that do
not use non-latin alphabets or non-alphabetic scripts. Omega, Aleph and how
all the attempts were called, were never really finished, so the users of
diverse l
On Mon, Oct 08, 2007 at 12:47:28PM +0200, Jürgen Spitzmüller wrote:
> Jean-Marc Lasgouttes wrote:
> > Looks like bad design, then.
>
> Yes. The problem is that LaTeX was simply not designed for languages that do
> not use non-latin alphabets or non-alphabetic scripts. Omega, Aleph and how
> all
Enrico Forestieri wrote:
> \newcommand{\Ebold}{\mbox{\usefont{U}{cmsy}{b}{n}\char69}}
>
> defines the macro \Ebold which prints a calligraphic bold E in whatever
> context (math or text). So, it is quite simple to devise a \lyxgreek
> macro to typeset a series of greek letters.
But this is bound t
On Mon, Oct 08, 2007 at 01:52:25PM +0200, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > \newcommand{\Ebold}{\mbox{\usefont{U}{cmsy}{b}{n}\char69}}
> >
> > defines the macro \Ebold which prints a calligraphic bold E in whatever
> > context (math or text). So, it is quite simple to devise
Enrico Forestieri wrote:
> > But this is bound to a specific font, isn't it?
>
> But you have to choose a font, as not all (if any) of them (LaTeX fonts)
> have all possible glyphs.
But I do not want a times-like greek font (not to mention cm) if I'm using
Palatino for the latin characters. I thi
On Mon, Oct 08, 2007 at 03:02:32PM +0200, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > > But this is bound to a specific font, isn't it?
> >
> > But you have to choose a font, as not all (if any) of them (LaTeX fonts)
> > have all possible glyphs.
>
> But I do not want a times-like gr
Enrico Forestieri wrote:
> So, in the end you always get the same font with babel, too.
> I think that it is easy to mimic what babel does without requiring
> to mark as greek the text in LyX.
I'm not sure. There are the new TeXGyre fonts that come with Greek characters.
I think the babel definit
On Mon, Oct 08, 2007 at 04:39:43PM +0200, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > So, in the end you always get the same font with babel, too.
> > I think that it is easy to mimic what babel does without requiring
> > to mark as greek the text in LyX.
>
> I'm not sure. There are
Enrico Forestieri wrote:
> Have a look at the attached .lyx files.
I can't see it.
Jürgen
> Should greek characters be automatically in greek language? I thought
> the two were separated.
I don't think we could do this. Take for example Cyrillic: Russian users might find it useful to
convert Cyrillic characters to Russian, but what about the Ukrainian, Bulgarian, ..., users? They
wi
OK. In the end, I need lyx to
1. tell me what character is causing the problem
2. tell me why this happens, and suggest a solution
3. be able to replace all beta with math beta, greek beta etc.
(Advanced find/replace).
I guess 1 and 2 should not be too difficult.
Cheers,
Bo
Bo Peng schrieb:
OK. In the end, I need lyx to
1. tell me what character is causing the problem
Yes, definetively.
2. tell me why this happens, and suggest a solution
Not easy to do. Take the case that the user has inserted a Korean character. I think highlighting
the problematic charact
On Mon, Oct 08, 2007 at 05:46:58PM +0200, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > Have a look at the attached .lyx files.
>
> I can't see it.
Hrmpf. Too many things to do at the same time...
--
Enrico
#LyX 1.5.2 created this file. For more info see http://www.lyx.org/
\lyxform
Enrico Forestieri wrote:
> > Enrico Forestieri wrote:
> > > Have a look at the attached .lyx files.
> >
> > I can't see it.
>
> Hrmpf. Too many things to do at the same time...
OK. This looks like what I expected. What am I supposed to see?
Jürgen
On Mon, Oct 08, 2007 at 07:14:46PM +0200, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > > Enrico Forestieri wrote:
> > > > Have a look at the attached .lyx files.
> > >
> > > I can't see it.
> >
> > Hrmpf. Too many things to do at the same time...
>
> OK. This looks like what I expecte
Enrico Forestieri wrote:
> When you view the dvi, the argument of \textgreek is shown as greek
> letters. So, the unicode character in LyX whose codepoint represents
> the greek alpha can be translated to LaTeX as \textgreek{a}, without
> the need to mark it as greek, provided the preamble contains
Uwe Stöhr wrote:
Bo Peng schrieb:
Then why do not we use this unicodesymbol file to do this? Something
like
0x "" (do not convert) "use package" ""
This is not possible. The unicodesymbols file is made to translate
single characters to a command. As I said, the characters must be
take
A user might paste his favourite greek quote from a webpage. That
works in the GUI, too bad if they then get a latex compile error.
As I said, then he mark it as Greek in the GUI and get a perfect output.
Uwe
Uwe Stöhr wrote:
A user might paste his favourite greek quote from a webpage. That
works in the GUI, too bad if they then get a latex compile error.
As I said, then he mark it as Greek in the GUI and get a perfect output.
That is a nice workaround - but a workaround is what it is.
LyX should
On Tue, Oct 09, 2007 at 07:38:57AM +0200, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > When you view the dvi, the argument of \textgreek is shown as greek
> > letters. So, the unicode character in LyX whose codepoint represents
> > the greek alpha can be translated to LaTeX as \textgre
Enrico Forestieri wrote:
> But \textgreek is defined in greek.ldf which is only loaded when
> specifying the greek option to babel. However, when doing so everything
> is typeset as greek and not only the argument of \textgreek...
I didn't know this. Is is of course bad.
Jürgen
On Tue, Oct 09, 2007 at 04:06:02PM +0200, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > But \textgreek is defined in greek.ldf which is only loaded when
> > specifying the greek option to babel. However, when doing so everything
> > is typeset as greek and not only the argument of \text
Enrico Forestieri wrote:
> Consider also that babel could be switched off by preference, so this
> would leave us in the cold. So, I propose that when any greek unicode
> character is detected the following lines are added to the preamble:
>
> \DeclareRobustCommand{\greektext}{%
> \fontencoding{L
Helge Hafting schrieb:
As I said, then he mark it as Greek in the GUI and get a perfect output.
>
That is a nice workaround - but a workaround is what it is.
That is no workaround, that's how it should work, this is intended. When you insert words from other
language, mark them as such. Whe
On Tue, Oct 09, 2007 at 05:03:54PM +0200, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > Consider also that babel could be switched off by preference, so this
> > would leave us in the cold. So, I propose that when any greek unicode
> > character is detected the following lines are added
> The first patch implements the ideas above (without ranges) and
> works perfectly. You can even mark as greek the chars and get the
> same behaviour as before.
I just tested this patch and it works as expected.
Bo
Uwe Stöhr wrote:
Helge Hafting schrieb:
As I said, then he mark it as Greek in the GUI and get a perfect
output.
>
That is a nice workaround - but a workaround is what it is.
That is no workaround, that's how it should work, this is intended.
When you insert words from other language, mark
On Wed, Oct 10, 2007 at 12:07:51AM -0500, Bo Peng wrote:
> > The first patch implements the ideas above (without ranges) and
> > works perfectly. You can even mark as greek the chars and get the
> > same behaviour as before.
>
> I just tested this patch and it works as expected.
Please, try the a
Enrico Forestieri wrote:
On Wed, Oct 10, 2007 at 12:07:51AM -0500, Bo Peng wrote:
The first patch implements the ideas above (without ranges) and
works perfectly. You can even mark as greek the chars and get the
same behaviour as before.
I just tested this patch and it works as expected.
Plea
On Thu, Oct 11, 2007 at 08:12:18AM +0200, Abdelrazak Younes wrote:
> Enrico Forestieri wrote:
> > On Wed, Oct 10, 2007 at 12:07:51AM -0500, Bo Peng wrote:
> >>> The first patch implements the ideas above (without ranges) and
> >>> works perfectly. You can even mark as greek the chars and get the
>
Enrico Forestieri wrote:
On Thu, Oct 11, 2007 at 08:12:18AM +0200, Abdelrazak Younes wrote:
Enrico Forestieri wrote:
On Wed, Oct 10, 2007 at 12:07:51AM -0500, Bo Peng wrote:
The first patch implements the ideas above (without ranges) and
works perfectly. You can even mark as greek the chars an
On Thu, Oct 11, 2007 at 09:55:01AM +0200, Abdelrazak Younes wrote:
> >> I'd prefer:
> >>if (Encodings::isGreekChar(next))
> >> + break;
Thanks for the suggestion. I also updated the patch in order to have
a sane behaviour with change tracking.
If there are no objecti
On Thu, Oct 11, 2007 at 11:31:30PM +0200, Enrico Forestieri wrote:
> On Thu, Oct 11, 2007 at 09:55:01AM +0200, Abdelrazak Younes wrote:
>
> > >> I'd prefer:
> > >> if (Encodings::isGreekChar(next))
> > >> +break;
>
> Thanks for the suggestion. I also updated the p
> If there are no objections I will commit it.
Before you do, what is the current status?
I currently can't test your patch but it seems that we now convert pasted Greek characters to
\textgreek. Is this done in every case?
We agreed not to convert Greek characters I think. Converting to \text
On Fri, Oct 12, 2007 at 07:54:02PM +0200, Uwe Stöhr wrote:
> > If there are no objections I will commit it.
>
> Before you do, what is the current status?
> I currently can't test your patch but it seems that we now convert pasted
> Greek characters to
> \textgreek. Is this done in every case?
> Without this patch, if you have greek chars in the document and don't
> mark them as Greek, you get latex errors. With this patch, you get the
> greek chars nicely typesetted.
I tried this, but still get a LyX encoding error, see the attached LyX-file. There are some missing
characters in te u
On Sat, Oct 13, 2007 at 02:16:11AM +0200, Uwe Stöhr wrote:
> > Without this patch, if you have greek chars in the document and don't
> > mark them as Greek, you get latex errors. With this patch, you get the
> > greek chars nicely typesetted.
>
> I tried this, but still get a LyX encoding erro
>> Do you have btw. an idea how to highlight the characters LyX stubles over?
>> It would be helpful when LyX tells the user that a character is not in the
>> used encoding, that the problematic character is highlighted.
> I hate any highlighting, flashing, and so on...
Why? When you e.g. search
On Sat, Oct 13, 2007 at 04:51:23PM +0200, Uwe Stöhr wrote:
> >> Do you have btw. an idea how to highlight the characters LyX stubles over?
> >> It would be helpful when LyX tells the user that a character is not in the
> >> used encoding, that the problematic character is highlighted.
>
> > I
> That's in response to a precise request from me and not done without
> my consent. For example, the first thing I do when forced to use Word,
> is deactivating that stupid "feature" about underlining in red unknown
> words.
You shouldn't conclude from you to others. My experience is that 90% of
Uwe Stöhr wrote:
> > That's in response to a precise request from me and not done without
> > my consent. For example, the first thing I do when forced to use Word,
> > is deactivating that stupid "feature" about underlining in red unknown
> > words.
>
> You shouldn't conclude from you to oth
On Sunday 14 October 2007 09:00:13 Georg Baum wrote:
> The View->Source dialog should never be needed for using LyX. It is a nice
> gimmick for people who know LaTeX, but users who don't should never be
> forced to use it.
+1
> Georg
--
José Abílio
Uwe Stöhr wrote:
> I still don't understand what is the problem of highlighting the
> problematic characters when LyX tells you that "a caracter" can't be
> encoded. We do already the same, when LyX shows LaTeX-errors.
We already have the code for throwing the error list on buffer loading if
ther
On Sun, Oct 14, 2007 at 01:20:44PM +0200, Alfredo Braunstein wrote:
> Uwe Stöhr wrote:
[...]
> > > No pasaran!
>
> > What's this?
>
> May I? This means literally "they will not pass" in spanish and was an
> anti-fascist slogan used in the spanish civil war. I am very sad to inform
> Enrico it d
On Sun, Oct 14, 2007 at 10:00:13AM +0200, Georg Baum wrote:
> I agree with Enrico that some automatic as-you-type-stuff should not be
> done, but using the same mechanism that it used for LaTeX errors (an error
> list where you can select an error and the problematic part of the text
> gets highli
Enrico Forestieri wrote:
But in practice it is invaluable for identifying problematic
constructs that otherwise would require exporting as latex for
examination.
maybe it is a good idea to document these somewhere ?
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> That's in response to a precise request from me and not done without
> my consent. For example, the first thing I do when forced to use Word,
> is deactivating that stupid "feature" about underlining in red unknown
> words.
If the error happens at l
Jean-Marc Lasgouttes wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
>> That's in response to a precise request from me and not done without
>> my consent. For example, the first thing I do when forced to use Word,
>> is deactivating that stupid "feature" about underlining in red unknown
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes wrote:
>
>> Enrico Forestieri <[EMAIL PROTECTED]> writes:
>>
>>> That's in response to a precise request from me and not done without
>>> my consent. For example, the first thing I do when forced to use Word,
>>> is deactivatin
On Mon, Oct 15, 2007 at 02:49:27PM +0200, Jean-Marc Lasgouttes wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> > That's in response to a precise request from me and not done without
> > my consent. For example, the first thing I do when forced to use Word,
> > is deactivating that stup
71 matches
Mail list logo
