On Thu, Sep 22, 2011 at 5:16 PM, Helge Hafting wrote:
>> because the word "Paris3" was initially in English and changling th
>> language of a documentdoesn't affect its existing content at all, only
>> the default language. I agree this can be misleading and we prbably need
>> an option to change
On 16. sep. 2011 16:00, Abdelrazak Younes wrote:
[...]
An example:
start a new document, main language is English, be default
write two words: Berlin Paris
Change the language of the first word to German (through Text Style).
Now the document is multilingual.
Yes: German and English
So far
On 20/09/2011 10:11 AM, Guenter Milde wrote:
On 2011-09-19, Liviu Andronic wrote:
On Mon, Sep 19, 2011 at 9:16 AM, Guenter Milde wrote:
(This is also reminiscent of the debate on automatically setting fonts
for new documents other than the 'default' CM;
However, with font-encoding T1, t
On 2011-09-19, Liviu Andronic wrote:
> On Mon, Sep 19, 2011 at 9:16 AM, Guenter Milde wrote:
>>> (This is also reminiscent of the debate on automatically setting fonts
>>> for new documents other than the 'default' CM;
...
However, with font-encoding T1, the used font is not CM but either DC (a
b
On 2011-09-19, Stephan Witt wrote:
> Am 19.09.2011 um 09:16 schrieb Guenter Milde:
>> On 2011-09-18, Liviu Andronic wrote:
>>> On Sun, Sep 18, 2011 at 6:00 PM, Stephan Witt wrote:
Why do you think it makes any sense to use an foreign default for new
documents while the interface languag
We could handle a new language, say "default". Changing document language
would mean to change the handling of this parts only.
Explicitly marked parts should stay as they are.
Maybe LyX could put all the foreign language parts in the environments
\begin{otherlanguage}{esperanto}
\end{otherlan
On Mon, Sep 19, 2011 at 9:16 AM, Guenter Milde wrote:
>> (This is also reminiscent of the debate on automatically setting fonts
>> for new documents other than the 'default' CM; the prevailing opinion
>> was that LaTeX classes most of teh times were setting their own
>> defaults (sometimes non-CM
Am Montag, 19. September 2011 schrieb Guenter Milde:
> On 2011-09-18, Enrico Forestieri wrote:
> > On Sun, Sep 18, 2011 at 06:20:24PM +0200, Stephan Witt wrote:
> >> That's not 100% correct. It does the change for all matching text.
> >> With your patch applied, when changing from default to German
Am 19.09.2011 um 09:16 schrieb Guenter Milde:
> On 2011-09-18, Liviu Andronic wrote:
>> On Sun, Sep 18, 2011 at 6:00 PM, Stephan Witt wrote:
>
>>> Why do you think it makes any sense to use an foreign default for new
>>> documents while the interface language and the help files are all in
>>> my
On 2011-09-18, Enrico Forestieri wrote:
> On Sun, Sep 18, 2011 at 06:20:24PM +0200, Stephan Witt wrote:
>> That's not 100% correct. It does the change for all matching text.
>> With your patch applied, when changing from default to German for a mixed
>> document (some parts in German some parts de
On 2011-09-18, Stephan Witt wrote:
> Am 18.09.2011 um 21:36 schrieb Liviu Andronic:
>> On Sun, Sep 18, 2011 at 8:58 PM, Stephan Witt wrote:
>>> I cannot believe any user expects English as default document language
>>> when using LyX the first time in a non-english environment.
>> I we start pl
On 2011-09-18, Liviu Andronic wrote:
> On Sun, Sep 18, 2011 at 6:00 PM, Stephan Witt wrote:
>> Why do you think it makes any sense to use an foreign default for new
>> documents while the interface language and the help files are all in
>> my current locale. That's why I'd propose to set the defa
On Sun, Sep 18, 2011 at 08:58:14PM +0200, Stephan Witt wrote:
> That was not my intention. I did second your patch already.
> What I wanted is to find an explanation for the current state.
Sorry, I must have misunderstood you.
--
Enrico
Am 18.09.2011 um 21:36 schrieb Liviu Andronic:
> On Sun, Sep 18, 2011 at 8:58 PM, Stephan Witt wrote:
>> I cannot believe any user expects English as default document language
>> when using LyX the first time in a non-english environment.
>>
> I we start playing with that, this could become a t
On Sun, Sep 18, 2011 at 8:58 PM, Stephan Witt wrote:
> I cannot believe any user expects English as default document language
> when using LyX the first time in a non-english environment.
>
I we start playing with that, this could become a thorny issue. Should
we start using the locale to guess &
Am 18.09.2011 um 19:05 schrieb Enrico Forestieri:
> On Sun, Sep 18, 2011 at 06:20:24PM +0200, Stephan Witt wrote:
>
>> That's not 100% correct. It does the change for all matching text.
>> With your patch applied, when changing from default to German for a mixed
>> document (some parts in German
On Sun, Sep 18, 2011 at 6:00 PM, Stephan Witt wrote:
> Yes, I meant the status bar text "Font: default". Not showing the
> language portion of the font (it should be separate anyway) is ok
> if the default value is what the user expects.
>
I guess the user should expect that, unless explicitly men
On Sun, Sep 18, 2011 at 06:20:24PM +0200, Stephan Witt wrote:
> That's not 100% correct. It does the change for all matching text.
> With your patch applied, when changing from default to German for a mixed
> document (some parts in German some parts default) and changing again to
> English all Ge
Am 18.09.2011 um 17:52 schrieb Enrico Forestieri:
> On Sun, Sep 18, 2011 at 05:11:31PM +0200, Stephan Witt wrote:
>
>> Am 18.09.2011 um 14:38 schrieb Enrico Forestieri:
>>
>>> On Sun, Sep 18, 2011 at 02:08:28PM +0200, Stephan Witt wrote:
>>>
We have at least two errors here:
1. the wr
Am 18.09.2011 um 17:28 schrieb Liviu Andronic:
> I haven't followed the entire debate too attentively, but see two
> remarks below.
>
>
> On Sun, Sep 18, 2011 at 5:11 PM, Stephan Witt wrote:
>> If it is English, we can at least display "Default (English)" or something
>> similar.
>> It it is d
On Sun, Sep 18, 2011 at 05:11:31PM +0200, Stephan Witt wrote:
> Am 18.09.2011 um 14:38 schrieb Enrico Forestieri:
>
> > On Sun, Sep 18, 2011 at 02:08:28PM +0200, Stephan Witt wrote:
> >
> >> We have at least two errors here:
> >> 1. the wrong default language is choosen
> >
> > I don't think so
I haven't followed the entire debate too attentively, but see two
remarks below.
On Sun, Sep 18, 2011 at 5:11 PM, Stephan Witt wrote:
> If it is English, we can at least display "Default (English)" or something
> similar.
> It it is dynamically assigned I wouldn't present "Default" as default.
Am 18.09.2011 um 14:38 schrieb Enrico Forestieri:
> On Sun, Sep 18, 2011 at 02:08:28PM +0200, Stephan Witt wrote:
>
>> Am 17.09.2011 um 20:56 schrieb Enrico Forestieri:
>>
>>> On Sun, Sep 11, 2011 at 06:42:37PM +0200, PhilipPirrip wrote:
When one chooses to change the global document
The only thing left would be to handle, in BufferView.cpp, the case
when LTR is changed to RTL, so that one (= the cursor) can leave the
old text (i.e. text that was in a LTR language).
I am not sure what you mean. If you want to write in a RTL language and
the cursor is right after a LTR word
On 09/18/2011 02:08 PM, Stephan Witt wrote:
Because this seems to be a common workflow:
* you start LyX with your local GUI environment
* your GUI language is German -or-Italian-
* you start typing and for text language is... the default
* later you realize that this default is English
* now you
On Sun, Sep 18, 2011 at 2:38 PM, Enrico Forestieri wrote:
>> To correct this the check for isMultiLingual() should be replaced by a
>> confirmation dialog were the user can decide, IMHO.
>
> Yet another bothering dialog to answer...
>
I would agree with Enrico here: a dialogue would be overkill fo
On Sun, Sep 18, 2011 at 02:08:28PM +0200, Stephan Witt wrote:
> Am 17.09.2011 um 20:56 schrieb Enrico Forestieri:
>
> > On Sun, Sep 11, 2011 at 06:42:37PM +0200, PhilipPirrip wrote:
> >>
> >> When one chooses to change the global document language in the
> >> Document Settings dialog, can someon
Am 17.09.2011 um 20:56 schrieb Enrico Forestieri:
> On Sun, Sep 11, 2011 at 06:42:37PM +0200, PhilipPirrip wrote:
>>
>> When one chooses to change the global document language in the
>> Document Settings dialog, can someone tell me why is the test being
>> made (now in BufferView.cpp, line 1905)
On Sun, Sep 18, 2011 at 12:05:07AM +0200, PhilipPirrip wrote:
> The only thing left would be to handle, in BufferView.cpp, the case
> when LTR is changed to RTL, so that one (= the cursor) can leave the
> old text (i.e. text that was in a LTR language).
I am not sure what you mean. If you want to
On 09/17/2011 08:56 PM, Enrico Forestieri wrote:
I think you are right and that test is wrong. I checked it with RTL
and LTR languages and I also observe the wrong behavior you report.
Without that test everything goes as one expects. So I am going to
commit the attached patch, unless someone ca
On Sun, Sep 11, 2011 at 06:42:37PM +0200, PhilipPirrip wrote:
>
> When one chooses to change the global document language in the
> Document Settings dialog, can someone tell me why is the test being
> made (now in BufferView.cpp, line 1905) on
> !buffer_.isMultiLingual().
I think you are right a
Question 2:
Why is the word Paris now marked as being in English (pure guess)?
because the word "Paris3" was initially in English and changling th
language of a document doesn't affect its existing content at all, only
the default language. I agree this can be misleading and we prbably need
a
On 11/09/2011 18:42, PhilipPirrip wrote:
When one chooses to change the global document language in the
Document Settings dialog, can someone tell me why is the test being
made (now in BufferView.cpp, line 1905) on !buffer_.isMultiLingual().
I'm asking that because I'm trying to find *which o
On Thu, Sep 15, 2011 at 6:52 PM, PhilipPirrip wrote:
> Thank you, Liviu.
> In fact, there's already a bug report #7681 related to the same thing (as i
> see it), and I thought it would be more convenient to have some discussion
> here. Now I'm confused :)
> #7681 is a bug report for one special ca
On 15/09/2011 6:52 PM, PhilipPirrip wrote:
Thank you, Liviu.
In fact, there's already a bug report #7681 related to the same thing
(as i see it), and I thought it would be more convenient to have some
discussion here. Now I'm confused :)
#7681 is a bug report for one special case, but the same ha
PhilipPirrip wrote:
> #7681 is a bug report for one special case, but the same happens in many
> others.
> #7681 is marked as "fixedintrunk" "fixedinbranch", and I'm not sure how
> much attention it can get as such, nor if I'm allowed to change the
> keywords.
> Should I expand the report at the
Thank you, Liviu.
In fact, there's already a bug report #7681 related to the same thing
(as i see it), and I thought it would be more convenient to have some
discussion here. Now I'm confused :)
#7681 is a bug report for one special case, but the same happens in many
others.
#7681 is marked as
Hello
I'm acutely interested in a fix to this issue, but unfortunately I
couldn't help you with any guidance for the code. I believe that you
didn't get many answers because your e-mail contained a lot of
specifics, but didn't clearly state the issue at the beginning.
I would suggest that you sear
No one to answer?
It's really hard to work with this bug (feature?) in multilingual documents.
When one chooses to change the global document language in the Document
Settings dialog, can someone tell me why is the test being made (now in
BufferView.cpp, line 1905) on !buffer_.isMultiLingual().
I'm asking that because I'm trying to find *which other code* is
responsible for changing th
40 matches
Mail list logo
