[tex-live] getnonfreefonts

[Paulo Ney de Souza]

On Wed, Apr 13, 2016 at 12:51 PM, Zdenek Wagner <zdenek.wagner at gmail.com>
wrote:

> 2016-04-13 21:34 GMT+02:00 Paulo Ney de Souza <pauloney at gmail.com>:
>
>>
>>
>> If it is in TDS, just put it to your $TEXM-LOCAL and run updmap(-sys)
>>>
>>
>>
>> I can show you a ton of fonts for which that will NOT work! And that you
>> have to disable some Map's and enable others in oredr to make it work.
>>
>
> ... which means that they are not properly packaged.
>

Correct! I agree with you that some of these fonts are not properly
packaged.


>
>>
>> With the additional information on how they are packaged it should be
>> enough. A few subroutines to deal with each class... and the info laid out
>> in a flat DB should be all that is required.
>>
>
> Yes, but the information must be available in a standardized computer
> readable metafile.
>

Yes, of course!



>
>>
>>>
>>> It can be automatic if all fonts are packaged exactly the same way. If
>>> you do not force all font authors to pack the distribution in an exactly
>>> the same way, the script will sooner or later crash.
>>>
>>
>>
>> getnonfreefonts is the counter-example of what you saying above. It
>> install 10 different fonts which are packaged in different ways, and it
>> does it beautifully.
>>
>
> No, getnonfreefonts is a script that can install selected fonts where the
> packages were manually tweaked by Reinhard (or maybe somebody else too).
>

And I am not saying that similar work will not be necessary here.

Paulo Ney



>
>
>
> Zdeněk Wagner
> http://ttsm.icpf.cas.cz/team/wagner.shtml
> http://icebearsoft.euweb.cz
>
>
>
>>
>> Paulo Ney
>>
>>
>>
>>>  Wagner <zdenek.wagner at gmail.com> wrote:
>>>>
>>>>> Saying that something is packaged does not give any useful
>>>>> information. How is it packaged, as zip, rpm, deb, ...? If it is a zip,
>>>>> what is the directory structure inside it? What is the format of the font,
>>>>> is it MF, Type 1, TrueType, OpenType? What is the encoding of the font?
>>>>> Which languages and scripts are supported? If a font is properly packaged,
>>>>> it means that all this information is present in a metafile understandable
>>>>> to an infrastructure that is able to put the files to correct directories
>>>>> and is able to inform the operating system and/or a particular TeX
>>>>> distribution that the font is available. CTAN usually contains archive
>>>>> files, not packages. In order to use them a user has to collect all this
>>>>> information and install the font. There is nothing like super simple font
>>>>> installation unless it is an OpenType font and you can just copy the *.otf
>>>>> to a system directory.
>>>>>
>>>>>
>>>>> Zdeněk Wagner
>>>>> http://ttsm.icpf.cas.cz/team/wagner.shtml
>>>>> http://icebearsoft.euweb.cz
>>>>>
>>>>> 2016-04-13 2:41 GMT+02:00 Paulo Ney de Souza <pauloney at gmail.com>:
>>>>>
>>>>>> We are talking about fonts that have already been packaged - this is
>>>>>> about installation and not packaging for TeX.
>>>>>>
>>>>>> Paulo Ney
>>>>>>
>>>>>> On Tue, Apr 12, 2016 at 5:38 PM, Norbert Preining <preining at logic.at>
>>>>>> wrote:
>>>>>>
>>>>>>> > elsewhere) which are not available on TL. This is vexing because
>>>>>>> the
>>>>>>> > technology to make these installs a single command line like ...
>>>>>>> >
>>>>>>> >     font-install Antiqua
>>>>>>>
>>>>>>>         $ font-install Antiqua
>>>>>>>         bash: font-install: command not found
>>>>>>>
>>>>>>> I don't know what you are talking about that super simple font
>>>>>>> installation, but I can guarantee you - and I have packaged a lot of
>>>>>>> fonts - that font installation cross platform is not trivial.
>>>>>>>
>>>>>>> Norbert
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------
>>>>>>> PREINING, Norbert
>>>>>>> http://www.preining.info
>>>>>>> JAIST, Japan                                 TeX Live & Debian
>>>>>>> Developer
>>>>>>> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C
>>>>>>> DC13
>>>>>>>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/tex-live/attachments/20160413/7b98c610/attachment.html>