On Wed, Feb 08, 2023 at 07:23:43PM +0100, Jürgen Spitzmüller wrote:
> Am Mittwoch, dem 08.02.2023 um 13:22 -0500 schrieb Scott Kostyshak:
> > Would it be helpful to see the ctest results for XeTeX and LuaTeX
> > (with system fonts) when "Always Babel" is checked? i.e., I would
> > essentially sed i
Am Mittwoch, dem 08.02.2023 um 13:22 -0500 schrieb Scott Kostyshak:
> Would it be helpful to see the ctest results for XeTeX and LuaTeX
> (with system fonts) when "Always Babel" is checked? i.e., I would
> essentially sed in the '\language_package babel' to the .lyx files
> and then run the ctests
On Wed, Feb 08, 2023 at 07:14:20PM +0100, Jürgen Spitzmüller wrote:
> Am Mittwoch, dem 08.02.2023 um 13:10 -0500 schrieb Scott Kostyshak:
> > But aren't there cases where both Babel and Polyglossia are
> > reasonable choices?
>
> Yes, with XeTeX and LuaTeX.
>
> > Let me try to answer the above qu
Am Mittwoch, dem 08.02.2023 um 13:10 -0500 schrieb Scott Kostyshak:
> But aren't there cases where both Babel and Polyglossia are
> reasonable choices?
Yes, with XeTeX and LuaTeX.
> Let me try to answer the above question:
>
> When both Babel and Polyglossia are both appropriate, if the user
> w
On Wed, Feb 08, 2023 at 07:05:22PM +0100, Jürgen Spitzmüller wrote:
> Am Mittwoch, dem 08.02.2023 um 12:57 -0500 schrieb Scott Kostyshak:
> > There is an option "Always Babel". Would it make sense to also have
> > "Always Polyglossia"?
>
> No.
>
> Babel works with classic and new engines, polyglo
Am Mittwoch, dem 08.02.2023 um 12:57 -0500 schrieb Scott Kostyshak:
> There is an option "Always Babel". Would it make sense to also have
> "Always Polyglossia"?
No.
Babel works with classic and new engines, polyglossia only with new
ones. Thus always would fail where polyglossia is not preferred
On Mon, Sep 02, 2019 at 04:14:04PM +0200, Günter Milde wrote:
> On 31.08.19, Scott Kostyshak wrote:
> > On Sat, Aug 31, 2019 at 11:41:17AM +0200, Jürgen Spitzmüller wrote:
> > > Am Freitag, den 30.08.2019, 21:29 -0400 schrieb Scott Kostyshak:
> > > > I don't remember if this is being discussed else
On Sat, Aug 31, 2019 at 04:11:08PM +0200, Jürgen Spitzmüller wrote:
> Am Samstag, den 31.08.2019, 08:46 -0400 schrieb Scott Kostyshak:
> > Sounds good. Günter, can I do that and then invert this test and mark
> > it
> > as a "tex issue" ?
>
> I had a very quick check (no time for more ATM) and not
Am Samstag, den 31.08.2019, 08:46 -0400 schrieb Scott Kostyshak:
> Sounds good. Günter, can I do that and then invert this test and mark
> it
> as a "tex issue" ?
I had a very quick check (no time for more ATM) and noted that it is
not dependent on a particular language, but apparently on the shee
On Sat, Aug 31, 2019 at 11:41:17AM +0200, Jürgen Spitzmüller wrote:
> Am Freitag, den 30.08.2019, 21:29 -0400 schrieb Scott Kostyshak:
> > I don't remember if this is being discussed elsewhere. If I compile
> > the
> > following file with XeTeX I get an error:
> >
> > autotests/export/latex/lang
Am Freitag, den 30.08.2019, 21:29 -0400 schrieb Scott Kostyshak:
> I don't remember if this is being discussed elsewhere. If I compile
> the
> following file with XeTeX I get an error:
>
> autotests/export/latex/languages/supported-languages_babel_non-
> tex.lyx
>
> The first error is:
>
> !
Am Mittwoch, 25. April 2018 19:13:13 CEST schrieb Jürgen Spitzmüller
:
> Am Dienstag, den 24.04.2018, 20:55 +0200 schrieb Kornel Benko:
> > For our language specialists...
> > This MWE is not compilable.
>
> Can you file a bug report, please?
#11128
Kornel
signature.asc
Description
Am Dienstag, den 24.04.2018, 20:55 +0200 schrieb Kornel Benko:
> For our language specialists...
> This MWE is not compilable.
Can you file a bug report, please?
Jürgen
>
> Kornel
signature.asc
Description: This is a digitally signed message part
Am Dienstag, 24. April 2018 20:55:28 CEST schrieb Kornel Benko :
> For our language specialists...
> This MWE is not compilable.
>
> Kornel
>
Added new testcase 'languagenesting_tablecell.*' at 0add712.
Kornel
signature.asc
Description: This is a digitally signed message part.
On Sun, Dec 17, 2017 at 12:45:30AM +, Uwe Stöhr wrote:
> El 16.12.2017 a las 22:33, Scott Kostyshak escribió:
>
> > Uwe, should I make the Changelog file? What do you prefer?
>
> Better mail him directly. He usually responds quickly.
OK sent.
Thanks,
Scott
signature.asc
Description: PGP
El 16.12.2017 a las 22:33, Scott Kostyshak escribió:
Uwe, should I make the Changelog file? What do you prefer?
Better mail him directly. He usually responds quickly.
thanks and regards
Uwe
On Wed, Dec 13, 2017 at 06:46:01AM +, Jürgen Spitzmüller wrote:
> Am Montag, den 11.12.2017, 21:07 -0500 schrieb Scott Kostyshak:
> > Will Koji know that the string should be translated? I assumed that
> > he
> > just searches for text that is marked as English. Should we just
> > notify
> > hi
Am Montag, den 11.12.2017, 21:07 -0500 schrieb Scott Kostyshak:
> Will Koji know that the string should be translated? I assumed that
> he
> just searches for text that is marked as English. Should we just
> notify
> him directly or should we make a "Changelog-sweave.lyx" file?
Either solution see
On Fri, Nov 03, 2017 at 09:09:59AM +, Jürgen Spitzmüller wrote:
> Am Freitag, den 03.11.2017, 00:10 -0400 schrieb Scott Kostyshak:
> > On Thu, Nov 02, 2017 at 08:43:35PM +, Kornel Benko wrote:
> > > Am Donnerstag, 2. November 2017 um 21:37:25, schrieb Jürgen
> > > Spitzmüller
> > > > Am Do
Am Freitag, den 03.11.2017, 00:10 -0400 schrieb Scott Kostyshak:
> On Thu, Nov 02, 2017 at 08:43:35PM +, Kornel Benko wrote:
> > Am Donnerstag, 2. November 2017 um 21:37:25, schrieb Jürgen
> > Spitzmüller
> > > Am Donnerstag, den 02.11.2017, 21:17 +0100 schrieb Kornel Benko:
> > > > examples/j
On Thu, Nov 02, 2017 at 08:43:35PM +, Kornel Benko wrote:
> Am Donnerstag, 2. November 2017 um 21:37:25, schrieb Jürgen Spitzmüller
>
> > Am Donnerstag, den 02.11.2017, 21:17 +0100 schrieb Kornel Benko:
> > > examples/ja/sweave.lyx not compilable. Resetting the English text at
> > > section 5
Am Donnerstag, 2. November 2017 um 21:37:25, schrieb Jürgen Spitzmüller
> Am Donnerstag, den 02.11.2017, 21:17 +0100 schrieb Kornel Benko:
> > examples/ja/sweave.lyx not compilable. Resetting the English text at
> > section 5
> > 'The user manual ofSweave is at'
> > cures the problem.
>
> A
Am Donnerstag, den 02.11.2017, 21:17 +0100 schrieb Kornel Benko:
> examples/ja/sweave.lyx not compilable. Resetting the English text at
> section 5
> 'The user manual ofSweave is at'
> cures the problem.
A more sane solution is to set "Language package" in Document Settings
from "None" to "A
On Thu, Nov 02, 2017 at 08:17:16PM +, Kornel Benko wrote:
> examples/ja/sweave.lyx not compilable. Resetting the English text at section 5
> 'The user manual ofSweave is at'
> cures the problem.
>
> The error message is
>
> l.
Helge Hafting wrote:
> We see that "selectlanguage" inside an index entry cause trouble.
> Therefore, LyX should not emit language change commands inside index
> entries. This is probably not necessary either - an index entry will
> not be hyphenated so language support is not needed there.
Unless
On 05. sep. 2011 08:49, Jean-Pierre Chrétien wrote:
[...]
After investigation, this error is due to the fact that the word
'Flottants' is in French in the index inset within title of section
4.6.3. The exported latex construct
\subsection{More Information\index{Flottants@\selectlanguage{french}%
Am 05.09.2011 08:49, schrieb Jean-Pierre Chrétien:
After investigation, this error is due to the fact that the word 'Flottants' is
in French in the
index inset within title of section 4.6.3. The exported latex construct
\subsection{More Information\index{Flottants@\selectlanguage{french}%
Flot
Hello
On Mon, Aug 29, 2011 at 10:03 AM, Rufat Mirza wrote:
> Hello dear Lyx developers,
> I'm quite a new lyx user (before, I was using just Latex).The Lyx
> project is great. Keep going. I feel that a minor contribution from my
> side can somehow be also helpful. In the Turkish translation,
>
T
On 2011-06-10, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Jean-Pierre Chrétien wrote:
>> So to come back to the previous thread, if Enrico's patch is not applied,
>> which one of the "}\n" strings in output_latex.cpp should be modified ?
> See attachment.
Jürgen Spitzmüller lyx.org> writes:
>
> Jean-Pierre Chrétien wrote:
> > So to come back to the previous thread, if Enrico's patch is not applied,
> > which one of the "}\n" strings in output_latex.cpp should be modified ?
>
> See attachment.
>
> The new bool is introduced because pending_newli
Jean-Pierre Chrétien wrote:
> So to come back to the previous thread, if Enrico's patch is not applied,
> which one of the "}\n" strings in output_latex.cpp should be modified ?
See attachment.
The new bool is introduced because pending_newline is used multiple times.
Jürgen
Index: src/output_la
On 2011-06-09, Jean-Pierre Chrétien wrote:
> Guenter Milde users.berlios.de> writes:
> I added an exemple in my test file in bugzilla to show the spaces
> added in various situations:
> http://www.lyx.org/trac/attachment/ticket/7607/test_foreign_in_Flex1.lyx
> You may open it both with lyx-2.0.0
Guenter Milde users.berlios.de> writes:
> > Sure, output_export.cpp seems wrong there. Shouln't all "}\n" strings
> > be replaced by "}%\n" strings there ?
>
> There are many examples where the line-break does not need to be
> escaped (end of environments, say).
> (It took me some time to find o
On 2011-06-09, Jean-Pierre Chrétien wrote:
> Guenter Milde users.berlios.de> writes:
>> > This exports as
>> > \code{\selectlanguage{english}%
>> > word\selectlanguage{french}
>> > }
>> There correct LaTeX code is:
>> \code{\selectlanguage{english}%
>> - word\selectlanguage{french}
>> + word\
Guenter Milde users.berlios.de> writes:
>
> > This exports as
>
> > \code{\selectlanguage{english}%
> > word\selectlanguage{french}
> > }
>
> There correct LaTeX code is:
>
> \code{\selectlanguage{english}%
> - word\selectlanguage{french}
> + word\selectlanguage{french}%
> }
>
> The commen
Guenter Milde wrote:
> Could you be more specific? I could not find more missing line-break
> escapes in lib/languages, but there might be more somewhere in the C code.
I'll try to make a test case when I find time (too busy currently). The issue
often arises when I use a foreign language for a c
On 06/06/2011 07:45 AM, Guenter Milde wrote:
> On 2011-06-06, Jürgen Spitzmüller wrote:
>> Guenter Milde wrote:
This white space disappears by properly escaping
the line breaks in \addto\extrasfrench{...}.
>>> So I hope it is easily fixed for 2.1 (or 2.0.1).
>> Sure. Just add the % to lan
On 2011-06-06, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> > This white space disappears by properly escaping
>> > the line breaks in \addto\extrasfrench{...}.
>> So I hope it is easily fixed for 2.1 (or 2.0.1).
> Sure. Just add the % to languages and be done with it.
Here is the patch f
Guenter Milde wrote:
> > This white space disappears by properly escaping
> > the line breaks in \addto\extrasfrench{...}.
>
> So I hope it is easily fixed for 2.1 (or 2.0.1).
Sure. Just add the % to languages and be done with it.
There are still other whitespace issues, though, with language ch
On 2011-06-05, Enrico Forestieri wrote:
>> > As \selectlanguage introduces spurious white space, it should not be used
>> > in "inline" content.
>> It does not. Only the incorrect use (with a non-escaped line-break)
>> does.
> That is yet another source of white space. However, even escaping the
On Sun, Jun 05, 2011 at 09:08:11PM +, Guenter Milde wrote:
> On 2011-06-03, Enrico Forestieri wrote:
> > On Fri, Jun 03, 2011 at 09:47:35AM +0200, Jean-Marc Lasgouttes wrote:
>
> >> Le 03/06/11 02:07, Enrico Forestieri a écrit :
> >> >See attached patch.
>
> >> I am not sure I understand the
On 2011-06-03, Enrico Forestieri wrote:
> On Fri, Jun 03, 2011 at 09:47:35AM +0200, Jean-Marc Lasgouttes wrote:
>> Le 03/06/11 02:07, Enrico Forestieri a écrit :
>> >See attached patch.
>> I am not sure I understand the patch, but how come one has to decide
>> based on isMainText()? What about a
On 2011-06-02, Jean-Pierre Chrétien wrote:
> [-- Type: text/plain, Encoding: 7bit --]
> Hello,
> I checked the pdf export of the French version of the Custolization
> manual, and I discovered a number of extra spaces after constructs
> where a word remained in English inside a Flex inset
...
>
On Fri, Jun 03, 2011 at 02:32:16PM +0200, Jean-Marc Lasgouttes wrote:
> Le 03/06/11 14:26, Enrico Forestieri a écrit :
> >As \selectlanguage introduces spurious white space, it should not be used
> >in "inline" content. As \selectlanguage is only used when the language is
> >changed at the very be
Le 03/06/11 14:26, Enrico Forestieri a écrit :
As \selectlanguage introduces spurious white space, it should not be used
in "inline" content. As \selectlanguage is only used when the language is
changed at the very beginning of a LyX paragraph, checking isMainText()
ensures that it is used only a
On Fri, Jun 03, 2011 at 09:47:35AM +0200, Jean-Marc Lasgouttes wrote:
> Le 03/06/11 02:07, Enrico Forestieri a écrit :
> >See attached patch.
>
> I am not sure I understand the patch, but how come one has to decide
> based on isMainText()? What about a Flex inset in a Note? What would
> the situa
Jean-Marc Lasgouttes wrote:
> > See attached patch.
>
> I am not sure I understand the patch, but how come one has to decide
> based on isMainText()? What about a Flex inset in a Note? What would the
> situation be different?
I am not sure either. I often face such problems for environments (qu
Enrico Forestieri lyx.org> writes:
>
> See attached patch.
>
Tested with trunk, as it belongs to it, and it solves the problem both in
Customization.lyx and in my simple test example.
I created a ticket
http://www.lyx.org/trac/ticket/7607
--
Jean-Pierre
Le 03/06/11 02:07, Enrico Forestieri a écrit :
See attached patch.
I am not sure I understand the patch, but how come one has to decide
based on isMainText()? What about a Flex inset in a Note? What would the
situation be different?
JMarc
On 06/02/2011 08:07 PM, Enrico Forestieri wrote:
> On Thu, Jun 02, 2011 at 11:36:08PM +0200, Enrico Forestieri wrote:
>
>> On Thu, Jun 02, 2011 at 03:56:42PM -0400, Richard Heck wrote:
>>
>>> I think so. I've had a look at it, and it's more difficult than it might
>>> seem. A comment in the code (t
On Thu, Jun 02, 2011 at 11:36:08PM +0200, Enrico Forestieri wrote:
> On Thu, Jun 02, 2011 at 03:56:42PM -0400, Richard Heck wrote:
>
> > I think so. I've had a look at it, and it's more difficult than it might
> > seem. A comment in the code (this is output_latex.cpp, lines 770ff)
> > suggests th
On Thu, Jun 02, 2011 at 03:56:42PM -0400, Richard Heck wrote:
> On 06/02/2011 12:37 PM, Jean-Pierre Chrétien wrote:
> > Hello,
> >
> > I checked the pdf export of the French version of the Custolization
> > manual, and I discovered a number of extra spaces after constructs
> > where a word remaine
On 06/02/2011 12:37 PM, Jean-Pierre Chrétien wrote:
> Hello,
>
> I checked the pdf export of the French version of the Custolization
> manual, and I discovered a number of extra spaces after constructs
> where a word remained in English inside a Flex inset, e.g.:
>
> \begin_inset Flex Code
> status
On 23-3-2011 20:44, Georg Baum wrote:
Georg Baum wrote:
Thanks for the explanation. Meanwhile I have added special code to cover
the current situation. Anything that does not make this special code
useless is no improvement. Changing the .po files is no good idea IMHO,
since I see zh_CN and zh_
Georg Baum wrote:
> Thanks for the explanation. Meanwhile I have added special code to cover
> the current situation. Anything that does not make this special code
> useless is no improvement. Changing the .po files is no good idea IMHO,
> since I see zh_CN and zh_TW in my system, but neither zh_H
Jürgen Spitzmüller wrote:
> Jürgen Spitzmüller wrote:
>> It seems to me that zh_TW is "more" correct for traditional Chinese,
>> although it seems to be more a convention than strictly conforming
>> (since TW and CN are not country codes).
>
> The official tags seem to be zh-Hant (traditional Chi
Jürgen Spitzmüller wrote:
It seems to me that zh_TW is "more" correct for traditional Chinese,
although it seems to be more a convention than strictly conforming
(since TW and CN are not country codes).
The official tags seem to be zh-Hant (traditional Chinese) and zh-Hans
(simplified Chinese)
Georg Baum wrote:
lib/languages has zh_CN as language code both for chinese (simplified) and
chinese (traditional), while the .po files are named zh_CN.po (simplified)
and zh_TW.po (traditional).
What is correct? Do we need to change lib/languages, or do I need a special
case in the layout trans
Jürgen Spitzmüller wrote:
> Here's the patch.
polished version that also handles multipart documents.
Jürgen
Index: src/Buffer.h
===
--- src/Buffer.h (Revision 33363)
+++ src/Buffer.h (Arbeitskopie)
@@ -375,6 +375,8 @@
///
bool
Jürgen Spitzmüller wrote:
> > Agreed. However, currently language switching is far too cumbersome:
> >
> > a) Edit>Text-style>Custom>...>select from an "endless" list, or
> >
> > b) M-x language ... (where you need to know the correct name of the
> > desired language)
>
> I
Hi All,
After reading all the inputs, I really wet worried about my installation so I
decided to uninstall Lyx and reinstall it again, accepting all default settings
proposed by the installer.
Starting the program from the installer gave me the menus in english. After
closing the program and
Paul A. Rubin wrote:
Angus Leeming wrote:
FWIW, I just opened a doc with spaces in the path (though not in the
file name itself) and instant preview worked fine. I did have to
scroll through the document to induce instant preview to update the
display, but that seems to be normal modus operan
Angus Leeming wrote:
FWIW, I just opened a doc with spaces in the path (though not in the
file name itself) and instant preview worked fine. I did have to
scroll through the document to induce instant preview to update the
display, but that seems to be normal modus operandi. (This was
1.3.6
Paul A. Rubin wrote:
Angus Leeming wrote:
Eugenio Guevara wrote:
4.. Instant preview works fine if there is no spaces in pathnames
- I think it's a problem of python or one of this support programs
Again, this is odd. Others have reported that Instant preview works
well.
FWIW, I just ope
Angus Leeming wrote:
Eugenio Guevara wrote:
4.. Instant preview works fine if there is no spaces in pathnames
- I think it's a problem of python or one of this support programs
Again, this is odd. Others have reported that Instant preview works
well.
FWIW, I just opened a doc with spac
Angus Leeming wrote:
> Eugenio Guevara wrote:
>> By the way, a very minor glitch, "Español" instead of "Espagñol"
> How odd! I thought I'd fixed this one. Must look deeper.
I've just committed the fix to cvs.
--
Angus
Eugenio Guevara wrote:
> Hi,
Hi, Eugenio.
> I just downloaded Lyx 1.3.6pre-Version17 and found some minor
> "problems", as follows
> 1.. Selection of language for menus during install process does
> not work (version 16 was ok). Menus are in english.
I'll investigate this evening.
> By t
Andre Poenitz <[EMAIL PROTECTED]> writes:
> I wrote:
> > What, *any* of those? Doesn't your orthography comittee tell you which
> > one is the right one? Ours would.
>
> Not really. The would try. Then we'd have 17 different attempts to
> pass a law (one per state + a federal one), than we'd ask
On Wed, Jan 12, 2005 at 02:11:46PM +0100, [EMAIL PROTECTED] wrote:
> On Wed, 12 Jan 2005, Lars Gullik Bjønnes wrote:
>
> > Andreas Vox <[EMAIL PROTECTED]> writes:
> >
> > | Maybe a typo for "Okay, do key" ? Can you say "do key" instead of "press
> > key" ?
> >
> > Why would you "do Key"? What
On Wed, Jan 12, 2005 at 01:42:36PM +, Angus Leeming wrote:
> It is widely rumoured that the the English got rid of sex sometime in the
> Middle Ages. It just makes things too difficult. It is also widely
> rumoured that the Victorians tried to extend this removal from the
> lamguage to everyday
On Wed, Jan 12, 2005 at 03:45:00AM +, Andreas Vox wrote:
> John Weiss <[EMAIL PROTECTED]> writes:
>
> <
> < On Sat, Jan 01, 2005 at 01:38:07PM +, Angus Leeming wrote:
> < > Ok, dokey.
> <
> < Lanuage Lesson for all international colleagues:
Hear here. ;-)
> < The correct phrase
> < is
On Thu, Jan 13, 2005 at 09:18:50AM +0200, Martin Vermeer wrote:
> On Wed, 2005-01-12 at 05:45, Andreas Vox wrote:
> > What, *any* of those? Doesn't your orthography comittee tell you which
> > one is the right one? Ours would.
>
> And then you would proceed ignoring them and go on writing it the
John Weiss <[EMAIL PROTECTED]> writes:
| On Wed, Jan 12, 2005 at 11:35:51AM +0100, Lars Gullik Bjønnes wrote:
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>>
>> | While we're at it, however, what's a "lanuage"?
>>
>> that is the lesson you just received.
>
| Methinks Angus refers to the missing
On Wed, Jan 12, 2005 at 02:11:46PM +0100, [EMAIL PROTECTED] wrote:
> On Wed, 12 Jan 2005, Lars Gullik Bjønnes wrote:
>
> > Andreas Vox <[EMAIL PROTECTED]> writes:
> >
> > | Maybe a typo for "Okay, do key" ? Can you say "do key" instead of "press
> > key" ?
> >
> > Why would you "do Key"? What
On Wed, Jan 12, 2005 at 03:45:00AM +, Andreas Vox wrote:
>
> What, *any* of those? Doesn't your orthography comittee tell you which
> one is the right one? Ours would.
Yeah, but no one pays any attention to them. :)
Besides, that's an informal enough phrase, anyhow, so as not to
have nor ne
On Wed, Jan 12, 2005 at 11:35:51AM +0100, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | While we're at it, however, what's a "lanuage"?
>
> that is the lesson you just received.
Methinks Angus refers to the missing 'g' in "language" in one of
sentences.
I blame it
Martin Vermeer <[EMAIL PROTECTED]> writes:
> > What, *any* of those? Doesn't your orthography comittee tell you which
> > one is the right one? Ours would.
>
> And then you would proceed ignoring them and go on writing it the way
> you always have written it...
Oh no, definitely not!
1. If you
On Wed, 2005-01-12 at 05:45, Andreas Vox wrote:
> John Weiss <[EMAIL PROTECTED]> writes:
...
> < Or, if you prefer: "Okee dokee"
> < "Okey-dokey"
> < "Okee-dokee"
> < "Okie dokie"
> < "Okie-dokie"
>
> What, *any* of
[EMAIL PROTECTED] writes:
| On Wed, 12 Jan 2005, Lars Gullik Bjønnes wrote:
>> Why would you "do Key"? What wrong has Key ever done to you?
>
| Maybe Key is of the opposite sex?
The you should at least ask Key for permission.
--
Lgb
[EMAIL PROTECTED] wrote:
>> | Maybe a typo for "Okay, do key" ? Can you say "do key" instead of
>> | "press key" ?
>>
>> Why would you "do Key"? What wrong has Key ever done to you?
>
> Maybe Key is of the opposite sex?
It is widely rumoured that the the English got rid of sex sometime in the
M
On Wed, 12 Jan 2005, Lars Gullik Bjønnes wrote:
> Andreas Vox <[EMAIL PROTECTED]> writes:
>
> | Maybe a typo for "Okay, do key" ? Can you say "do key" instead of "press
> key" ?
>
> Why would you "do Key"? What wrong has Key ever done to you?
Maybe Key is of the opposite sex?
/C
--
Christi
Angus Leeming <[EMAIL PROTECTED]> writes:
| While we're at it, however, what's a "lanuage"?
that is the lesson you just received.
--
Lgb
John Weiss wrote:
> On Sat, Jan 01, 2005 at 01:38:07PM +, Angus Leeming wrote:
>> Ok, dokey.
>
> Lanuage Lesson for all international colleagues: The correct phrase
> is, "Okey dokey".
>
> Or, if you prefer: "Okee dokee"
> "Okey-dokey"
> "Okee-dokee"
Andreas Vox <[EMAIL PROTECTED]> writes:
| Maybe a typo for "Okay, do key" ? Can you say "do key" instead of "press
key" ?
Why would you "do Key"? What wrong has Key ever done to you?
--
Lgb
John Weiss <[EMAIL PROTECTED]> writes:
<
< On Sat, Jan 01, 2005 at 01:38:07PM +, Angus Leeming wrote:
< > Ok, dokey.
<
< Lanuage Lesson for all international colleagues: The correct phrase
< is, "Okey dokey".
<
< Or, if you prefer: "Okee dokee"
< "Okey-dokey"
<
On Thu, Nov 06, 2003 at 01:41:13PM +0100, Andre Poenitz wrote:
> I don't know, I think either is ok. I'd probably use 'allowSpellCheck'
> as this indicates exactly its single purpose and we'd separate two
> ideas ('language is unknown', 'dont spellcheck') cleanly.
Please don't call it unknown tho
Andre Poenitz wrote:
> I don't know, I think either is ok. I'd probably use 'allowSpellCheck'
> as this indicates exactly its single purpose and we'd separate two
> ideas ('language is unknown', 'dont spellcheck') cleanly.
I'll do that then.
Regards, Alfredo
On Thu, Nov 06, 2003 at 01:32:54PM +0100, Alfredo Braunstein wrote:
> Shouldn't we have a language "ignore" or "unknown"?
> I think this is a must in a lot of situations.
Why not.
> Incidentally, we could then put ERT text automatically in that
> language and automatically solve the spellcheck-er
On Thursday 02 May 2002 10:44 am, Juergen Vigna wrote:
> On 30-Apr-2002 Claus Hindsgaul wrote:
> > Sorry, no luck with the new patch
>
> Ok thanks for the file I can recreate the crash with it and your
> explanation. I fixed this now hopefully but there is IMO a greater problem
> to fix in GCItem.
On 30-Apr-2002 Claus Hindsgaul wrote:
> Sorry, no luck with the new patch
Ok thanks for the file I can recreate the crash with it and your explanation.
I fixed this now hopefully but there is IMO a greater problem to fix in GCItem.
(this is for Angus)
IMO that this function is wrong:
void GCac
tir, 2002-04-30 kl. 17:47 skrev John Levon:
> Can you please provide a screenshot. I've tried varying line lengths and
> am unable to cause any problems
Sure.
This picture were made after:
* Opening LyX
* Deactivating "Rescale bitmap fonts" (so the bug351-file will
loa
On Tue, Apr 30, 2002 at 03:08:18PM +0200, Claus Hindsgaul wrote:
> > * If I maximize the LyX window before opening the document, the
> > bug
> ... is not triggered.
Can you please provide a screenshot. I've tried varying line lengths and
am unable to cause any problems
thanks
Ooops, I my posting missed some words and called for an extra comment...
tir, 2002-04-30 kl. 14:01 skrev Claus Hindsgaul:
> The problem seems to be tied tightly to the line wrapping on the WYSIWYM
> screen WHILE LOADING IMAGES.
>
> * If I maximize the LyX window before opening the docume
Sorry, no luck with the new patch
But I found a very good lead!
The problem seems to be tied tightly to the line wrapping on the WYSIWYM
screen WHILE LOADING IMAGES.
* If I maximize the LyX window before opening the document, the
bug can
* Choosing Danish language si
On 29-Apr-2002 Claus Hindsgaul wrote:
> By request, I have obtained the following backtraces from valgrind
> (attached) and gdb from a LyX 1.2.0CVS of today with Juergens patch
> applied compiled with --disable-optimization. They were both made doing
> the same thing as in my prior backtraces.
[s
By request, I have obtained the following backtraces from valgrind
(attached) and gdb from a LyX 1.2.0CVS of today with Juergens patch
applied compiled with --disable-optimization. They were both made doing
the same thing as in my prior backtraces.
Claus Hindsgaul
gdb:
(gdb) run
Starting progra
Claus Hindsgaul <[EMAIL PROTECTED]> writes:
| man, 2002-04-29 kl. 15:42 skrev Juergen Vigna:
>> Thanks for your backtraces (and patience). Would it be possible for you to
>> apply the attached patch to an updated cvs version and see if that fixes the
>> problem for you?
>
| Thank you for the patc
man, 2002-04-29 kl. 15:42 skrev Juergen Vigna:
> Thanks for your backtraces (and patience). Would it be possible for you to
> apply the attached patch to an updated cvs version and see if that fixes the
> problem for you?
Thank you for the patch. Unfortunately it did not avoid the crash. Would
yo
On 24-Apr-2002 Claus Hindsgaul wrote:
> ons, 2002-04-24 kl. 15:27 skrev John Levon:
>> > Did that help?
>>
>> No ! Look at the backtrace yourself then look at the source they are
>> completely different. Perhaps a valgrind bug ?
Thanks for your backtraces (and patience). Would it be possible fo
On Thu, Apr 25, 2002 at 12:13:06AM +0200, Claus Hindsgaul wrote:
> Or perhaps an optimized executable...
Still a valgrind bug ! Or binutils, or gcc ... anyway
> I have recompiled LyX without optimizations, deleting all "-O" options
> in the configure file (since 'configure --disable-optimizatio
1 - 100 of 150 matches
Mail list logo
