Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
scrreprt error reports.
1,084 views
Skip to first unread message
Sharon Kimble
Jul 31, 2014, 1:25:27 PM7/31/14
to
I am using "\documentclass{scrreprt}" and each time that I generate the
pdf again, I am seeing this in the terminals output -
--8<---------------cut here---------------start------------->8---
Class scrreprt Warning: Usage of deprecated font command `\sl'!
(scrreprt) You should note, that in 1994 font command `\sl' has
(scrreprt) been defined for compatiblitiy to Script 2.0 only.
(scrreprt) Now, after two decades of LaTeX2e and NFSS2, you
(scrreprt) shouldn't use such commands any longer and within
(scrreprt) KOMA-Script usage of `\sl' is definitely deprecated.
(scrreprt) See `fntguide.pdf' for more information about
(scrreprt) recommended font commands.
(scrreprt) Note also, that KOMA-Script will remove the definition
(scrreprt) of `\sl' anytime until release of about version 3.20.
(scrreprt) But for now, KOMA-Script will replace deprecated `\sl'
(scrreprt) by `\normalfont \slshape ' on input line 329.
Class scrreprt Warning: Usage of deprecated font command `\rm'!
(scrreprt) You should note, that in 1994 font command `\rm' has
(scrreprt) been defined for compatiblitiy to Script 2.0 only.
(scrreprt) Now, after two decades of LaTeX2e and NFSS2, you
(scrreprt) shouldn't use such commands any longer and within
(scrreprt) KOMA-Script usage of `\rm' is definitely deprecated.
(scrreprt) See `fntguide.pdf' for more information about
(scrreprt) recommended font commands.
(scrreprt) Note also, that KOMA-Script will remove the definition
(scrreprt) of `\rm' anytime until release of about version 3.20.
(scrreprt) But for now, KOMA-Script will replace deprecated `\rm'
(scrreprt) by `\normalfont \rmfamily ' on input line 329.
--8<---------------cut here---------------end--------------->8---
How can I either get rid of these messages, or stop them entirely
please? The packages come from "Texlive 2014".
Thanks
Sharon.
--
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, fluxbox 1.3.5, emacs 24.3.92.1
Axel Berger
Jul 31, 2014, 1:41:41 PM7/31/14
to
Sharon Kimble wrote:
> How can I either get rid of these messages, or stop them entirely
> please?
The best way is to read and heed them. I also recommend the well known
> How can I either get rid of these messages, or stop them entirely
> please?
l2tabu list of deprecated and wrong commands.
If you insist on persisting in your less than perfect ways, which is
entirely up to you, then a little gentle nagging is what you shall have
to put up with.
Axel
Ulrike Fischer
Jul 31, 2014, 1:56:27 PM7/31/14
to
Am Thu, 31 Jul 2014 18:25:27 +0100 schrieb Sharon Kimble:
> I am using "\documentclass{scrreprt}" and each time that I generate the
> pdf again, I am seeing this in the terminals output -
> I am using "\documentclass{scrreprt}" and each time that I generate the
> pdf again, I am seeing this in the terminals output -
> How can I either get rid of these messages, or stop them entirely
> please?
Depends on how they are triggered: If you are using \rm or \sl in
> please?
your document then simply change them to \rmfamily or \slshape. If
the messages are triggered because some package is using these
commands you will have to identify the package and try to get the
author to change it.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
Sharon Kimble
Jul 31, 2014, 4:04:50 PM7/31/14
to
within the packages that I am using. I am not using \rm or \sl anywhere
at all in my documents, so it must be coming in from some other package
that is interacting with "scrreprt".
With regard to my "less than perfect ways", as you phrase it, I am
largely self-taught and rely on various sites and forums for support and
guidance. I am open to criticism providing that it is constructive, and
not destructive, and any pointers given I am quite willing to follow up
and learn from it or them. But thank you for the pointer to
"l2tabuen.pdf", it looks interesting. Unfortunately the most recent
version of "l2tabu.pdf" in Texlive 2014, is written in german and dated
2011, whereas the english translation is "l2tabuen.pdf" and dated 2007.
Axel Berger
Jul 31, 2014, 6:48:24 PM7/31/14
to
Ulrike Fischer wrote:
> you will have to identify the package
That first. Then try to find out which is used. Most will long be
> you will have to identify the package
updated by now, so there is a good chance the trouble lies with another
old copy in your local texmf tree. The local one is always searched
first and gets priority over the packaged one.
Axel
jon
Jul 31, 2014, 11:54:33 PM7/31/14
to
On Thursday, 31 July 2014 16:04:50 UTC-4, Sharon Kimble wrote:
>
> As far as I know, these reports are generated by some command from
> within the packages that I am using. I am not using \rm or \sl anywhere
> at all in my documents, so it must be coming in from some other package
> that is interacting with "scrreprt".
>
>
> With regard to my "less than perfect ways", as you phrase it, I am
> largely self-taught and rely on various sites and forums for support and
> guidance.
troubleshooting in this case is best done by constructing a "minimal
>
> As far as I know, these reports are generated by some command from
> within the packages that I am using. I am not using \rm or \sl anywhere
> at all in my documents, so it must be coming in from some other package
> that is interacting with "scrreprt".
>
>
> With regard to my "less than perfect ways", as you phrase it, I am
> largely self-taught and rely on various sites and forums for support and
> guidance.
working example"; for more information, see the faq:
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minxampl
(more links at bottom of that page.)
if a package is to blame, it should be pretty easy to find the culprit(s).
cheers,
jon.
Ulrike Fischer
Aug 1, 2014, 3:52:45 AM8/1/14
to
Am Fri, 01 Aug 2014 00:48:24 +0200 schrieb Axel Berger:
> Ulrike Fischer wrote:
>> you will have to identify the package
>
> That first. Then try to find out which is used. Most will long be
> updated by now,
It's probably fancyhdr, and no it hasn't been updated.
> Ulrike Fischer wrote:
>> you will have to identify the package
>
> That first. Then try to find out which is used. Most will long be
> updated by now,
Nicola Talbot
Aug 1, 2014, 5:49:31 AM8/1/14
to
On 31/07/14 18:25, Sharon Kimble wrote:
> (scrreprt) by `\normalfont \rmfamily ' on input line 329.
In this case, the problematic command is on line 329, so have a look at
> (scrreprt) by `\normalfont \rmfamily ' on input line 329.
that line in your document source to see what commands are used in it.
If you have \input or \include you'll need to look at the log file to
see which file is being processed when the warning occurred.
That may help you pinpoint the problem.
Regards
Nicola Talbot
--
Home: http://www.dickimaw-books.com/
Creating a LaTeX Minimal Example:
http://www.dickimaw-books.com/latex/minexample/
Ulrike Fischer
Aug 1, 2014, 6:44:27 AM8/1/14
to
Am Fri, 01 Aug 2014 10:49:31 +0100 schrieb Nicola Talbot:
> On 31/07/14 18:25, Sharon Kimble wrote:
>> (scrreprt) by `\normalfont \rmfamily ' on input line 329.
>
> In this case, the problematic command is on line 329, so have a look at
> that line in your document source to see what commands are used in it.
As the warning is quite probably triggered by fancyhdr this is
> On 31/07/14 18:25, Sharon Kimble wrote:
>> (scrreprt) by `\normalfont \rmfamily ' on input line 329.
>
> In this case, the problematic command is on line 329, so have a look at
> that line in your document source to see what commands are used in it.
probably the line where a page break occurs.
Nicola Talbot
Aug 1, 2014, 7:20:04 AM8/1/14
to
On 01/08/14 11:44, Ulrike Fischer wrote:
> Am Fri, 01 Aug 2014 10:49:31 +0100 schrieb Nicola Talbot:
>
>> On 31/07/14 18:25, Sharon Kimble wrote:
>>> (scrreprt) by `\normalfont \rmfamily ' on input line 329.
>>
>> In this case, the problematic command is on line 329, so have a look at
>> that line in your document source to see what commands are used in it.
>
> As the warning is quite probably triggered by fancyhdr this is
> probably the line where a page break occurs.
>
>
You're right. I didn't think about that, but it may help if it turns out
> Am Fri, 01 Aug 2014 10:49:31 +0100 schrieb Nicola Talbot:
>
>> On 31/07/14 18:25, Sharon Kimble wrote:
>>> (scrreprt) by `\normalfont \rmfamily ' on input line 329.
>>
>> In this case, the problematic command is on line 329, so have a look at
>> that line in your document source to see what commands are used in it.
>
> As the warning is quite probably triggered by fancyhdr this is
> probably the line where a page break occurs.
>
>
there's another loaded package also using the obsolete commands. (I
doubt fancyhdr is the only package still in use that has deprecated code.)
Robin Fairbairns
Aug 3, 2014, 12:10:20 PM8/3/14
to
Nicola Talbot <n.ta...@uea.ac.uk> writes:
> On 01/08/14 11:44, Ulrike Fischer wrote:
>> Am Fri, 01 Aug 2014 10:49:31 +0100 schrieb Nicola Talbot:
>>
>>> On 31/07/14 18:25, Sharon Kimble wrote:
>>>> (scrreprt) by `\normalfont \rmfamily ' on input line 329.
>>>
>>> In this case, the problematic command is on line 329, so have a look at
>>> that line in your document source to see what commands are used in it.
>>
>> As the warning is quite probably triggered by fancyhdr this is
>> probably the line where a page break occurs.
>
> You're right. I didn't think about that, but it may help if it turns
> out there's another loaded package also using the obsolete
> commands. (I doubt fancyhdr is the only package still in use that has
> deprecated code.)
probably not. however, fancyhdr's a pretty commonly-recommended package
> On 01/08/14 11:44, Ulrike Fischer wrote:
>> Am Fri, 01 Aug 2014 10:49:31 +0100 schrieb Nicola Talbot:
>>
>>> On 31/07/14 18:25, Sharon Kimble wrote:
>>>> (scrreprt) by `\normalfont \rmfamily ' on input line 329.
>>>
>>> In this case, the problematic command is on line 329, so have a look at
>>> that line in your document source to see what commands are used in it.
>>
>> As the warning is quite probably triggered by fancyhdr this is
>> probably the line where a page break occurs.
>
> You're right. I didn't think about that, but it may help if it turns
> out there's another loaded package also using the obsolete
> commands. (I doubt fancyhdr is the only package still in use that has
> deprecated code.)
-- istr i say in my faq that it's the only plausible one for the job
... a statement that's probably not true. i've a plausible-looking
address for piet van oostrum (which seems to work), so i'll ask him if
he could do the job, or whether he'd like to depute it to me...
--
Robin Fairbairns, Cambridge
0 new messages