absque fenestris wrote: ↑Wed Dec 02, 2020 3:29 pm
- 1. a simple image processing application à la Irfanview. More precisely, a program that would combine Irfanview, Faststone and ShiftN from the Windows side, as well as Macs Preview, LibreOffice's Draw and - from Mint's point of view, Pix - in a single, great and simple to use image processing program ...
If I'm in a mode where I'm heavily playing around with image file management, I'll set the Nemo thumbnail size to something large enough to visually keep track of what I'm doing, and I use the default image preview program to do a detailed review of the image so I can tell if, for example, it's the version I want to keep. If I were a pro, I'd probably be more inclined to use something like Dark Table.
- 2. a Layout program à la PageMaker from 1996. Scribus is still lame and cumbersome - and in my opinion still very user-unfriendly. And yes - LibreOffice Writer just isn't a layout application ...
I cut my teeth on PageMaker, and in more ways than I can count, you're absolutely right. If I had the money to invest so that I could have some ability to steer the direction of things, I'd try to get Scribus to be the best possible hybrid of QuarkXPress and InDesign. I'm told that recent series of QXP have gone to crap, and that Quark has really taken a customer service nosedive, but back in the day (QXP 3-6) nothing could touch it, especially in a hardcore production environment. InDesign really incorporated a number of effects and capabilities which made it easier to do more graphic design-type work in the middle of a desktop publishing project.
I think Scribus has a lot of promise, but it's extremely rough around the edges. A lot of this is exacerbated by the proliferation of proprietary technology as industry standards (this is, in essence, how it's always been) and that means a lot of "standard" and "normal" things, like color management, for example, either require prohibitively expensive licenses, or heavy lifting to try and reimplement them as libre code without stepping on patented, trademarked, or otherwise copyrighted elements.
And incidentally, this is but one area which demonstrates why software patents are a very bad legal concept.
- 3. a sensible, customizable font management. Fonts grouped in families. MacOS 7, 8, 9 in combination with Adobe ATM showed more than twenty years ago that something like this is possible. It now seems that this cannot be implemented in Linux, Windows or the more recent Mac systems. Nice progress!
In addition, under Linux (also under Linux Mint) it would be necessary to clarify what should happen to PostScript Type 1 fonts in the future. Just turning it off and showing weird rectangles is a bit shabby.
A Macintosh Plus was my very first computer. I ran ATM (Adobe Type Manager, for the uninitiated) on basically every version of Classic Mac OS which it supported. I still remember Font/DA Mover (with a little bit less than fond feelings, I might add) and dealing with font conflicts, separate versions of font faces for Mac OS and Windows, etc.
There's a bit more going on behind the scenes vis a vis font listings in menus are concerned, I suspect. Now, font designers who actually know what they're doing, will take the time to ensure all the appropriate parameters are correct. For example, when you have multiple weights of a font (this refers to both thicknesses as well as other things, like italics) you have to make sure you're setting up each face as a member of a common family (for example, if there was a font called "Absque Fenestris", then you might have:
• Absque Fenestris Light
• Absque Fenestris Light Italic
• Absque Fenestris Book (or
Regular, or no additional descriptor)
• Absque Fenestris Book Italic (it would follow the convention used by
Book above)
• Absque Fenestris Medium
• Absque Fenestris Medium Italic
• Absque Fenestris Demi
• Absque Fenestris Demi Italic
• Absque Fenestris Bold
• Absque Fenestris Bold Italic
and so forth and so on.
However, the "family name" would be Absque Fenestris, and this would have several naming conventions to suit how different OSs require name data to be entered (generally without spaces). Also, does the OS itself give the capabilities of a single slug listing for the family, with a hierarchical menu for each weight? Beyond that, did whomever wrote any particular program you might use implement that? Even in Classic Mac OS, this could be a problem with programs written by folks who didn't have the interest in including that sort of high polish finishing touch to their code.
One of the things Apple (or at least Apple of old) had going for it was they had a lot of visual arts folks on the payroll who could ensure such things were done properly.
I have an archive of fonts, much of which comes from a multi-decadal collection. Many originated as fonts for the Classic Mac OS environment, and others from the Windows 3.x->W98 environment. They're now all converted to OpenType, with a dogged, one might even describe as obsessive, attention to detail, and yet the greatest limiting factor — really, the only one — is how a given program handles font handling.