On 09/26/2010 03:11 PM, Uwe Stöhr wrote:
Am 26.09.2010 16:27, schrieb Richard Heck:
Please have another look at 5.1. I've added a note about something
that should be fixed.
Many thanks!
I revised this section and added the method of installing only for
current user on Windows.
But there are 2 problems:
- you use URL for paths. This is in my opinion a hack because paths
are no URLs. However, this makes the documents uncompilable. The
reason is that Windows paths contain \ characters which is interpreted
by LaTeX as command opening.
Long paths can in general often not be broken at the end of a text
line by LaTeX, because LaTeX doesn't know where to hyphenate them. We
therefore have in any case to take care manually that long paths don't
protrude over the margin. I now used the solution your find for the 2
long Windows paths in sec. 5.1. I hope this is fine with you.
You might know better than I do, but I think URL will work correctly
with *nix paths, since they use the / separator, as in URIs. The only
thing lacking, really, from a proper URI is the scheme, "file://".
Anyway, we can use code for now.
- your are using the style typewriter a lot which often leads to text
protruding over the text margin. I therefore propose to use sans serif
instead. (That's how I do in the UserGuide and the other manuals.)
The code charstyle uses typewriter. I don't see any problems with it
when I compile here. If it causes problems, then we can alter that
charstyle in local layout. I've put the necessary code (commented out) in.
To reply to your questions:
- ~ is commonly used in the Windows world to specify that there is
something before, like a placeholder. So "~:\programs" means that it
could be "C:\programs" or "E:\programs" or whatever.
OK. Very confusing for us *nix folks.
- I corrected my mistake of using a German term in the path. Our
English documentation should use English terms, and the corresponding
translations in the other language versions.
I've added a note saying that this can vary depending upon language,
since users of non-English installs might be reading the English docs
anyway.
Oh and (not just you), everyone, please make use of character styles
in the Customization manual.
Character styles are still not working for me well:
- In the Spanish version of Customization.lyx I added the module
"Logical markup". But then I don't know how to insert one. How is that
done?
Edit>Text Style, and now you should see the options.
- In the French Customization manual I also loaded the logical markup
module and then copied the whole section 5.1 from the English version
to the French version. I then get 3 errors, that "CharStyle:MenuItem"
is undefined. I did the same action for the Spanish manual and there I
don't get errors.
Can you therefore please have a look at sec. 5.1 of the French
Customization.lyx in trunk?
This is defined in local layout (since menu items are only needed in our
own docs). You can just copy the local layout from the English one to
the others.
- I copy a text line including a charstyle from an English manual to
e.g. a German one. Then I highlight the whole text line and set its
language to German. But the charstyle content remains English. One has
to go into the charstyle and do the action there again to change it to
German. This is very annoying and perhaps the reason why our
translators don't use charstyles often.
That would be a bug. Obviously, when we change the language, we should
recurse into charstyles. I have no idea how to do this, or even where
this info is stored. Can you report it on trac?
Richard
