Re: Question on whitespace at the end of raw TeX - inserts

2009-01-15 Thread Dieter Jurzitza
Dear Helge,
thank you for your reply. There were several of them - and I came to the end 
that I - to some extend - took it too simple. My personal wrap up is the fact 
that the current TeX-inserts in LyX are not encapsulated - i. e. they reach 
further than the closing insert "bracket".

So, maybe there would be an option to define encapsulated and non encapsulated 
TeX-inserts. But even this increases the complexity as you'd have to cope 
with two different "insert" styles.

Therefore I - sort of accepted, though missing an option to explain why things 
are as they are.

Take care





Dieter



-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---Am Donnerstag, 15. 
Januar 2009 15:31:10 schrieb Helge Hafting:
***
> Dieter Jurzitza wrote:
> Usually, yes. Your case is the normal one. But there are other cases,
> and auto-adding anything will make the unusual cases impossible. And the
> whole point of ERT is to support unusual stuff. Anything normal ought to
> be supported without ERT - someday.
***


Re: Question on section - properties in the menu bar

2009-01-02 Thread Dieter Jurzitza
Hi Vincent,
this solution is perfectly fine with me - would you kindly consider to include 
my debugging - extension to GuiApplication.cpp as well? 

I never ever worked on a public source repository - and basically I think that 
I would not come up with too many contributions so some other nice person 
(thinking of you :-))) should do the job in my place?

Thank you in advance anyway,
take care




Dieter

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---Am Freitag, 2. 
Januar 2009 13:55:14 schrieben Sie:
*
> I did this in http://www.lyx.org/trac/changeset/27977. Now, the icons
> should be named:
*


Patch for the German localization file

2009-01-02 Thread Dieter Jurzitza
Dear listmembers,
attached please find a patch for de.po including "Blocksatz" in the translated 
sequences.
Take care



Dieter Jurzitza

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---
--- po/de.po.original	2008-12-13 09:56:20.0 +0100
+++ po/de.po	2009-01-02 10:43:45.0 +0100
@@ -11504,6 +11504,10 @@
 msgid "Unset all lines"
 msgstr "Alle Linien entfernen"
 
+#: lib/ui/stdtoolbars.inc:128
+msgid "Align justified"
+msgstr "Blocksatz"
+
 #: lib/ui/stdtoolbars.inc:129
 msgid "Align left"
 msgstr "Linksbündig ausrichten"


Re: Question on section - properties in the menu bar

2009-01-01 Thread Dieter Jurzitza
Hi Vincent,
I wouldn't consider "/" being a good idea when it comes to file access, as 
is "\" not a good idea.

If I was asked I'd rather suggest to use something like a doubled underscore, 
say "__" as a replacement for "\". "__" is harmless in any regard, escaping 
is not complicated.


As an alternative I could imagine to replace "\" by string "bcksl_" or 
something alike.

I'd avoid using either "/" or "\" - but these are just my 2 cents here ...

Take care




Dieter Jurzitza

P.S. I'd never ever thought that I'd rise such a discussion starting from the 
menu bar question :-)

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---Am Freitag, 2. 
Januar 2009 01:00:59 schrieb Vincent van Ravesteijn:

> Shouldn't we then implement something to translate "\" into "slash" when




Re: Question on section - properties in the menu bar

2009-01-01 Thread Dieter Jurzitza
Dear Andre,
thanks for the pointer, I see, I see, I forgot to apply the "stderr" in 
fprintf ...
I know, there are lots of people around having higher programming capabilities 
than I do  ;-), but anyway, one should not mix up C and C++, so, it 
wasn't that bad to modify LYXERR output instead 
Take care




Dieter Jurzitza

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---Am Donnerstag, 1. 
Januar 2009 22:37:14 schrieb Andre Poenitz:
> On Thu, Jan 01, 2009 at 10:03:12PM +0100, Dieter Jurzitza wrote:
*


Re: Question on section - properties in the menu bar

2009-01-01 Thread Dieter Jurzitza
Dear listmembers,
well, obviously my C-programming capabilities were sufficient, though. My 
first attempt of using "fprintf("%s\n", name1); ended with an "invalid 
machinecode" message - but patching the debugging-cout messagestring resulted 
in success.

