Re: Re: Error in build process on Windows 7, using Visual Studio 2012

[Kornel Benko]

Am Dienstag, 16. Oktober 2012 um 17:14:31, schrieb Stephan Witt 
st.w...@gmx.net
 Am 16.10.2012 um 13:21 schrieb Kornel Benko kor...@lyx.org:
 
  Am Dienstag, 16. Oktober 2012 um 12:06:08, schrieb Kornel Benko 
  kor...@lyx.org
   
   Versuchen wir es mit der einfachen Version zuerst.
   
 Kornel
   
   
  Ich habe eine leise Ahnung, warum es nicht mit Xcode ging, vorausgesetzt 
  die test-CMakeLists Datei war OK.
  Wir haben zwei unterschiedliche targets. Einmal das executable (erzeugbar 
  mit add_executable()), und
  einmal als Daten in BUILD/support/tests/regfiles/ erzeugt werden.
  Also BUILD/bin/Debug/check_convert versus 
  BUILD/support/tests/regfiles/check_convert.
   
  Vielleicht verträgt cmake-erzeugtes Xcode so etwas nicht.
   
  Anhang: Eine neue Komplett-Version.
   
  Kornel
  CMakeLists.txt
 
 Ld /Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug/check_convert normal 
 x86_64
 cd /Users/stephan/git/lyx
 setenv MACOSX_DEPLOYMENT_TARGET 10.8
 
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
  -arch x86_64 -isysroot 
 /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk
  -L/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug 
 -L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/Debug 
 -L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug 
 -L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/Debug 
 -L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug 
 -F/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug 
 -F/Users/stephan/git/lyx-build/qt-4.8.3-frameworks-cocoa-x86_64/lib -filelist 
 /Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/LyX.build/Debug/check_convert.build/Objects-normal/x86_64/check_convert.LinkFileList
  -mmacosx-version-min=10.8 -Wl,-search_paths_first 
 -Wl,-headerpad_max_install_names 
 /Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/libsupport.a 
 /Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/libboost_signals.a 
 /Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/libboost_regex.a 
 -framework QtCore /usr/lib/libz.dylib 
 /Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/libintl.a 
 /usr/lib/libiconv.dylib -lobjc -framework AppKit -framework CoreFoundation -o 
 /Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug/check_convert
 
 ld: warning: directory not found for option 
 '-L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/Debug'
 ld: warning: directory not found for option 
 '-L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/Debug'
 Undefined symbols for architecture x86_64:
   QDesktopServices::storageLocation(QDesktopServices::StandardLocation), 
 referenced from:
   lyx::support::(anonymous 
 namespace)::get_document_dir(lyx::support::FileName const) in 
 libsupport.a(Package.o)
   lyx::support::(anonymous 
 namespace)::get_default_user_support_dir(lyx::support::FileName const) in 
 libsupport.a(Package.o)
 ld: symbol(s) not found for architecture x86_64
 clang: error: linker command failed with exit code 1 (use -v to see 
 invocation)
 
 We need to link the QtGui framework too.
 
 Should I commit it?

Yes please. But split the line. It makes it more readable (for me)

Kornel

signature.asc
Description: This is a digitally signed message part.

Qt issue? (Re: #8374: missing/bad display of dots and cdots)

[Pavel Sanda]

LyX Ticket Tracker wrote:
 #8374: missing/bad display of dots and cdots
 +--
  Reporter:  MarkBravington  |   Owner:  poenitz
  Type:  defect  |  Status:  new
  Priority:  normal  |   Milestone:
 Component:  mathed  | Version:  2.0.4
  Severity:  normal  |  Resolution:
  Keywords:  |
 +--

Is there anyone around who can see rendering of three dots instead of two dots
when typing \cdots in mathed? The code looks correct and unchanged compared
to older versions where it worked.

If yes, what Qt version do you use, it might be some issue related to rounding
in painter, because even tiny change makes the middle dot magically appear.

Pavel

 -- 
 Ticket URL: http://www.lyx.org/trac/ticket/8374#comment:2
 The LyX Project http://www.lyx.org/
 LyX -- The Document Processor
diff --git a/src/mathed/MathSupport.cpp b/src/mathed/MathSupport.cpp
index 82de873..614ef4e 100644
--- a/src/mathed/MathSupport.cpp
+++ b/src/mathed/MathSupport.cpp
@@ -212,7 +212,7 @@ double const ot[] = {
 
 double const hline3[] = {
1, 0.1,   0,  0.15,  0,
-   1, 0.475, 0,  0.525, 0,
+   1, 0.472, 0,  0.525, 0,
1, 0.85,  0,  0.9,   0,
0
 };

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
 OK thanks for the tips. I'm guessing it's OK to update the format in
 trunk when changing the manuals?

For additional manual it's OK. IIRC Uwe wanted the manuals under his
maintenance to remain in 2.0.x for easy synchronization.

 Attached is a patch to update the Additional manual. Is it OK?

Yes. Feel free to push similar paragraph to branch.
Pavel

Re: About LyX menus usability.

[Pavel Sanda]

Tommaso Cucinotta wrote:
 However, nobody seems to care about marginal note. So, I would readily 
 move it to the Insert-Note sub-menu. At least, it will be 1 less entry in 
 the crowded Insert menu.

I think margin/foot note should be rather coupled together...

 I also noticed that the [Insert]-[LyX Note] function is called merely 
 Insert Note in the toolbar tooltip. Should that be changed to Insert LyX 
 Note as well ?

As you wish ;)

 (assuming the user grasps the difference between a LyX note and a comment 
 note -- what is it supposed to be ? Both don't seem to show up in the PDF, 
 but only the comment goes into the latex).

Exactly. Those three in note submenu can be also easily mutated one to 
another,
see e.g. context menu.

Pavel

Re: Re: Re: Error in build process on Windows 7, using Visual Studio 2012

[Kornel Benko]

Am Dienstag, 16. Oktober 2012 um 18:06:18, schrieb Vincent van Ravesteijn 
v...@lyx.org
 
 
 
 
  Yes, but nonetheless I'd like to have it resolved.
 
  I would like to know:
 
 
 
  Is the problem in
 
  * Compiling: maybe a missing include reference (something not defined?)
 
  * Linking: maybe missing needed library (which externals are not resolved?)
 
 
 
 
  Kornel
 
 
 
 Last time I checked I had the following problems:
 
 - there is a missing #include string,
 - iconv.lib and intl.lib are not used by the linker,

Is this a problem? Stephan added a third lib today. Not a problem on linux,
but we may use also a platform specific solution iff needed.

 - the executable could not be found (it is in a Debug directory),

Should be OK now

 - to be able to run the executable, it should be installed along with the
 necessary dlls,
 
 I will check the current status later.

 Vincent

Thanks
Kornel

signature.asc
Description: This is a digitally signed message part.

Re: About LyX menus usability.

[Jean-Marc Lasgouttes]

Le 17/10/2012 10:30, Pavel Sanda a écrit :

Tommaso Cucinotta wrote:

However, nobody seems to care about marginal note. So, I would readily
move it to the Insert-Note sub-menu. At least, it will be 1 less entry in
the crowded Insert menu.


I think margin/foot note should be rather coupled together...


I also noticed that the [Insert]-[LyX Note] function is called merely
Insert Note in the toolbar tooltip. Should that be changed to Insert LyX
Note as well ?


As you wish ;)


