On Thu, Mar 27, 2025 at 09:46:45PM +0900, Koji Yokota wrote:
>
> > 2025/03/25 22:07、Scott Kostyshak
> > のメール:
> > On Tue, Mar 25, 2025 at 12:41:32PM +0100, Kornel Benko wrote:
> >> So 'Object/Element' will it be. Koji, would you like to make the change?
> >
> > To be clear (because I was not bef
On Fri, Mar 21, 2025 at 01:25:03PM +0100, Kornel Benko wrote:
> I'd like to change the strin 'Color name' in GuiPrefs.cpp:1028 to something
> more
> appropriate.
>
> It describes a set of objects (not colors) which appears in a specified color.
>
> The strin
Am Tue, 25 Mar 2025 08:12:19 +0900
schrieb Koji Yokota :
> > On Fri, Mar 21, 2025 at 01:25:03PM +0100, Kornel Benko wrote:
> >> I'd like to change the strin 'Color name' in GuiPrefs.cpp:1028 to
> >> something more
> >> appropriate.
> >&g
Am Thu, 27 Mar 2025 14:48:00 +0100
schrieb Scott Kostyshak :
> On Thu, Mar 27, 2025 at 10:35:41PM +0900, Yokota K. wrote:
> >
> > > 2025/03/27 22:23、Scott Kostyshak のメール:
> > > Just a note that I'm fine with "Object/Element" or "Object or Element"
> > > since I think Kornel pointed out that not
> 2025/03/27 22:23、Scott Kostyshak のメール:
> Just a note that I'm fine with "Object/Element" or "Object or Element"
> since I think Kornel pointed out that not everything is an object (like
> for "background”).
I see. It seems I missed Kornel’s mail. Then let’s go with "Object/Element”.
Koji--
ly
On Thu, Mar 27, 2025 at 10:35:41PM +0900, Yokota K. wrote:
>
> > 2025/03/27 22:23、Scott Kostyshak のメール:
> > Just a note that I'm fine with "Object/Element" or "Object or Element"
> > since I think Kornel pointed out that not everything is an object (like
> > for "background”).
>
> I see. It seems
> 2025/03/25 22:07、Scott Kostyshak
> のメール:
> On Tue, Mar 25, 2025 at 12:41:32PM +0100, Kornel Benko wrote:
>> So 'Object/Element' will it be. Koji, would you like to make the change?
>
> To be clear (because I was not before), I don't propose
> "Object/Element". I propose either "Object" or "Ele
On Tue, Mar 25, 2025 at 12:41:32PM +0100, Kornel Benko wrote:
> Am Tue, 25 Mar 2025 08:12:19 +0900
> schrieb Koji Yokota :
>
> > > On Fri, Mar 21, 2025 at 01:25:03PM +0100, Kornel Benko wrote:
> > >> I'd like to change the strin 'Color name' i
> On Fri, Mar 21, 2025 at 01:25:03PM +0100, Kornel Benko wrote:
>> I'd like to change the strin 'Color name' in GuiPrefs.cpp:1028 to something
>> more
>> appropriate.
>>
>> It describes a set of objects (not colors) which appears in a specified
I'd like to change the strin 'Color name' in GuiPrefs.cpp:1028 to something more
appropriate.
It describes a set of objects (not colors) which appears in a specified color.
The string could be something like
'Colored object' or
'Colored element'
Kor
Am Samstag, den 06.01.2018, 10:35 +0100 schrieb Jürgen Spitzmüller:
> Probably a minor glitch in lyx2lyx.
Identified and fixed in master. Please confirm.
Jürgen
>
> Jürgen
>
> >
> > Kornel
signature.asc
Description: This is a digitally signed message part
Am Samstag, 6. Januar 2018 um 10:35:32, schrieb Jürgen Spitzmüller
> Am Samstag, den 06.01.2018, 10:30 +0100 schrieb Kornel Benko:
> > Maybe the structure checking is not good enough. The respecting lines
> > are:
> >
> > \begin_layout Plain Layout
> > Caption:\begin_inset space \hspace{}
> > \l
Am Samstag, 6. Januar 2018 um 10:19:36, schrieb Jürgen Spitzmüller
> Am Samstag, den 06.01.2018, 10:13 +0100 schrieb Kornel Benko:
> > -- check structures of /usr2/src/lyx/lyx-
> > git/lib/doc/ja/Customization.lyx
> > expected \end_layout, got \end_inset instead at
> > /BUILD/BUILDMint17/BuildLyx
Am Samstag, den 06.01.2018, 10:30 +0100 schrieb Kornel Benko:
> Maybe the structure checking is not good enough. The respecting lines
> are:
>
> \begin_layout Plain Layout
> Caption:\begin_inset space \hspace{}
> \length 0dd
> \end_inset
>
> That is '\begin_inset' is not on the start of line.
wh
Am Samstag, 6. Januar 2018 um 10:13:58, schrieb Kornel Benko
> > What is exactly failing?
>
> This is the message I get running export/doc/ja/Customization_lyx22
>
>
> -- check structures of /usr2/src/lyx/lyx-git/lib/doc/ja/Customization.lyx
> expected \end_layout, got \end_inset instead at
>
Am Samstag, den 06.01.2018, 10:13 +0100 schrieb Kornel Benko:
> -- check structures of /usr2/src/lyx/lyx-
> git/lib/doc/ja/Customization.lyx
> expected \end_layout, got \end_inset instead at
> /BUILD/BUILDMint17/BuildLyxGitQt5.8self-gcc7.1/autotests/out-
> home/ja/Customization.22.lyx:15724
Can yo
a3
> > > Author: Juergen Spitzmueller
> > > Date: Sat Jan 6 09:31:24 2018 +0100
> > >
> > > Customization: some color name fixes.
> > >
> > > (cherry picked from commit
> > > 44670d477831f56feef0de37f205f4b9c0e7ce09)
> >
;
> > Customization: some color name fixes.
> >
> > (cherry picked from commit
> > 44670d477831f56feef0de37f205f4b9c0e7ce09)
> > ---
> > lib/doc/Customization.lyx|8
> > lib/doc/de/Customization.lyx | 16 --
Am Samstag, 6. Januar 2018 um 09:32:58, schrieb Juergen Spitzmueller
> commit 01281ca670efedccbf46e35265680130290ea8a3
> Author: Juergen Spitzmueller
> Date: Sat Jan 6 09:31:24 2018 +0100
>
> Customization: some color name fixes.
>
> (cher
Am 26.02.2008 um 02:37 schrieb rgheck:
Pavel Sanda wrote:
hi,
with the current trunk i get this warning:
QColor::setNamedColor: Unknown color name 'grey70'
Me, too...though we need to fix the color stuff still, anyway.
Fixed that locally already. Will commit soon.
Stefan
>> with the current trunk i get this warning:
>> QColor::setNamedColor: Unknown color name 'grey70'
>>
>>
> Me, too...though we need to fix the color stuff still, anyway.
part of completion stuff, Stefan already know about it.
pavel
Pavel Sanda wrote:
hi,
with the current trunk i get this warning:
QColor::setNamedColor: Unknown color name 'grey70'
Me, too...though we need to fix the color stuff still, anyway.
rh
hi,
with the current trunk i get this warning:
QColor::setNamedColor: Unknown color name 'grey70'
pavel
23 matches
Mail list logo