So, at least for linux I can confirm that "\" in a file name is acceptable 
(horray, I'm not on M$) and the expected filename was

  "paragraph-params_\align_block.png"

the other ones have to be adapted in accordance to this. Maybe it is denoted 
somewhere that the " " between "\align" and "block" should be replaced by an 
underscore, but I did not find and this is hard to achieve by simply 
guessing.

So, to whom it might concern: I attach the png-files required for the commands 
I wanted to this email as well as the required patch for the ui file - use it 
or discard it.

To the developers: it would be _very_ nice if you could patch the debug output 
message in such a way that the names of the missing files get printed as 
well - this would be a way of helping people to help themselves. See patch 
attached - just my suggestion, this would really help.

Thanks again to everybody!

Takce care



Dieter Jurzitza

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---
<><><><>--- src/frontends/qt4/GuiApplication.cpp.original	2008-11-29 15:16:00.0 +0100
+++ src/frontends/qt4/GuiApplication.cpp	2009-01-01 21:56:46.0 +0100
@@ -342,7 +342,11 @@
 	if (res.exists(name2))
 		return path + name2;
 
-	LYXERR(Debug::GUI, "Cannot find icon for command \""
+	LYXERR(Debug::GUI, "Cannot find icon with filename "
+			   << "\"" << name1 << "\""
+			   << " or filename "
+			   << "\"" << name2 << "\"" 
+			   << " for command "
 			   << lyxaction.getActionName(f.action)
 			   << '(' << to_utf8(f.argument()) << ")\"");
 
--- stdtoolbars.inc.original	2008-12-20 20:01:06.0 +0100
+++ stdtoolbars.inc	2009-01-01 21:37:59.0 +0100
@@ -110,6 +110,11 @@
 		Item "Text style" "dialog-show character"
 		Item "Paragraph settings" "layout-paragraph"
 		Item "Thesaurus" "thesaurus-entry"
+Separator
+Item "Align justified" "paragraph-params \align block"
+Item "Align left" "paragraph-params \align left"
+Item "Align center" "paragraph-params \align center"
+Item "Align right" "paragraph-params \align right"
 	End
 	
 	Toolbar "table" "Table"


Re: Question on section - properties in the menu bar

2009-01-01 Thread Dieter Jurzitza
Dear listmembers,
dear Vincent,
dear Steve,
well, I can see, christmas just passed by, so I am not t sad about Vincent 
for not having the red robe and the beard.
But many thanks to Vincent, this really did the trick!

And, Steve, you do not have to make me a TeXnician - I readily am (since 
roughly 18 years). However, I want to give you the example where I keep _not_ 
using a special environment and do _not_ want to write an extra TeX style in 
order to achieve my task:

When including figures in reports, I mostly (but not always) put them 
centered, in contrast, the remainder of the text remains aligned justified. 

And I am sure that I could potentially write a specific environment doing 
this, use "myfigure" readily containing the \begin{center}/\end{center} 
sequence, but I don't.

I hardly cope with 300 page documents, I rather have between 2 and 30 pages. 
And there is no problem for me with parsing optically whether all figures are 
justified as I want them to be - I'll have to do this anyway because the size 
of the figure and their positions should fit to the text around it, and no 
LaTeX in the world will bear the burden for me to judge whether or not 
figuresize and remaining text go together well - from a visual standpoint.

By the way, there are several points like this we discuss on our TeX-round 
table once a month. Whenever I rise the point and say that float.sty with the 
capability of using "H" for figure placement can be very useful I may end up 
in lenghty discussions. I am on the pragmatic side, every other time 
prefering simplicity in approach to programming beauty - but not everybody 
shares this point of view :-

But thank you _very_ much for the huge amount of time you've spent for your 
answer! 

Best regards,
thanks again




Dieter Jurzitza


-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---Am Donnerstag, 1. 
Januar 2009 16:40:49 schrieb Vincent van Ravesteijn:
***
> I don't have a "red robe or a long white beard", so if you still want to
> have the four (you need justified too) items in a toolbar, you can try
***


Re: Question on section - properties in the menu bar

2009-01-01 Thread Dieter Jurzitza
Dear listmembers,
in the meantime I created some icons for my purpose and have been putting them 
in the  directory /usr/share/lyx/images.

From the stdtoolbars.inc file I know (theoretically) that the naming 
convention for the files ought to be

_.png 

following this strategy based on i.e.
"Align left" "paragraph-params \align left"

I would follow that  is "paragraph-params" and  is "\align 
left".

So the filename ought to be

"paragraph-params_\align left.png"

which I can create. However, the debug mode (I tried -dbg 8 and "full" dbg, 
what is nonsense in this case) tells me:

GuiApplication.cpp(347): Cannot find icon for command "paragraph-params(\align 
left)"

but it unfortunately does not tell me the name of the game i. e. the actual 
filename it is heading for. I have been playing around with the names, 
modifiying to many versions, however, the only thing that actually works is

paragraph_params.png

but that would consequently assign the very same icon to all the four  
variants of the command, because it references the action only but not the 
parameter, what is not what I would require. My c++ knowledge is not 
sufficient to parse the source-code in this regard, so any help for me again? 
IMHO it would be a "help to help yourself" if the debug message would be 
clearer and add the name of the game to the output-message, too.

Well, and re-reading Vincent's email shows clearly that as "\" is not allowed 
in a filename my concept cannot work in this way.

Thank you very much,
take care




Dieter Jurzitza

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---Am Donnerstag, 1. 
Januar 2009 16:40:49 schrieb Vincent van Ravesteijn:
> > Well, lazy me, what I would like to see are three little symbols for
> > flush-right, flush-left or center on the top-level menu bar that help me
> > avoid diving into a submenu in order to achieve this.
>
> I don't have a "red robe or a long white beard", so if you still want to
> have the four (you need justified too) items in a toolbar, you can try
> the following:
>
> Add to Resources\ui\stdtoolbars.inc the following lines (after Item
> "Thesaurus" "thesaurus-entry"):
>
> Separator
> Item "Align justified" "paragraph-params \align block"
> Item "Align left" "paragraph-params \align left"
> Item "Align center" "paragraph-params \align center"
> Item "Align right" "paragraph-params \align right"
>
> One problem: I don't know how to define the icons for the functions (the
> \ is not allowed in a filename). It works though.
>
> Vincent




