[Therion] First use of locally compiled Therion: metapost error
Stacho Mudrak
lists at group-s.sk
Tue Feb 21 15:11:05 CET 2017
Hi,
I have finished implementation today, but it was a long term problem. Now
therion should compile without any additional therion.ini modifications. If
it does not find required fonts, it will not use them.
S.
On 21 February 2017 at 15:04, Rodrigo Severo via Therion <therion at speleo.sk>
wrote:
> Hi Stacho,
>
> 2017-02-21 8:48 GMT-03:00 Stacho Mudrak via Therion <therion at speleo.sk>:
>
>> Hello,
>>
>> we have implemented Olly's proposal of tex-fonts-optional. It should work
>> now I believe, because all non standard TeX fonts used are now optional.
>>
>
> I'm not sure I understood. Have you implemented Olly's proposal after
> yesterday afternoon?
>
> I'm asking because I got Therion's code yesterday afternoon and that code
> got me the 768 metapost error that I had to fix by manually inserting the
> *text-fonts* line in /etc/therion.ini. And again, just copying the
> therion.ini would not have solved the issue as it has no uncommented lines
> in it.
>
> May be there should be a new text-fonts-optional line on source's
> therion.ini file. Is that what's missing now?
>
>
> Regards,
>
> Rodrigo
>
>
>
>>
>> S.
>>
>> On 21 February 2017 at 01:31, Rodrigo Severo via Therion <
>> therion at speleo.sk> wrote:
>>
>>> 2017-02-20 21:00 GMT-03:00 Olly Betts <olly at survex.com>:
>>>
>>>> On Mon, Feb 20, 2017 at 08:40:36PM -0300, Rodrigo Severo via Therion
>>>> wrote:
>>>> > To fix it I had to include the following line on */etc/therion.ini*
>>>> >
>>>> > tex-fonts raw cmr10 cmti10 cmbx10 cmss10 cmssi10
>>>> >
>>>> > despite Therion Book stating at page 80 that this is the default
>>>> setting.
>>>> >
>>>> > Should this line be uncommented on the default *therion.ini* file?
>>>>
>>>> Do you have the Ubuntu package of therion installed too?
>>>>
>>>
>>> Yes, I do.
>>>
>>>
>>>> If so, my guess is that /etc/therion.ini is from that package.
>>>
>>>
>>> I bet it is.
>>>
>>>
>>>> Currently
>>>> the Debian (and hence Ubuntu) packages have a couple of patches in this
>>>> area - see the discussion here for details:
>>>>
>>>> https://github.com/therion/therion/pull/31
>>>>
>>>> Assuming I'm right, the quickest fix for your situation is probably to
>>>> copy
>>>> therion.ini from the source tree to /etc.
>>>>
>>>
>>> I just checked the diferences between *therion.ini* from the source
>>> tree and the one at */etc/therion.ini*. There are a few but all on
>>> lines that are commented, so they are irrelevant for this situation.
>>>
>>> The only diference on a non commented line is exactly the line I
>>> included in */etc/therion.ini* that is not present on the *therion.ini* file
>>> available at the source and also wasn't at */etc/therion.ini* until I
>>> included it myself.
>>>
>>> So, no, coping the *therion.ini* available at the source to
>>> */etc/therion.ini* wouldn't fix my issue.
>>>
>>> My issue is exactly the one discussed at the link you sent.
>>> Unfortunatelly that issue isn't solved yet.
>>>
>>> AFAICT, right now new Therion installations from source on Linux won't
>>> work because of error 768.
>>>
>>>
>>> Regards,
>>>
>>> Rodrigo
>>>
>>>
>>>
>>>>
>>>> Cheers,
>>>> Olly
>>>>
>>>
>>>
>>> _______________________________________________
>>> Therion mailing list
>>> Therion at speleo.sk
>>> https://mailman.speleo.sk/listinfo/therion
>>>
>>>
>>
>> _______________________________________________
>> Therion mailing list
>> Therion at speleo.sk
>> https://mailman.speleo.sk/listinfo/therion
>>
>>
>
> _______________________________________________
> Therion mailing list
> Therion at speleo.sk
> https://mailman.speleo.sk/listinfo/therion
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20170221/2856d3d5/attachment.htm>
More information about the Therion
mailing list