From: "Keith J. Schultz" <schultzk@uni-trier.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: unknown library 'loc'
Date: Mon, 13 Jan 2014 16:54:58 +0100 [thread overview]
Message-ID: <6285DFD8-E4A6-4312-A795-EECC3167444A@uni-trier.de> (raw)
In-Reply-To: <52D31C4D.9070106@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2411 bytes --]
Hi Hans,
Suppressing the message of a loc that is not needed would be the cleanest
method.
IMHO, it should not be even causing a warning.
regards
Keith.
Am 12.01.2014 um 23:50 schrieb Hans Hagen <pragma@wxs.nl>:
> On 1/12/2014 11:23 AM, Keith J. Schultz wrote:
>> Hi Hans,
>>
>> Am 07.01.2014 um 00:24 schrieb Hans Hagen <pragma@wxs.nl>:
>>
>>> On 1/3/2014 2:33 PM, H. van der Meer wrote:
>>>> Has someone an idee what causes the unknown library message as in the
>>>> log below? Is it harmful?
>>>>
>>>> fonts > typescripts > unknown library 'loc'
>>>
>>> you can add a file type-loc.mkiv someplace in your local tree with
>>>
>>> % dummy file
>>>
>>> \endinput
>>>
>>> this file can be used for local overrides (just some mkii compatible feature).
>> If this is the case, should not the the "dummy"-file be in the distribution!
>> That way if somebody has local overrides they can modify it if needed,
>> and the rest of have one lees message we need to worry, about?
>
> It depends ... there are some more loc files, like cont-loc.mkiv and we don't ship these either. Normally users would put such files in texmf-local nowadays but in the past that tree has changes positions in texlive (loading order) so we make no assumptions i.e. it can even be in the main base path which in turn means that we need to make sure it doesn't get overwritten. Easier is probably to suppress the message (ugly but doable).
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 4931 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2014-01-13 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 13:33 H. van der Meer
2014-01-05 0:05 ` Hans Hagen
2014-01-06 23:24 ` Hans Hagen
2014-01-12 10:23 ` Keith J. Schultz
2014-01-12 22:50 ` Hans Hagen
2014-01-13 15:54 ` Keith J. Schultz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6285DFD8-E4A6-4312-A795-EECC3167444A@uni-trier.de \
--to=schultzk@uni-trier.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).