[tex-live] Undocumented change in fmtutil --enablefmt/--disablefmt

[Zdenek Wagner]

For me it's also OK.
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz


2015-06-16 15:25 GMT+02:00 Ken Brown <kbrow1i at gmail.com>:
> Hi Norbert,
>
> On 6/16/2015 9:19 AM, Norbert Preining wrote:
>>
>> Hi Ken,
>>
>> On Tue, 16 Jun 2015, Ken Brown wrote:
>>>
>>> In TL2014, the commands 'fmtutil-sys --enablefmt cont-en' and
>>> 'fmtutil-sys --disablefmt cont-en' would enable/disable both cont-en
>>> formats (one with engine pdftex, the other with engine xetex).
>>
>>
>> Which is not really intuitive ...
>
>
> I agree.
>
>>> fmtutil [WARNING]: More engines given for format cont-en.
>>> fmtutil [WARNING]: Please specify one of the engines: xetex pdftex
>>> fmtutil [WARNING]: No changes done.
>>>
>>> Neither the error message nor the fmtutil help text explains *how*
>>> to specify the engine (by using the syntax "format/engine").  I
>>
>>
>> Is the following output better:
>>         fmtutil [WARNING]: More engines given for format cont-en.
>>         fmtutil [WARNING]: Possible engines: xetex pdftex
>>         fmtutil [WARNING]: Please select one by passing in cont-en/ENGINE
>>         fmtutil [WARNING]: No changes done.
>
>
> Perfect.
>
>>>    --enablefmt FORMATNAME/ENGINENAME
>>>
>>> and say that the second form is mandatory if FORMATNAME occurs in
>>> fmtutil.cnf with more than one engine.
>>
>>
>> This part of the help text:
>>    --enablefmt FORMATNAME[/ENGINE] enable formatname in config file
>>    --disablefmt FORMATNAME[/ENGINE] disable formatname in config file
>>                               If more formats share the same name but have
>>                               different engines, the ENGINE parameter is
>>                               obligatory.
>>
>>
>> Does this satsify your needs?
>
>
> Perfect again.
>
> Thanks.
>
> Ken