LyX Note is a bad name I think. Sticky note? Yellow note? Note?

JMarc

Re: About LyX menus usability.

[Jürgen Spitzmüller]

2012/10/17 Pavel Sanda:
 Tommaso Cucinotta wrote:
 However, nobody seems to care about marginal note. So, I would readily
 move it to the Insert-Note sub-menu. At least, it will be 1 less entry in
 the crowded Insert menu.

 I think margin/foot note should be rather coupled together...

Agreed. Marginal notes and footnotes are conceptually different to the
LyX notes, despite the similar name. LyX notes are rather editiorial
tools (adressed at the author/editor; except for greyed out maybe,
which is a problematic case in itself). Footnotes, endnotes and
marginal notes are part of the document proper. Since they are so
important in scientific writing, moving them to a second level would
be a bad sign for a mainly scientific writing application.

For my lectures, I use marginal notes quite a lot, and I would be
quite annoyed if they wouldn't be easily reachable anymore (via
Alt+E+R in my German l7n currently).

Jürgen

Re: About LyX menus usability.

[Jean-Marc Lasgouttes]

Le 17/10/2012 12:26, Jürgen Spitzmüller a écrit :

Agreed. Marginal notes and footnotes are conceptually different to the
LyX notes, despite the similar name. LyX notes are rather editiorial
tools (adressed at the author/editor; except for greyed out maybe,
which is a problematic case in itself). Footnotes, endnotes and
marginal notes are part of the document proper. Since they are so
important in scientific writing, moving them to a second level would
be a bad sign for a mainly scientific writing application.


+1

JMarc

Re: Qt issue? (Re: #8374: missing/bad display of dots and cdots)

[Richard Heck]

On 10/17/2012 04:11 AM, Pavel Sanda wrote:

LyX Ticket Tracker wrote:

#8374: missing/bad display of dots and cdots
+--
  Reporter:  MarkBravington  |   Owner:  poenitz
  Type:  defect  |  Status:  new
  Priority:  normal  |   Milestone:
Component:  mathed  | Version:  2.0.4
  Severity:  normal  |  Resolution:
  Keywords:  |
+--

Is there anyone around who can see rendering of three dots instead of two dots 
when typing \cdots in mathed? The code looks correct and unchanged compared to 
older versions where it worked.

Two dots here. I noticed this recently. Qt is 4.8.2.

rh

Re: Qt issue? (Re: #8374: missing/bad display of dots and cdots)

[Jürgen Spitzmüller]

2012/10/17 Richard Heck:
 Is there anyone around who can see rendering of three dots instead of two
 dots when typing \cdots in mathed? The code looks correct and unchanged
 compared to older versions where it worked.

 Two dots here. I noticed this recently. Qt is 4.8.2.

I get three, both for \dots and \cdots. Qt 4.8.2 as well.

Jürgen

Re: Qt issue? (Re: #8374: missing/bad display of dots and cdots)

[Jürgen Spitzmüller]

2012/10/17 Jürgen Spitzmüller sp...@lyx.org:
 I get three, both for \dots and \cdots. Qt 4.8.2 as well.

However, scaling matters! I have 200 dpi. If I scale down, I get two
dots at ~140 dpi and one dot at ~100 dpi. At some scale rates (such as
150), the dots even disappear completely.

Jürgen

Re: Re: Qt issue? (Re: #8374: missing/bad display of dots and cdots)

[Kornel Benko]

Am Mittwoch, 17. Oktober 2012 um 16:37:27, schrieb Jürgen Spitzmüller 
sp...@lyx.org
 2012/10/17 Richard Heck:
  Is there anyone around who can see rendering of three dots instead of two
  dots when typing \cdots in mathed? The code looks correct and unchanged
  compared to older versions where it worked.
 
  Two dots here. I noticed this recently. Qt is 4.8.2.
 
 I get three, both for \dots and \cdots. Qt 4.8.2 as well.
 
 Jürgen

Same here, three both, Qt 4.8.2

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: About LyX menus usability.

[Jean-Marc Lasgouttes]

Le 15/10/12 22:41, Andrew Parsloe a écrit :

Anyone who can drop pleonastic into a sentence hardly needs a native
English speaker.


Well I am able to check in a dictionary that the French word 
pléonastique actually translates to English (it looks like it comes 
from English actually). But of course looking like somebody who casually 
drops pleonastic in a sentence is an art :)


But knowing which one of pane or panel is more suited to UI is more 
delicate.


JMarc

Re: About USE_META_KEYBINDING (Stephan?)

[Jean-Marc Lasgouttes]

Le 17/10/12 07:41, Stephan Witt a écrit :

Why not just define USE_META_KEYBINDING in configure for the mac build?


Yes, this can be done.

Other options are
1) to remove the USE_META_KEYBINDING macro
2) to handle Alt and Meta separately on all platforms


This is what I though afterwards. Is the problem that all M- bindings 
should become A-? It is a lesser problem now that we hav prefs2prefs 
which can update bind files.


JMarc

Re: About LyX menus usability.

[Tommaso Cucinotta]

On 17/10/12 11:26, Jürgen Spitzmüller wrote:

Marginal notes and footnotes are conceptually different to the
LyX notes, despite the similar name. LyX notes are rather editiorial
tools (adressed at the author/editor; except for greyed out maybe,
which is a problematic case in itself). Footnotes, endnotes and
marginal notes are part of the document proper. Since they are so
important in scientific writing, moving them to a second level would
be a bad sign for a mainly scientific writing application.

For my lectures, I use marginal notes quite a lot, and I would be
quite annoyed if they wouldn't be easily reachable anymore (via
Alt+E+R in my German l7n currently).


