Unfluffing the Dictionary

[tperry2x]

Hex 1212 is Ethiopic 'HHI'.
I can see all the school children in Norfolk jumping for joy knowing they can produce Ethiopic glyphs with Linux.
So extendKey.text should stay?

Haha, they would be mystified by it unless they can bring up a grid of characters onscreen and click on the one they want.
I think extendKey is still in use, or at least, still seems to work. Whether it has any or much use, that's not really for me to say. If we got rid of it - who would know the feature exists? (until you get someone complain that it's not documented).
If anything, perhaps we should add to the documentation to cover typing extra symbols and how this works with the extendKey? I'm probably (definitely) not the best person to ask. Anyone else reading this?

[richmond62]

GetOpt function.txt

Description:
Parse UNIX-like command line arguments, extracting options and their arguments.

I am NOT altering this, as 'UNIX-like command line arguments' are just that where-ever they are.

[richmond62]

32 documents "done" this morning.

Stumping off for lunch.

Will try as many this afternoon.

Quite a few of these will "come down the pipe" again re the Mac/Mac OS/MacOS/OS X/OS X Systems "inconsistency" (bloody sloppy) that
peppers the documents like a bad case of chickenpox.

[richmond62]

Wow! 15 minutes in a massage chair + a cup of coffee.

import command.txt

"The import command can import GIF, JPEG, PNG, BMP, XWD, XBM, XPM, or , PGM, or PPM files."

Emphases are mine.

REALLY: most of this says more about my trip to the massage chair than images:

XBM : Xtreme Back Massage

XPM : Xtreme Pelvic Massage

PBM : Perfect Back Massage

PGM : Pretty Good Massage

PPM : Pretty Perfect Massage

not forgetting the excessive car:

XWD : Ten Wheel Drive.

But, Seriously (surely not?): are any of those distinctly outdated images formats capable of being imported into anything on Linux?

Seriously :
-

mChair.jpg (8.37 KiB) Viewed 1622 times

[richmond62]

Humph:

I only managed another 14 files.

Teaching "tinies" in about 10 minutes: so, nothing more until tomorrow.

Attaching the files I have "gone through" so far in case someone wants to "go through" them again, or bung them back into the 'resaved'
directory.

[richmond62]

OF COURSE those have ONLY been altered with regard to UNIX, not to MacOS.

Which is a 'nice' way of saying that the vast majority of them will have to be re-examined for Macintosh cafuffles.

[richmond62]

Oh, and, err, yeah: the image format question:
-

SShot 2024-12-02 at 15.36.37.png (41.54 KiB) Viewed 1612 times

-

SShot 2024-12-02 at 15.37.35.png (34.62 KiB) Viewed 1611 times

-

SShot 2024-12-02 at 15.38.27.png (48.13 KiB) Viewed 1611 times

-
I wonder when anyone used a barebones system with just the X windows system?

[richmond62]

SShot 2024-12-02 at 15.39.54.png (52.33 KiB) Viewed 1610 times

-

SShot 2024-12-02 at 15.40.41.png (51.93 KiB) Viewed 1607 times

-

[tperry2x]

Thanks for these Richmond. They are looking good.
I've spotted the add should be a "command", not a "property" so have corrected the filename and the index.txt

I also spotted there's a lot of double spaces in the dictionary text. (It's there in the originals too).
Rather than sit and have to remove two spaces and replace with one, I might just get the dictionary stack to do this. That would be a lot easier.

my_amends.zip

(17.29 KiB) Downloaded 31 times

[richmond62]

Wonderful: I also noticed all those double spaces, but wondered if they were there for some arcane reason.

Also cannot work out the difference between

Unix

and

Unix|Unix

[richmond62]

SShot 2024-12-02 at 15.44.08.png (50.04 KiB) Viewed 1598 times

-
Well, well, well: we all learnt something new.

[tperry2x]

Wonderful: I also noticed all those double spaces, but wondered if they were there for some arcane reason.

No, unfortunately they aren't there for any good reason. Just shoddy data entry on the original dictionary.

Also cannot work out the difference between
Unix
and
Unix|Unix

unix|unix means the dictionary will make a link in the text, with the name "unix". When you click it, it'll put "unix" in the search field.
So that might be handy if you wanted to pepper the text full of links. For example, if you used:

Code: Select all

The womble|backgroundPattern of an image...

You'd see "The backgroundPattern of an image..." and when you clicked on the backgroundPattern, it'd search for womble in the field.

I've just tweaked the dictionary stack somewhat (so it filters out things like "term(glossary)" and replaces with "term" instead). Please replace with this one attached, or I can do it as an update. Purely up to you.

