<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 19, 2013, at 6:15 PM, Herbert Schulz <<a href="mailto:herbs@wideopenwest.com">herbs@wideopenwest.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">Or... just put all the fonts in one location, e.g., .../texmf-local, and still live with one updmap.cfg file. :-)</span><br style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "></blockquote></div><br><div>That works very well as long as you don't use the --enable/--disable options to updmap-sys, perhaps inadvertently, which will create an updmap.cfg in texmf-config. (This happens when you install fonts with scripts like getnonfreefonts-sys, for example.) Then you have two updmap.cfg files, one trumping the other for the remainder of the current TeXLive year. That's not to say that keeping as much as you can in texmf-local doesn't have some serious advantages---it does not need to be reinstalled with every new TeXLive year. To me, having one updmap.cfg that lasts forever even when using --enable/--disable, with the proper initiation each year, is worth a lot.</div><div><br></div><div>Michael</div></body></html>