I see your point. I'm just trying to think from a new user perspective:

-) I need to insert a footnote
-) so I go straight to Insert- menu,
-) scroll it down, find the Note- sub-menu,
-) cannot see any footnote
-) conclusion: this tool doesn't even support footnotes :-)!
-) sudo apt-get purge LyX :-(...

exacerbating the last step/conclusions of course, it's just that we all 
probably know very well how to customize the UI, etc (and surely we 
all agree that what LyX probably lacks is a Tools-Customize menus... 
tool for re-arranging menus). The experienced user knows where things 
are, he's used to that.
A UI is effective when it allows new users to find stuff intuitively and 
quickly, isn't it ?


One last thing: how does one add an end note in LyX ?

Bye,

T.

Re: About LyX menus usability.

[Tommaso Cucinotta]

On 09/10/12 14:44, Charles de Miramon wrote:

Like Pavel, I find the Insert menu too long. Maybe, everything that relates
to the life cycle of the document (annotations, branches) could go into
'Document'


Do you mean: moving Insert-Branch to document ? AFAIU, it's really a 
local edit, so it should stay in Insert.


What about Version Control operations ? They probably affect the whole 
document, so move them to Document ? However, it's quite common to find 
that stuff under File.


What about File-New Window / Close Window ? These 2 just seem to me 
they belong to the View menu ?


And, conceputally speaking, perhaps Insert-Graphics... should be 
grouped with Insert-File-... sub-menu (think of 
Insert-File-ExternalMaterial). Again, inserting figures is very very 
common, and I guess there's a nice button readily available on the 
toolbar. If you're about to complain about using keyboard to reach the 
menu entry without using the mouse, I can anticipate that Ctrl+G, on my 
Ubuntu, produces a telephone character -- why ? why doesn't it 
activate Insert-Graphics ?


Of course, everyone opinion is very welcome. UI is so subjective

T.

Re: About LyX menus usability.

[Jean-Marc Lasgouttes]

Le 18/10/12 00:30, Tommaso Cucinotta a écrit :

Do you mean: moving Insert-Branch to document ? AFAIU, it's really a
local edit, so it should stay in Insert.


Yes.


What about Version Control operations ? They probably affect the whole
document, so move them to Document ? However, it's quite common to find
that stuff under File.

What about File-New Window / Close Window ? These 2 just seem to me
they belong to the View menu ?


Or create a Window(s) menu? Other programs tend to use that.


If you're about to complain about using keyboard to reach the
menu entry without using the mouse, I can anticipate that Ctrl+G, on my
Ubuntu, produces a telephone character -- why ? why doesn't it
activate Insert-Graphics ?


This could be added indeed.

JMarc

Re: About LyX menus usability.

[Tommaso Cucinotta]

On 17/10/12 23:19, Tommaso Cucinotta wrote:

On 17/10/12 11:26, Jürgen Spitzmüller wrote:

For my lectures, I use marginal notes quite a lot, and I would be
quite annoyed if they wouldn't be easily reachable anymore (via
Alt+E+R in my German l7n currently).