oxt_dictionary.oxtstack

(90.86 KiB) Downloaded 31 times

(Otherwise, to be included in some future update).

[FourthWorld]

GetOpt function.txt

Description:
Parse UNIX-like command line arguments, extracting options and their arguments.

I am NOT altering this, as 'UNIX-like command line arguments' are just that where-ever they are.

Good call. That one's fairly recent, added by Dr Peter Brett in 2016. If you're making a command line app in LC it's a godsend, making short work of what used to require a cumbersome script if your app supports a lot of options.
https://lists.runrev.com/pipermail/use- ... 28348.html

Background:
https://en.m.wikipedia.org/wiki/Getopt

[richmond62]

Does the zip file my_amends contain ONLY amended versions of the files I have changed, or the whole 2700?

Because if it the latter, I am NOT editing the ones I have already edited for 'Unix'.

[tperry2x]

just-three.png (6.31 KiB) Viewed 1424 times

Just three. But you don't have to use them. The index file gets regenerated anyway if it has write access.
The "add command.txt" was called "add property", yet the text inside refers to a command, not a property - so it should really be renamed to "add command.txt" as I've done.
The "backgroundPattern property.txt" is just me fixing the links on the text in the description, as an example - showing how I use the | to make links in the description (I might call it 'the womblelinker' now) since I seem to have inadvertently found a name for it above. However I don't expect you to go through, also correcting links.
These three text files are based on your edits, so as not to get you going back over the same work twice.
The index has the "add command.txt" mentioned, rather than "add property.txt" since I changed the name.

Don't worry about using any of them if you don't want to. I can always go back over each as a 'second pass" - all (2707 of them), and correct the links as to what they should be. It can then be a joint effort. Either way, your work on this is appreciated.

I do also plan to look through the "Dictionary edits" topic, as that mentions things that need fixing too.

[OpenXTalkPaul]

SShot 2024-12-02 at 15.44.08.png
-
Well, well, well: we all learnt something new.

This has been discussed in these forums previously, Netpbm that is (https://openxtalk.org/forum/viewtopic.php?p=6759#p6759) there is actually both a human readable ASCII-text format, which can be very handy for scripting pixels of images (that's how I generate the display images for that GIMP index colors importer https://openxtalk.org/forum/viewtopic.php?p=7962#p7962), and also each (1bit, 8 bit, 24bit, etc.) have their own more compact binary equivalent formats.

Very simple file format, the Wikipedia Article pretty much covers it:
https://en.wikipedia.org/wiki/Netpbm

[OpenXTalkPaul]

I thought we went down the EPS control rabbit whole before on this forum too.
Yeah there were NeXT, Sun, SGI (high-end) Workstations back in the day (1980s to 1990s) that used Display Postscript.
In fact there was for Sun Open Windows (not FOSS) a toolkit NeWS with an xCard-like thing call HyperNeWS (or HyperLook?), that was scriptable using Postscript (which is a full fledged programming language) instead of our (much more readable favorite) xTalk.

https://donhopkins.medium.com/hyperlook ... f411e58ce4
http://bitsavers.trailing-edge.com/pdf/ ... k_1989.pdf
https://donhopkins.com/home/documents/N ... InNeWS.pdf
https://donhopkins.medium.com/hyperlook ... f627eab14a
https://donhopkins.medium.com/the-story ... 7992b4c797

I'm pretty certain that It's on a machine with Display Postscript built into the Window server, like those mentioned high-end workstations from thirty years ago, where MetaCard's EPS Object once worked as expected, now it basically produces a control that is simply a gray rectangle.
It's strange to me that it was not removed from the engine two decades ago. I'm not sure if it would be possible to rewire those bits in the engine to use some alternative like GhostScript: https://www.ghostscript.com/index.html

[richmond62]

Cripes!

libURLSetFTPListCommand command.txt

I am now finding triple-SPACE gaps between words.
-

HopPicker.jpg (122.34 KiB) Viewed 1323 times

[richmond62]

lookAndFeel property.txt

Appearance Manager: standard Windows XP, Mac OS and OS X look and feel
Macintosh: emulated Mac OS Platinum appearance, used regardless of current theme
Motif: standard Motif look and feel for Linux systems
Windows 95: standard Windows look and feel

Why do I have a funny feeling that the 'standard' Windows look and feel may no longer conform to an operating system produced 29 years ago?

Oh, and how-in-blazes do you 'feel' an operating system?

[richmond62]

metal property.txt

metal
(property)
Displays a window with a textured-metal appearance.

-

Screenshot 2024-12-03 at 11.57.50.png (155.28 KiB) Viewed 1318 times

-
Not for donkey's ages it hasn't . . .