Re: Question on section - properties in the menu bar

2009-01-01 Thread Dieter Jurzitza
Dear Steve,
dear listmembers,
your answer tells me that I haven't been precise enough. Imagine you have a 
section in your document you want to be centered rather than (i.e.) 
flushleft. To achieve this in LyX, you have to mark the section and then 
klick on the section menu, from where you can choose the appropriate 
orientation of the text.

Well, lazy me, what I would like to see are three little symbols for 
flush-right, flush-left or center on the top-level menu bar that help me 
avoid diving into a submenu in order to achieve this.

Such an option is very common in other text processing systems and I must 
admit that I like it because I need it every other time. So my question was 
whether some guy shares my kind of laziness and probably readily did 
something similar so I could just copy  :-)

Thanks again,
take care





Dieter Jurzitza

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---Am Mittwoch, 31. 
Dezember 2008 19:03:55 schrieb Steve Litt:
*
> Dieter -- did you mean making the same mod to every section in the book, or
> on a case by case basis?
*


Question on section - properties in the menu bar

2008-12-31 Thread Dieter Jurzitza
Dear listmembers,
from other text processing systems (b ) I am acustomed to the 
possibility to directly access the section attributes (centered, right 
adjusted, left adjusted) via small icons in the menu bar.
I know this is doable in lyx for sure - did someone readily do this and could 
possibily provide the corresponding modifications for 
the /usr/share/lyx/ui/* - files?
Thank you very much,
wish you all a happy new year,
take care



Dieter Jurzitza

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---


Re: Problem when i create from template

2008-12-28 Thread Dieter Jurzitza
Dear Tony,
this message sounds like a partly installed TeX system on your box. It is only 
partly related to lyx - lyx is missing TeX files it needs for proper 
operation.
So you might try to do a full install of texlive (don't know about ubuntu, but 
you  shoule be able to get something from i. e. www.dante.de for M$) and the 
issue is hopefully gone.
Hope this helps,
take care



Dieter

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---Am Sonntag, 28. 
Dezember 2008 12:45:52 schrieb Groupme:
> Hi,
>
> I have installed Lyx 1.6 on both WinXP and Ubuntu 8.10.
>



Re: Question on whitespace at the end of raw TeX - inserts

2008-12-23 Thread Dieter Jurzitza
Dear David,
if I get you right you suggest protecting the first whitespace following ERT - 
if there is one - the point is that the developers say they do not want to 
cope with side effects from ERT as ERT is a "do that if you _really_ know 
what you do! And expect side effects on the document!"

The question is not how the whitespace could be protected. The point is 
whether it should be protected and whether this would impact other things - 
like backward compatibility.

If that's the status then things are as they are - the actual implementation 
of a solution for the issue is a minor problem in this regard.

ERT as is today is not encapsulated. If it was it would be easy to protect 
everything because you could have "brackets" around the ERT (how they'd ever 
look like).

But this is not the intention as sometimes there are good reasons to allow an 
ERT entry to impact content that follows.

Thanks for looking into this but the question is a more basic one and the 
answers were far from an actual implementation issue, the latter not being 
the problem here.

Take care,



Dieter

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---Am Dienstag, 23. 
Dezember 2008 17:54:41 schrieb dcmert...@gmail.com:
> Quick question: why doesn't LyX do this?
>
> abcdef ghi
> -to tex-
> abcdef\ ghi
>
> I totally agree that you shouldn't mess with ert; that's the point of
*


Re: Question on whitespace at the end of raw TeX - inserts

2008-12-22 Thread Dieter Jurzitza
Hi folks,
first of all: thank you for all your replies. And yes, after hearing what you 
came up with I think ERT should remain ERT and inserting an automatic blank 
_within_ the ERT is not a good idea.

But wait: what is LyX saying about itself, WYSIWYM? Hey, if I put a whitespace 
after the end of an ERT you tell me we see it but we won't protect it because 
you put it there but because you've been working with an ERT before we are 
sure you did not mean to see a whitespace there ... 

sorry. This is nothing related to "other text processing systems". This is 
related to "I would expect to see what I mean".

I can remember quite a while ago when I told you that I had my wife working 
with LyX (she still does, by the way ... :-) ) and in the meantime she's much 
happier because if she states now "I want this text to be in this and that 
type of font" it is now. Simply wonderful.

There is one very basic question I am rising here for discussion: is the 
target beauty or understandability? I think all of you spend hours and hours 
(I _really_ appreciate, don't get me wrong) in making LyX to what it is: 
highly usuable, extremely configurable and with a very nice user interface. 

However, I think all we are TeXnicians to some extent, aren't we? And that's 
the measure LyX will be checked against: the "native" user not being that 
familiar with TeX.

According to my understanding he should be protected against the oddities of 
TeX by the help of LyX. Well, I hear you say, the native user will not use 
TeX inserts - maybe - but he might do so. And that's were my point starts. I 
would say that if someone puts whitespace after an ERT, why would he do this? 
I'd say he does this because he want's it to be there.

But these are just my 2 cents ... I do not want to rise a large discussion on 
a probably small item ... maybe you like to rethink, maybe not - thank you 
for all of your work anyway, and have a nice Christmas Eve and Happy New 
Year, I hope you'll find the time to continue your work on LyX!

Take care



Dieter Jurzitza

P.S. and I was ignoring backward compatibility issues - this might be of  
heavier impact ...

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---Am Montag, 22. 
Dezember 2008 18:18:02 schrieb Steve Litt:
> On Monday 22 December 2008 11:58:24 am David Mertens wrote:
**


Question on whitespace at the end of raw TeX - inserts

2008-12-21 Thread Dieter Jurzitza
Dear listmembers,
I stumbled over (and found the hint in the documentation) that you are forced 
to add a whitespace at the end of any raw TeX-insert.

I understand that the TeX - insert is not encapsulated, i. e. it is intended 
to have impact on LyX code that follows.

However I would like to ask why LyX cannot insert Whitespace (i. e. a single 
blank) at the end of a TeX insert and why a blank _following_ a TeX insert is 
not guarded by some means.

Example - (the %-sign stands for start-end of TeX insert within LyX) if you 
say

"The difference between %\TeX% and %\LyX% is bla bla ..."

You will end in _no_ space between "TeX" and "and", you will get

".. between TeXand LyXis bla bla ..."

So a fist point would be to add to the (very good!) manual a hint 
that "closed" TeX inserts such as %\TeX% should in any case be bracketed to 
depict clearly that the following whitespace should be paid attention to. 
Simply adding a blank is not enough. You have to say %{\TeX}% to get the 
following blank in effect.

Therefore I would like to rise two points you may - or may not - share.

1.) put automatically a blank as whitespace at the end of each TeX-insert 
before closing it. 
2.) protect a whitespace follwing a TeX-insert if there is one - assume that 
the user intentionally puts a whitespace there.

Maybe I overlooked something - but for now I cannot see a good reason not to 
do this. I personally think that the results would be closer to what the user 
expects. If I insert a blank after a TeX-insert I (personally) expect it to 
be intentional and it is hard to understand (not being a TeXnician) why it is 
not remaining where I have been putting it to - even worse it is not easy to 
know the rule how to avoid that it is vanishing in the dark.

This is just the outcome from some testing - apart from this I like LyX 1.6 
very much and the option to have several texts open in parallel is simply 
great!

Thank you very much for working on this program,
take care



Dieter Jurzitza

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 <°°__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---