Further alternative/proposal: what about a single menu entry 
Insert-Note..., popping up a dialog, with a radio-box allowing to 
choose the type of note (and I can easily imagine a text/label right on 
its right explaining what these different notes are), where footnote 
would be automatically selected (so just type Enter and you're done with 
that -- most common type of note I guess), then marginal note could be 
the 2nd choice (so, [Down][Enter] and you're down), and so on... ?


I'm just realizing there's already such a dialog: context-menu on LyX 
note, for example, then Settings... So, what's really bad in making the 
UI for all of these notes all the same ? Want a note ? Just insert a 
note, then you get immediately the dialog, you pick your choice (and see 
these notes shortly explained if you're newbie), then click [Ok] button, 
or [Enter]. You could even have a preference voice \default_note_type 
with possible types ask (dialog), LyX, footnote, marginal, ... 
(you got the point).


Comments welcome.

T.

Re: $$e not set on import -- import of .Rnw (knitr) fails

[Jean-Marc Lasgouttes]

Le 17/10/12 06:09, Scott Kostyshak a écrit :

I have this problem on master and 2.0.x.

An empty $$e variable is being passed to the converter script on
import because the document is not open yet:
command = subst(command, token_encoding, buffer ?
buffer-params().encoding().iconvName() : string());

Should $$e be set to the default encoding of a new document?

Or is this something that the converter script should deal with?

To reproduce:
1. Open examples/knitr.lyx
2. Export to Rnw (knitr)
3. Import the Rnw (knitr) file

I get an error after (3) because lyxknitr.R is expecting a non-empty
$$e argument.


Stupid question; where is importation of knitr files defined in converters?

JMarc

Re: About LyX menus usability.

[Jean-Marc Lasgouttes]

Le 18/10/12 00:40, Tommaso Cucinotta a écrit :

On 17/10/12 23:19, Tommaso Cucinotta wrote:

On 17/10/12 11:26, Jürgen Spitzmüller wrote:

For my lectures, I use marginal notes quite a lot, and I would be
quite annoyed if they wouldn't be easily reachable anymore (via
Alt+E+R in my German l7n currently).


Further alternative/proposal: what about a single menu entry
Insert-Note..., popping up a dialog, with a radio-box allowing to
choose the type of note (and I can easily imagine a text/label right on
its right explaining what these different notes are), where footnote
would be automatically selected (so just type Enter and you're done with
that -- most common type of note I guess), then marginal note could be
the 2nd choice (so, [Down][Enter] and you're down), and so on... ?

I'm just realizing there's already such a dialog: context-menu on LyX
note, for example, then Settings... So, what's really bad in making the
UI for all of these notes all the same ? Want a note ? Just insert a
note, then you get immediately the dialog, you pick your choice (and see
these notes shortly explained if you're newbie), then click [Ok] button,
or [Enter]. You could even have a preference voice \default_note_type
with possible types ask (dialog), LyX, footnote, marginal, ...
(you got the point).


Yes, but the point is that there is note and note. I agree that our 
current UI is not very good at separating the two (markup vs author 
annotation), but it is not a reason for making this worse.


In some way, LyX Note could belong somewhere with change tracking, as an 
authoring tool of some sort. But I do not have anything to propose.

It could also be a special branch which is (always?) off.

JMarc

Re: Press about LyX

[Jerry]

Who among the LyX developers has the power to edit the press page, 
http://www.lyx.org/PressAboutLyX?
Daniel has written an article about LyX for the HowToAnswer web site and would 
like to get it linked from the LyX press page. Surely this benefits the LyX 
community as well.

Jerry


On Oct 16, 2012, at 6:01 PM, Jerry wrote:

 Hi Daniel,
 
 Thanks for this nice article. May I make a suggestion? I think you should 
 show at least one example of rendered LyX output so that the reader 
 understands better that what you see is not what is shown on the LyX screen, 
 but much better and better than typical Word output.
 
 Jerry
 (not a developer)
 
 On Oct 16, 2012, at 6:10 AM, HowToAnswer wrote:
 
 Hi,
 
 I recently finished my article about LyX, here it is :
 
 http://www.howtoanswer.com/a-quick-review-of-lyx--9.html
 
 According to this page, I should notify someone from LyX.
 
 http://www.lyx.org/PressAboutLyX
 
 How can I get in touch with someone from LyX community
 and (if possible) get listed there?
 
 Regards,
 Daniel
 

Re: $$e not set on import -- import of .Rnw (knitr) fails

[Scott Kostyshak]

On Wed, Oct 17, 2012 at 6:52 PM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
 Le 17/10/12 06:09, Scott Kostyshak a écrit :

 I have this problem on master and 2.0.x.

 An empty $$e variable is being passed to the converter script on
 import because the document is not open yet:
 command = subst(command, token_encoding, buffer ?
 buffer-params().encoding().iconvName() : string());

 Should $$e be set to the default encoding of a new document?

 Or is this something that the converter script should deal with?

 To reproduce:
 1. Open examples/knitr.lyx
 2. Export to Rnw (knitr)
 3. Import the Rnw (knitr) file

 I get an error after (3) because lyxknitr.R is expecting a non-empty
 $$e argument.


 Stupid question; where is importation of knitr files defined in converters?

Rnw (knitr) - latex (plain)
The converter is currently:
Rscript --verbose --no-save --no-restore $$s/scripts/lyxknitr.R $$p$$i
$$p$$o $$e $$r
When I change this to the following, import works:
Rscript --verbose --no-save --no-restore $$s/scripts/lyxknitr.R $$p$$i
$$p$$o ISO-8859-15 $$r

Scott

Re: Manuals contain outdated break-paragraph-keep-layout

[Uwe Stöhr]

Am 29.09.2012 18:22, schrieb Pavel Sanda:


break-paragraph-keep-layout is LFUN outdated for a long time,
we still have it in these manuals:

lib/doc/de/UserGuide.lyx
lib/doc/eu/Customization.lyx
lib/doc/eu/UserGuide.lyx
lib/doc/sk/UserGuide.lyx


Thanks for the hint. I have now removed the references to this deprecated function and also updated 
the description to reflect the current behaviour in lists.


regards Uwe

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Wed, Oct 17, 2012 at 4:15 AM, Pavel Sanda sa...@lyx.org wrote:
 Scott Kostyshak wrote:
 OK thanks for the tips. I'm guessing it's OK to update the format in
 trunk when changing the manuals?

 For additional manual it's OK. IIRC Uwe wanted the manuals under his
 maintenance to remain in 2.0.x for easy synchronization.

 Attached is a patch to update the Additional manual. Is it OK?

 Yes. Feel free to push similar paragraph to branch.

OK, it's in trunk and branch.

Thanks,

Scott

Re: About LyX menus usability.

[Andrew Parsloe]

On 18/10/2012 11:15 a.m., Jean-Marc Lasgouttes wrote:

Le 15/10/12 22:41, Andrew Parsloe a écrit :

Anyone who can drop pleonastic into a sentence hardly needs a native
English speaker.


Well I am able to check in a dictionary that the French word
pléonastique actually translates to English (it looks like it comes
from English actually). But of course looking like somebody who casually
drops pleonastic in a sentence is an art :)

But knowing which one of pane or panel is more suited to UI is more
delicate.

JMarc

I should have added in relation to pane/panel, that windows have panes, 
doors have panels -- which encourages flights of fancy: instead of a 
windowing system, a dooring system, where one has panels with door knobs 
and keys and locks to be opened with appropriate mouse drags and clicks, 
and instead of drop-down menus, little doors that open ...


Andrew

Re: About LyX menus usability.

[Liviu Andronic]

On Thu, Oct 18, 2012 at 12:15 AM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
 But knowing which one of pane or panel is more suited to UI is more
 delicate.

I'm no native English speaker either, but from my experience with FOSS
programs the Source and Messages thingies that LyX has are 'panes'.

However the Outline thingy looks more like a 'panel' to me; at least
this is how Opera and Midori call a similar artefact that can be
popped up on the left hand side. But Evince has another such artefact
and calls it 'Side pane'. So this paragraph really is useless.

Liviu

Re: About LyX menus usability.

[Jürgen Spitzmüller]

2012/10/18 Jean-Marc Lasgouttes lasgout...@lyx.org:
 Yes, but the point is that there is note and note. I agree that our current
 UI is not very good at separating the two (markup vs author annotation), but
 it is not a reason for making this worse.

I wonder if the term Annotation for LyX Notes and comments would be
better. I think less people would associate that with footnotes and
marginal notes.

How are these things called in Word Processors and PDF Readers in English UIs?

BTW, in the German translation, notes are (correctly) translated as
Notiz. This already disambiguates the phenomenon. Nobody would
subsume footnotes under Notiz (but rather under Anmerkungen). This
also means that German users would be completely lost if footnotes and
margin notes would indeed be added to the Notes/Notiz submenu.

Jürgen

Re: Re: Error in build process on Windows 7, using Visual Studio 2012

[Kornel Benko]

Am Dienstag, 16. Oktober 2012 um 17:14:31, schrieb Stephan Witt 

> Am 16.10.2012 um 13:21 schrieb Kornel Benko :
> 
> > Am Dienstag, 16. Oktober 2012 um 12:06:08, schrieb Kornel Benko 
> > 
> > > 
> > > Versuchen wir es mit der einfachen Version zuerst.
> > > 
> > >   Kornel
> >  
> >  
> > Ich habe eine leise Ahnung, warum es nicht mit Xcode ging, vorausgesetzt 
> > die test-CMakeLists Datei war OK.
> > Wir haben zwei unterschiedliche targets. Einmal das executable (erzeugbar 
> > mit add_executable()), und
> > einmal als Daten in /support/tests/regfiles/ erzeugt werden.
> > Also /bin/Debug/check_convert versus 
> > /support/tests/regfiles/check_convert.
> >  
> > Vielleicht verträgt cmake-erzeugtes Xcode so etwas nicht.
> >  
> > Anhang: Eine neue Komplett-Version.
> >  
> > Kornel
> > 
> 
> Ld /Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug/check_convert normal 
> x86_64
> cd /Users/stephan/git/lyx
> setenv MACOSX_DEPLOYMENT_TARGET 10.8
> 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
>  -arch x86_64 -isysroot 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk
>  -L/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug 
> -L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/Debug 
> -L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug 
> -L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/Debug 
> -L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug 
> -F/Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug 
> -F/Users/stephan/git/lyx-build/qt-4.8.3-frameworks-cocoa-x86_64/lib -filelist 
> /Users/stephan/git/lyx-build/cmake/2.1.0dev/src/support/tests/LyX.build/Debug/check_convert.build/Objects-normal/x86_64/check_convert.LinkFileList
>  -mmacosx-version-min=10.8 -Wl,-search_paths_first 
> -Wl,-headerpad_max_install_names 
> /Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/libsupport.a 
> /Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/libboost_signals.a 
> /Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/libboost_regex.a 
> -framework QtCore /usr/lib/libz.dylib 
> /Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/libintl.a 
> /usr/lib/libiconv.dylib -lobjc -framework AppKit -framework CoreFoundation -o 
> /Users/stephan/git/lyx-build/cmake/2.1.0dev/bin/Debug/check_convert
> 
> ld: warning: directory not found for option 
> '-L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/Debug'
> ld: warning: directory not found for option 
> '-L/Users/stephan/git/lyx-build/cmake/2.1.0dev/lib/Debug/Debug'
> Undefined symbols for architecture x86_64:
>   "QDesktopServices::storageLocation(QDesktopServices::StandardLocation)", 
> referenced from:
>   lyx::support::(anonymous 
> namespace)::get_document_dir(lyx::support::FileName const&) in 
> libsupport.a(Package.o)
>   lyx::support::(anonymous 
> namespace)::get_default_user_support_dir(lyx::support::FileName const&) in 
> libsupport.a(Package.o)
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> 
> We need to link the QtGui framework too.
> 
> Should I commit it?

Yes please. But split the line. It makes it more readable (for me)

Kornel

signature.asc
Description: This is a digitally signed message part.

Qt issue? (Re: #8374: missing/bad display of dots and cdots)

[Pavel Sanda]

LyX Ticket Tracker wrote:
> #8374: missing/bad display of dots and cdots
> +--
>  Reporter:  MarkBravington  |   Owner:  poenitz
>  Type:  defect  |  Status:  new
>  Priority:  normal  |   Milestone:
> Component:  mathed  | Version:  2.0.4
>  Severity:  normal  |  Resolution:
>  Keywords:  |
> +--

Is there anyone around who can see rendering of three dots instead of two dots
when typing \cdots in mathed? The code looks correct and unchanged compared
to older versions where it worked.

If yes, what Qt version do you use, it might be some issue related to rounding
in painter, because even tiny change makes the middle dot magically appear.

Pavel

> -- 
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor
diff --git a/src/mathed/MathSupport.cpp b/src/mathed/MathSupport.cpp
index 82de873..614ef4e 100644
--- a/src/mathed/MathSupport.cpp
+++ b/src/mathed/MathSupport.cpp
@@ -212,7 +212,7 @@ double const ot[] = {
 
 double const hline3[] = {
1, 0.1,   0,  0.15,  0,
-   1, 0.475, 0,  0.525, 0,
+   1, 0.472, 0,  0.525, 0,
1, 0.85,  0,  0.9,   0,
0
 };

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
> OK thanks for the tips. I'm guessing it's OK to update the format in
> trunk when changing the manuals?

For additional manual it's OK. IIRC Uwe wanted the manuals under his
maintenance to remain in 2.0.x for easy synchronization.

> Attached is a patch to update the Additional manual. Is it OK?

Yes. Feel free to push similar paragraph to branch.
Pavel

Re: About LyX menus & usability.

[Pavel Sanda]

Tommaso Cucinotta wrote:
> However, nobody seems to care about "marginal note". So, I would readily 
> move it to the Insert->Note sub-menu. At least, it will be 1 less entry in 
> the "crowded" Insert menu.

I think margin/foot note should be rather coupled together...

> I also noticed that the [Insert]->[LyX Note] function is called merely 
> "Insert Note" in the toolbar tooltip. Should that be changed to "Insert LyX 
> Note" as well ?

As you wish ;)

> (assuming the user grasps the difference between a LyX note and a "comment" 
> note -- what is it supposed to be ? Both don't seem to show up in the PDF, 
> but only the "comment" goes into the latex).

Exactly. Those three in note submenu can be also easily "mutated" one to 
another,
see e.g. context menu.

Pavel

Re: Re: Re: Error in build process on Windows 7, using Visual Studio 2012

[Kornel Benko]

Am Dienstag, 16. Oktober 2012 um 18:06:18, schrieb Vincent van Ravesteijn 

> >
> >
> >
> >
> > Yes, but nonetheless I'd like to have it resolved.
> >
> > I would like to know:
> >
> >
> >
> > Is the problem in
> >
> > * Compiling: maybe a missing include reference (something not defined?)
> >
> > * Linking: maybe missing needed library (which externals are not resolved?)
> >
> >
> >
> >
> > Kornel
> >
> 
> 
> Last time I checked I had the following problems:
> 
> - there is a missing #include ,
> - iconv.lib and intl.lib are not used by the linker,

Is this a problem? Stephan added a third lib today. Not a problem on linux,
but we may use also a platform specific solution iff needed.

> - the executable could not be found (it is in a "Debug" directory),

Should be OK now

> - to be able to run the executable, it should be installed along with the
> necessary dlls,
> 
> I will check the current status later.
>
> Vincent

Thanks
Kornel

signature.asc
Description: This is a digitally signed message part.

Re: About LyX menus & usability.

[Jean-Marc Lasgouttes]

Le 17/10/2012 10:30, Pavel Sanda a écrit :

Tommaso Cucinotta wrote:

However, nobody seems to care about "marginal note". So, I would readily
move it to the Insert->Note sub-menu. At least, it will be 1 less entry in
the "crowded" Insert menu.


I think margin/foot note should be rather coupled together...


I also noticed that the [Insert]->[LyX Note] function is called merely
"Insert Note" in the toolbar tooltip. Should that be changed to "Insert LyX
Note" as well ?


As you wish ;)


LyX Note is a bad name I think. "Sticky note?" "Yellow note?" "Note?"

JMarc

Re: About LyX menus & usability.

[Jürgen Spitzmüller]

2012/10/17 Pavel Sanda:
> Tommaso Cucinotta wrote:
>> However, nobody seems to care about "marginal note". So, I would readily
>> move it to the Insert->Note sub-menu. At least, it will be 1 less entry in
>> the "crowded" Insert menu.
>
> I think margin/foot note should be rather coupled together...

Agreed. Marginal notes and footnotes are conceptually different to the
LyX notes, despite the similar name. LyX notes are rather editiorial
tools (adressed at the author/editor; except for "greyed out maybe,
which is a problematic case in itself). Footnotes, endnotes and
marginal notes are part of the document proper. Since they are so
important in scientific writing, moving them to a second level would
be a bad sign for a mainly "scientific" writing application.

For my lectures, I use marginal notes quite a lot, and I would be
quite annoyed if they wouldn't be easily reachable anymore (via
Alt+E+R in my German l7n currently).

Jürgen

Re: About LyX menus & usability.

[Jean-Marc Lasgouttes]

Le 17/10/2012 12:26, Jürgen Spitzmüller a écrit :

Agreed. Marginal notes and footnotes are conceptually different to the
LyX notes, despite the similar name. LyX notes are rather editiorial
tools (adressed at the author/editor; except for "greyed out maybe,
which is a problematic case in itself). Footnotes, endnotes and
marginal notes are part of the document proper. Since they are so
important in scientific writing, moving them to a second level would
be a bad sign for a mainly "scientific" writing application.


+1

JMarc

Re: Qt issue? (Re: #8374: missing/bad display of dots and cdots)

[Richard Heck]

On 10/17/2012 04:11 AM, Pavel Sanda wrote:

LyX Ticket Tracker wrote:

#8374: missing/bad display of dots and cdots
+--
  Reporter:  MarkBravington  |   Owner:  poenitz
  Type:  defect  |  Status:  new
  Priority:  normal  |   Milestone:
Component:  mathed  | Version:  2.0.4
  Severity:  normal  |  Resolution:
  Keywords:  |
+--

Is there anyone around who can see rendering of three dots instead of two dots 
when typing \cdots in mathed? The code looks correct and unchanged compared to 
older versions where it worked.

Two dots here. I noticed this recently. Qt is 4.8.2.

rh

Re: Qt issue? (Re: #8374: missing/bad display of dots and cdots)

[Jürgen Spitzmüller]

2012/10/17 Richard Heck:
>> Is there anyone around who can see rendering of three dots instead of two
>> dots when typing \cdots in mathed? The code looks correct and unchanged
>> compared to older versions where it worked.
>
> Two dots here. I noticed this recently. Qt is 4.8.2.

I get three, both for \dots and \cdots. Qt 4.8.2 as well.

Jürgen

Re: Qt issue? (Re: #8374: missing/bad display of dots and cdots)

[Jürgen Spitzmüller]

2012/10/17 Jürgen Spitzmüller :
> I get three, both for \dots and \cdots. Qt 4.8.2 as well.

However, scaling matters! I have 200 dpi. If I scale down, I get two
dots at ~140 dpi and one dot at ~100 dpi. At some scale rates (such as
150), the dots even disappear completely.

Jürgen

Re: Re: Qt issue? (Re: #8374: missing/bad display of dots and cdots)

[Kornel Benko]

Am Mittwoch, 17. Oktober 2012 um 16:37:27, schrieb Jürgen Spitzmüller 

> 2012/10/17 Richard Heck:
> >> Is there anyone around who can see rendering of three dots instead of two
> >> dots when typing \cdots in mathed? The code looks correct and unchanged
> >> compared to older versions where it worked.
> >
> > Two dots here. I noticed this recently. Qt is 4.8.2.
> 
> I get three, both for \dots and \cdots. Qt 4.8.2 as well.
> 
> Jürgen

Same here, three both, Qt 4.8.2

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: About LyX menus & usability.

[Jean-Marc Lasgouttes]

Le 15/10/12 22:41, Andrew Parsloe a écrit :

Anyone who can drop "pleonastic" into a sentence hardly needs a native
English speaker.


Well I am able to check in a dictionary that the French word 
"pléonastique" actually translates to English (it looks like it comes 
from English actually). But of course looking like somebody who casually 
drops "pleonastic" in a sentence is an art :)


But knowing which one of pane or panel is more suited to UI is more 
delicate.


JMarc

Re: About USE_META_KEYBINDING (Stephan?)

[Jean-Marc Lasgouttes]

Le 17/10/12 07:41, Stephan Witt a écrit :

Why not just define USE_META_KEYBINDING in configure for the mac build?


Yes, this can be done.

Other options are
1) to remove the USE_META_KEYBINDING macro
2) to handle Alt and Meta separately on all platforms


This is what I though afterwards. Is the problem that all M- bindings 
should become A-? It is a lesser problem now that we hav prefs2prefs 
which can update bind files.


JMarc

Re: About LyX menus & usability.

[Tommaso Cucinotta]

On 17/10/12 11:26, Jürgen Spitzmüller wrote:

Marginal notes and footnotes are conceptually different to the
LyX notes, despite the similar name. LyX notes are rather editiorial
tools (adressed at the author/editor; except for "greyed out maybe,
which is a problematic case in itself). Footnotes, endnotes and
marginal notes are part of the document proper. Since they are so
important in scientific writing, moving them to a second level would
be a bad sign for a mainly "scientific" writing application.

For my lectures, I use marginal notes quite a lot, and I would be
quite annoyed if they wouldn't be easily reachable anymore (via
Alt+E+R in my German l7n currently).


I see your point. I'm just trying to think from a new user perspective:

-) I need to insert a footnote
-) so I go straight to Insert-> menu,
-) scroll it down, find the Note-> sub-menu,
-) cannot see any "footnote"
-) conclusion: "this tool doesn't even support footnotes :-)!"
-) sudo apt-get purge LyX :-(...

exacerbating the last step/conclusions of course, it's just that we all 
probably know very well how to customize the UI, etc (and surely we 
all agree that what LyX probably lacks is a "Tools->Customize menus..." 
tool for re-arranging menus). The experienced user knows where things 
are, he's used to that.
A UI is effective when it allows new users to find stuff intuitively and 
quickly, isn't it ?


One last thing: how does one add an "end note" in LyX ?

Bye,

T.

Re: About LyX menus & usability.

[Tommaso Cucinotta]

On 09/10/12 14:44, Charles de Miramon wrote:

Like Pavel, I find the Insert menu too long. Maybe, everything that relates
to the life cycle of the document (annotations, branches) could go into
'Document'


Do you mean: moving "Insert->Branch" to document ? AFAIU, it's really a 
local edit, so it should stay in Insert.


What about "Version Control" operations ? They probably affect the whole 
document, so move them to Document ? However, it's quite common to find 
that stuff under "File".


What about "File->New Window" / Close Window ? These 2 just seem to me 
they belong to the View menu ?


And, conceputally speaking, perhaps Insert->Graphics... should be 
grouped with Insert->File->... sub-menu (think of 
Insert->File->ExternalMaterial). Again, inserting figures is very very 
common, and I guess there's a nice button readily available on the 
toolbar. If you're about to complain about using keyboard to reach the 
menu entry without using the mouse, I can anticipate that Ctrl+G, on my 
Ubuntu, produces a "telephone" character -- why ? why doesn't it 
activate Insert->Graphics ?


Of course, everyone opinion is very welcome. UI is so subjective

T.

Re: About LyX menus & usability.

[Jean-Marc Lasgouttes]

Le 18/10/12 00:30, Tommaso Cucinotta a écrit :

Do you mean: moving "Insert->Branch" to document ? AFAIU, it's really a
local edit, so it should stay in Insert.


Yes.


What about "Version Control" operations ? They probably affect the whole
document, so move them to Document ? However, it's quite common to find
that stuff under "File".

What about "File->New Window" / Close Window ? These 2 just seem to me
they belong to the View menu ?


Or create a Window(s) menu? Other programs tend to use that.


If you're about to complain about using keyboard to reach the
menu entry without using the mouse, I can anticipate that Ctrl+G, on my
Ubuntu, produces a "telephone" character -- why ? why doesn't it
activate Insert->Graphics ?


This could be added indeed.

JMarc

Re: About LyX menus & usability.

[Tommaso Cucinotta]

On 17/10/12 23:19, Tommaso Cucinotta wrote:

On 17/10/12 11:26, Jürgen Spitzmüller wrote:

For my lectures, I use marginal notes quite a lot, and I would be
quite annoyed if they wouldn't be easily reachable anymore (via
Alt+E+R in my German l7n currently).


