"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
But they can be pointed to in the installation instructions of OWB. Debian also doesn't provides the fonts as part of the package, but there's a script that downloads and installs them. That way all's clean and nice.
Edit: And as Joerg pointed core fonts are optional and in abscence Deja-Vu fonts are used (afair).So they aren't destributed in the proposed above way, but suggested-with-links.
Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
had they been required it would not have been a good solution to require an extra download in a fresh os4 install.
Yup. Luckily it is optional. To be OK legally-wise the stuff should be repackaged to contain the EULA b/s.
Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
2. copy the /usr/share/fonts/truetype/msttcorefonts dir to Amiga
3. Use type manager to install the fonts, skip duplicates and remove the redundant "*_0" and "*_1" entries in the installed fonts side of type manager.
Jack
Edited by Jack on 2008/2/21 23:44:33
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
3. Use type manager to install the fonts, skip duplicates and remove the redundant "*_0" and "*_1" entries in the installed fonts side of type manager.
That's a nearly sure way to get fonts which don't work in OWB since TypeManager doesn't set up the font families automatically, you have to do that yourself after installing the fonts. That's why I created the corefonts.lha archive with the .font and .otag files for the core fonts, with the correct names and with the font families set ...
I've created a small test page to check the installation of the core fonts, you have to start OWB from a shell to check if everything works correctly (there must be no messages from OWB about missing fonts).
That's a nearly sure way to get fonts which don't work in OWB since TypeManager doesn't set up the font families automatically, you have to do that yourself after installing the fonts. That's why I created the corefonts.lha archive with the .font and .otag files for the core fonts, with the correct names and with the font families set ...
You're right, proper way is not to install your .font and .otag files, but to import the relevant linux fonts (to select lower or upper case linux files). (edit: and to "modify" the plain font of each family to have bold/italic/bold italic parts assigned in typemanager)
Interestingly, the wrong way did work for me (I think I know why).
edit2: BTW: why the designated bold/italic/bold italic fonts are not picked up requiring to modify the plain fonts? Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
BTW: why the designated bold/italic/bold italic fonts are not picked up requiring to modify the plain fonts?
It's possible to calculate italic and bold fonts from the regular ones, but of course the designed ones look much better.
Without the names of the other family members in the .otag files it's not possible to find them, for example simply appending " Bold Oblique" to the regular name for getting the bold italic one works for "DejaVu Sans", but it doesn't for "Arial" ("Arial Bold Italic") or "Nimbus Mono L Regular" ("Nimbus Mono L Bold Oblique").