ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Problems with Standalone distribution
Date: Wed, 05 Apr 2006 10:51:31 +0200	[thread overview]
Message-ID: <44338513.9070705@wxs.nl> (raw)
In-Reply-To: <44331E2D.9129.31B43F9@wwl.musensturm.de>

wwl@musensturm.de wrote:
> As I said, I work with the standalone distri?
>   
the minimal or the complete windows version (including scite etc)
> And I thought, the binaries are from fptex, right?
>   
sure
> And if both texexec.ini's are removed:
>
> texexec complains: 
>
>   warning: texexec.ini not found, try 'texexec --verbose'
>
> (the same with texexec --verbose)
>   
but that should normally be no problem

>  
>   
>> newtexexec.rb (which will replace texexec.pl) has no ini file but
>> uses 
>> some heuristics to determine what environment it runs in
>>     
>>>  
>>>   
>>>       
>>>> 'texexec --verbose' tries to compile all the files in the aktuel
>>>> path.
>>>>
>>>> but
>>>>
>>>> 'texmfstart texexec.pl --verbose' works ok.
>>>>
>>>> same with
>>>>
>>>> 'texexec --make --all' doesn't work
>>>>
>>>> but 
>>>>
>>>> 'texmfstart texexec.pl --make --all' works!
>>>>     
>>>>         
>> good
>>     
>
> upps?
>
> texexec (without parameters)
>
> compiles cscite.bat! Why?
>   
strange indeed

can you run "texmfstart texexec" and see what happens then
>  
>   
>> on windows: you need to associate the pl suffix to perl
>> on linux you need to make  texexec into a script (suffixless)
>>
>> on both you can best use texmfstart to launch the scripts since
>> that's 
>> upward compatible (and in some respects this call is more clever);
>> if 
>> needef you can create stubs with texmfstart (see manual)
>>     
>
> This works!
>
> But next Problem:
>
> pdfetex can not find pk-fonts.
>
> I have written: 
>
> PKFONTS = .;$TEXMF/fonts/pk//
>
> in 'texmf.cnf'
>
> font-file lies in
>
> texmf-project/fonts/pk/ricoh/local/msl/msl50.pk
>
> what else can I do?
>   
ok, that's another problem (once solved you know a bit about tex and fonts) ... it looks like there is a problem with locating fonts ... what 
font is that: msl50 ? 

(the minimal distribution does not have such a font)  

Hans 


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2006-04-05  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.600.1144137409.2083.ntg-context@ntg.nl>
2006-04-04 23:32 ` wwl
2006-04-05  8:51   ` Hans Hagen [this message]
     [not found] <mailman.571.1143822023.2083.ntg-context@ntg.nl>
2006-03-31 22:06 ` wwl
     [not found] <mailman.569.1143811078.2083.ntg-context@ntg.nl>
2006-03-31 13:38 ` wwl
2006-03-31 14:00   ` Hans Hagen
2006-03-31 12:11 wwl
2006-03-31 12:45 ` Hans Hagen

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=44338513.9070705@wxs.nl \
    --to=pragma@wxs.nl \
    --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).