![]() | |
![]() |
| | Thread Tools | Display Modes |
#21
| |||
| |||
|
|
On 24 Sep, 20:59, "Jukka K. Korpela" <jkorp... (AT) cs (DOT) tut.fi> wrote: Thus, at least when taken as a general statement, Andy's claim "Why specify Times and Times New Roman together? The synonym mechanisms will merge those." was not correct, in CSS authoring, even if we limit ourselves to the Windows world. Perhaps not, but it's (as ever) a pragmatic approach. What else are you going to do? Specify _every_ variant naming of "TNR/ Times/New/Roman/Rmn/Ramen" to try and make one stick? |
#22
| |||
| |||
|
|
What else are you going to do? Specify _every_ variant naming of "TNR/ Times/New/Roman/Rmn/Ramen" to try and make one stick? No, the point is that Times New Roman and Times (or Times Roman) can be different fonts. |
|
it's still a meaningful idea to suggest, say, font-family: Times, Times New Roman |
|
What I expect to get is a Times font designed by Linotype, when available, and Times New Roman, a Microsoft font, otherwise (and more often). |
#23
| |||
| |||
|
|
Besides, I just checked the settings in my current computer. Regedit tells that there are mappings for Times and Helvetica, as you wrote (though not for Courier). Yet, when I test an HTML document where I set font-family in CSS, text set to Helvetica is different from text set to Arial (though similar), and ditto for Times and Times New Roman. |
#24
| |||
| |||
|
|
No, the point is that Times New Roman and Times (or Times Roman) can be different fonts. Of course. But they're _unknowably_ dfifferent, if we assume "the web" rather than some controlled intranet. |
![]() |
| Thread Tools | |
| Display Modes | |
| |