On 02-Aug-2001 Jean-Marc Lasgouttes wrote:
> Asger> Now, language is not an ortogonal properties of text. Instead,
> Asger> it's a coupled property. You can not logically change the
> Asger> language of the text without changing the text itself, and vice
> Asger> versa.
>
> So what is the langu
On 01-Aug-2001 Asger K. Alstrup Nielsen wrote:
> On Wed, 1 Aug 2001, Dekel Tsur wrote:
>
>> Let's look at the two reason why you added the language_inherit
>
> Juergen, I actually agreed with Dekel in this case.
>
> Let me try to explain why:
[snip]
Well I agree with both of you! I always sai
On Wed, 1 Aug 2001, Dekel Tsur wrote:
> Let's look at the two reason why you added the language_inherit
Juergen, I actually agreed with Dekel in this case.
Let me try to explain why:
Font, font size, italic, bold, color. These are all ortogonal
properties of text: You can change them without c
On Mon, Jul 30, 2001 at 09:38:56AM +0200, Juergen Vigna wrote:
>
Let's look at the two reason why you added the language_inherit
1) Consistency with other font properties
2) Previously, a special code was needed to set the language when creating
an empty insettext. So the change simplifies th
On 28-Jul-2001 Dekel Tsur wrote:
> 1. When you copy text from English document to French document, the
> language of the text remains language_inherit, so the text will now be
> considered as French instead of English.
> When copying to the clipboard, you do need to store the language of the
> d
On Fri, Jul 27, 2001 at 03:03:07PM +0200, Juergen Vigna wrote:
> > We didn't need inherit language before, so we don't need one now.
>
> You surely meant we didn't have an inherit_language before and we have
> seen we need one so that all of it is working correctly, isn't it?
Up until a week ago
On 27-Jul-2001 Dekel Tsur wrote:
> Because the language property is not inherited.
> If you write some text in an English document, and then copy it to a French
> document, the language of the text should remain English (there are
> exceptions if for example you copy source code).
You're right
On Fri, Jul 27, 2001 at 02:15:56PM +0200, Jean-Marc Lasgouttes wrote:
> Dekel> Why the language in insetERT is changed to ignore_language ???
>
> We need a way to say inherit language. This works well for everything
> in a font when one specifies ALL_INHERIT, _except_ for language. Why?
Because
On 27-Jul-2001 Jean-Marc Lasgouttes wrote:
> The interesting methods in LyX Font are
>
> /** Reduce font to fall back to template where possible.
> Equal fields are reduced to INHERIT */
> void reduce(LyXFont const & tmplt);
>
> /// Realize font from a template (IN
On 27-Jul-2001 Dekel Tsur wrote:
> Why the language in insetERT is changed to ignore_language ???
No your're right it should be inherit_language and now it is!
> The correct way for implementing insetERT is to have an InsetEditor and use
Your free to provide one!
> it instead of insetText. C
On Fri, Jul 27, 2001 at 12:03:04PM +0200, Juergen Vigna wrote:
>
> On 27-Jul-2001 Jean-Marc Lasgouttes wrote:
>
> > And it should probably not be output in the .lyx file. Probably a few
> > changes in lyxfont.C will be enough.
>
> It HAS to be outputed, BUT as the document_wide language, otherw
On 27-Jul-2001 Jean-Marc Lasgouttes wrote:
> And it should probably not be output in the .lyx file. Probably a few
> changes in lyxfont.C will be enough.
It HAS to be outputed, BUT as the document_wide language, otherwise we're
not able to switch back and remain in the previously defined langua
Juergen Vigna wrote:
>
> > I've stripped out those \lang directives in emacs, and now the file loads
> > fine in today's CVS. What's the deal?
>
> This seems strange to me as it seems I changed the code in text.C so that
> the font of a "ignore" language is not displayed as different! Ignore sho
On 25-Jul-2001 Mike Ressler wrote:
> I'm converting the docs from 1.1.6 to 1.2.0. When trying to translate the
> UG, the conversion of the LaTeX code in Chapter 7 to an inset failed (or
> at least complained) as expected. What I didn't expect was that all the
> text in the inset was underlined bl
I'm converting the docs from 1.1.6 to 1.2.0. When trying to translate the
UG, the conversion of the LaTeX code in Chapter 7 to an inset failed (or
at least complained) as expected. What I didn't expect was that all the
text in the inset was underlined blue, indicating a language change.
Indeed, wh
15 matches
Mail list logo