Further alternative/proposal: what about a single menu entry 
"Insert->Note...", popping up a dialog, with a radio-box allowing to 
choose the type of note (and I can easily imagine a text/label right on 
its right explaining what these different notes are), where "footnote" 
would be automatically selected (so just type Enter and you're done with 
that -- most common type of note I guess), then "marginal note" could be 
the 2nd choice (so, [Down][Enter] and you're down), and so on... ?


I'm just realizing there's already such a dialog: context-menu on LyX 
note, for example, then Settings... So, what's really bad in making the 
UI for all of these notes all the same ? Want a note ? Just insert a 
note, then you get immediately the dialog, you pick your choice (and see 
these notes shortly explained if you're newbie), then click [Ok] button, 
or [Enter]. You could even have a preference voice "\default_note_type" 
with possible types "ask" (dialog), "LyX", "footnote", "marginal", ... 
(you got the point).


Comments welcome.

T.

Re: $$e not set on import --> import of .Rnw (knitr) fails

[Jean-Marc Lasgouttes]

Le 17/10/12 06:09, Scott Kostyshak a écrit :

I have this problem on master and 2.0.x.

An empty $$e variable is being passed to the converter script on
import because the document is not open yet:
command = subst(command, token_encoding, buffer ?
buffer->params().encoding().iconvName() : string());

Should $$e be set to the default encoding of a new document?

Or is this something that the converter script should deal with?

To reproduce:
1. Open examples/knitr.lyx
2. Export to Rnw (knitr)
3. Import the Rnw (knitr) file

I get an error after (3) because lyxknitr.R is expecting a non-empty
$$e argument.


Stupid question; where is importation of knitr files defined in converters?

JMarc

Re: About LyX menus & usability.

[Jean-Marc Lasgouttes]

Le 18/10/12 00:40, Tommaso Cucinotta a écrit :

On 17/10/12 23:19, Tommaso Cucinotta wrote:

On 17/10/12 11:26, Jürgen Spitzmüller wrote:

For my lectures, I use marginal notes quite a lot, and I would be
quite annoyed if they wouldn't be easily reachable anymore (via
Alt+E+R in my German l7n currently).


Further alternative/proposal: what about a single menu entry
"Insert->Note...", popping up a dialog, with a radio-box allowing to
choose the type of note (and I can easily imagine a text/label right on
its right explaining what these different notes are), where "footnote"
would be automatically selected (so just type Enter and you're done with
that -- most common type of note I guess), then "marginal note" could be
the 2nd choice (so, [Down][Enter] and you're down), and so on... ?

I'm just realizing there's already such a dialog: context-menu on LyX
note, for example, then Settings... So, what's really bad in making the
UI for all of these notes all the same ? Want a note ? Just insert a
note, then you get immediately the dialog, you pick your choice (and see
these notes shortly explained if you're newbie), then click [Ok] button,
or [Enter]. You could even have a preference voice "\default_note_type"
with possible types "ask" (dialog), "LyX", "footnote", "marginal", ...
(you got the point).


Yes, but the point is that there is note and note. I agree that our 
current UI is not very good at separating the two (markup vs author 
annotation), but it is not a reason for making this worse.


In some way, LyX Note could belong somewhere with change tracking, as an 
authoring tool of some sort. But I do not have anything to propose.

It could also be a special branch which is (always?) off.

JMarc

Re: Press about LyX

[Jerry]

Who among the LyX developers has the power to edit the press page, 
http://www.lyx.org/PressAboutLyX?
Daniel has written an article about LyX for the HowToAnswer web site and would 
like to get it linked from the LyX press page. Surely this benefits the LyX 
community as well.

Jerry


On Oct 16, 2012, at 6:01 PM, Jerry wrote:

> Hi Daniel,
> 
> Thanks for this nice article. May I make a suggestion? I think you should 
> show at least one example of rendered LyX output so that the reader 
> understands better that what you see is not what is shown on the LyX screen, 
> but much better and better than typical Word output.
> 
> Jerry
> (not a developer)
> 
> On Oct 16, 2012, at 6:10 AM, HowToAnswer wrote:
> 
>> Hi,
>> 
>> I recently finished my article about LyX, here it is :
>> 
>> http://www.howtoanswer.com/a-quick-review-of-lyx--9.html
>> 
>> According to this page, I should notify someone from LyX.
>> 
>> http://www.lyx.org/PressAboutLyX
>> 
>> How can I get in touch with someone from LyX community
>> and (if possible) get listed there?
>> 
>> Regards,
>> Daniel
> 

Re: $$e not set on import --> import of .Rnw (knitr) fails

[Scott Kostyshak]

On Wed, Oct 17, 2012 at 6:52 PM, Jean-Marc Lasgouttes
 wrote:
> Le 17/10/12 06:09, Scott Kostyshak a écrit :
>
>> I have this problem on master and 2.0.x.
>>
>> An empty $$e variable is being passed to the converter script on
>> import because the document is not open yet:
>> command = subst(command, token_encoding, buffer ?
>> buffer->params().encoding().iconvName() : string());
>>
>> Should $$e be set to the default encoding of a new document?
>>
>> Or is this something that the converter script should deal with?
>>
>> To reproduce:
>> 1. Open examples/knitr.lyx
>> 2. Export to Rnw (knitr)
>> 3. Import the Rnw (knitr) file
>>
>> I get an error after (3) because lyxknitr.R is expecting a non-empty
>> $$e argument.
>
>
> Stupid question; where is importation of knitr files defined in converters?

Rnw (knitr) -> latex (plain)
The converter is currently:
Rscript --verbose --no-save --no-restore $$s/scripts/lyxknitr.R $$p$$i
$$p$$o $$e $$r
When I change this to the following, import works:
Rscript --verbose --no-save --no-restore $$s/scripts/lyxknitr.R $$p$$i
$$p$$o ISO-8859-15 $$r

Scott

Re: Manuals contain outdated break-paragraph-keep-layout

[Uwe Stöhr]

Am 29.09.2012 18:22, schrieb Pavel Sanda:


break-paragraph-keep-layout is LFUN outdated for a long time,
we still have it in these manuals:

lib/doc/de/UserGuide.lyx
lib/doc/eu/Customization.lyx
lib/doc/eu/UserGuide.lyx
lib/doc/sk/UserGuide.lyx


Thanks for the hint. I have now removed the references to this deprecated function and also updated 
the description to reflect the current behaviour in lists.


regards Uwe

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Wed, Oct 17, 2012 at 4:15 AM, Pavel Sanda  wrote:
> Scott Kostyshak wrote:
>> OK thanks for the tips. I'm guessing it's OK to update the format in
>> trunk when changing the manuals?
>
> For additional manual it's OK. IIRC Uwe wanted the manuals under his
> maintenance to remain in 2.0.x for easy synchronization.
>
>> Attached is a patch to update the Additional manual. Is it OK?
>
> Yes. Feel free to push similar paragraph to branch.

OK, it's in trunk and branch.

Thanks,

Scott

Re: About LyX menus & usability.

[Andrew Parsloe]

On 18/10/2012 11:15 a.m., Jean-Marc Lasgouttes wrote:

Le 15/10/12 22:41, Andrew Parsloe a écrit :

Anyone who can drop "pleonastic" into a sentence hardly needs a native
English speaker.


Well I am able to check in a dictionary that the French word
"pléonastique" actually translates to English (it looks like it comes
from English actually). But of course looking like somebody who casually
drops "pleonastic" in a sentence is an art :)

But knowing which one of pane or panel is more suited to UI is more
delicate.

JMarc

I should have added in relation to pane/panel, that windows have panes, 
doors have panels -- which encourages flights of fancy: instead of a 
windowing system, a dooring system, where one has panels with door knobs 
and keys and locks to be opened with appropriate mouse drags and clicks, 
and instead of drop-down menus, little doors that open ...


Andrew

Re: About LyX menus & usability.

[Liviu Andronic]

On Thu, Oct 18, 2012 at 12:15 AM, Jean-Marc Lasgouttes
 wrote:
> But knowing which one of pane or panel is more suited to UI is more
> delicate.
>
I'm no native English speaker either, but from my experience with FOSS
programs the Source and Messages thingies that LyX has are 'panes'.

However the Outline thingy looks more like a 'panel' to me; at least
this is how Opera and Midori call a similar artefact that can be
popped up on the left hand side. But Evince has another such artefact
and calls it 'Side pane'. So this paragraph really is useless.

Liviu

Re: About LyX menus & usability.

[Jürgen Spitzmüller]

2012/10/18 Jean-Marc Lasgouttes :
> Yes, but the point is that there is note and note. I agree that our current
> UI is not very good at separating the two (markup vs author annotation), but
> it is not a reason for making this worse.

I wonder if the term "Annotation" for LyX Notes and comments would be
better. I think less people would associate that with footnotes and
marginal notes.

How are these things called in Word Processors and PDF Readers in English UIs?

BTW, in the German translation, notes are (correctly) translated as
"Notiz". This already disambiguates the phenomenon. Nobody would
subsume footnotes under "Notiz" (but rather under "Anmerkungen"). This
also means that German users would be completely lost if footnotes and
margin notes would indeed be added to the "Notes"/"Notiz" submenu.

Jürgen