I just stumbled over sec. 5.1 of the customization manual which describes how to install
LaTeX-package manually.
This section seems quite outdated:
- it contains a lot of special commands and settings that are most probably not
needed
- the important point how to unpack a LaTeX-package was miss
Am 25.09.2010 22:08, schrieb Richard Heck:
Perhaps the warning could be (a) rephrased to make it sound less dire and (b) given
a "don't show
again" box.
The attached patch does this and also distinguishes between LaTeX and DVI. This is in my opinion
important.
The method isValidLaTeXFileName
In some classes fancyhdr is not the solution. However we can expect
the layouts to provide the right environments already. In this case
they can be made incompatible with the
new module, can't they?
fancyhdr can be used with all document classes. See for example my example file that uses
KOMA-s
On 09/25/2010 12:54 PM, Uwe Stöhr wrote:
> Removing a warning just because it works for you is not an option
IMHO. Before
> you remove it, it is up to you to prove that it really is obsolete
in all
> cases.
That's why I asked you do test this with your TeXLive installation.
If we identify the
> Removing a warning just because it works for you is not an option IMHO. Before
> you remove it, it is up to you to prove that it really is obsolete in all
> cases.
That's why I asked you do test this with your TeXLive installation.
If we identify the problem of beeing only a problem in xdvi, th
Uwe Stöhr wrote:
> I cannot accept that we show a warning that is invalid. On Windows this
> warning is definitively invalid - TeXLive, MiKTeX and their DVI viewers
> can handle brackets.
As I said, a warning that states that something _might_ go wrong is not
invalid if it doesn't go wrong in ce
> I do not understand this argument. We do not "forbid" this characters in any
> way. We just issue a warning that users might run into problems when using
> these in file names. These warnings are still valid for the mentioned cases.
> So I do not see a reason to ditch the warning.
I cannot acce
Am 25.09.2010 16:51, schrieb Uwe Stöhr:
On Windows only the following characters are not allowed by the OS:
/ \ | > < " : * ?
Sorry, my mistake. This is irrelevant because I was only referring to valid LaTeX filenames and that
is what we are checking in isValidLaTeXFileName.
regards Uwe
Uwe Stöhr wrote:
> We should allow all other characters in isValidLaTeXFileName. If necessary,
> we have to differentiate between Unix systems, MaCOS and Windows.
I do not understand this argument. We do not "forbid" this characters in any
way. We just issue a warning that users might run into p
> Can someone who knows about encodings look at #6223?
Its language is Korean and the encoding set to auto. It therefore uses the encoding
"euc-kr".
regards Uwe
Edwin Leuven wrote:
> jurgen, perhaps you can put this into branch?
>
> http://www.lyx.org/trac/changeset/35492
Could you say a bit more about the problem (I do not see icon size problems)
and the fix?
And while I have you online, there's also a pending question for you here:
http://www.lyx.org
rgheck wrote:
> Author: rgheck
> Date: Fri Sep 24 19:24:25 2010
> New Revision: 35494
> URL: http://www.lyx.org/trac/changeset/35494
>
> Log:
> Fix #6914 for branch.
status.16x, please.
Jürgen
12 matches
Mail list logo
