Unfluffing the Dictionary

[richmond62]

Possibly . . .

Just copied the folder

[path to your oxt lite install folder]/Documentation/html_viewer/resources/data/api/exports/xtalk/resaved

to a merry desktop folder called "Hax 30 November" so as not to poison anything.

This information:

"BBEdit will perform a find/replace on any group of files you want. Just hit command+shift+f to bring up Multi-File Search instead of the basic find/replace window."

fills me with hope.

Let's have an initial run with 'UNIX':
-

Screenshot 2024-11-30 at 10.28.39.png (120.3 KiB) Viewed 206 times

-

Screenshot 2024-11-30 at 10.29.50.png (313.63 KiB) Viewed 206 times

[richmond62]

379 occurrences of 'UNIX':
-

Screenshot 2024-11-30 at 10.35.19.jpg (277.9 KiB) Viewed 205 times

-
HOWEVER, "my problem de jour" is to know how many of those occurrences DO apply to UNIX (at which point those occurrences should REMOVED or marked with some sort of 'Historical' symbol, and how many really mean 'Linux'.

Because I do not know that I CANNOT do a 'simple' repalce every occurrence of 'UNIX' with 'Linux'.

----

So, as far as can see at the moment the 'clever' thing to do is locate all those documents that contain the string'UNIX' and pop them in another folder.

[tperry2x]

I did mention there's an easy way to do this in the text dictionary, I have a script which will recursively replace "UNIX" with "[whatever]" in each file. I just need to know what you want it replaced to.
It's then just a matter of me pressing return and it's done. As you said, I can output the changes into a new folder, so we can wade through it.

But either way, I appreciate the dictionary information text getting some attention and being corrected, as it's long overdue.

[richmond62]

recursively replace "UNIX"

Yup: well BBEdit can do that as well, in 2 shakes of a lamb's tail: BUT, as I observed, that will end up as confusing, because SOME instances of the term 'UNIX' refer to things that are not handled by Linux.

To separate the chaff from the wheat was a simple, but boring exercise, so I am uploading all the files from 'resaved' that contain 'UNIX' so that some other person does not have to do that all over again.

Just to make my point . . .

"PBM
(glossary)

Syntax:
Synonyms:
pbm, .pbm

Params:

Examples:
Description:
Portable Bit Map. A black-and-white picture format created for the "pbmplus" image conversion program and usually used on Unix|Unix systems.

Values:

OS:"

Does ANYONE even remember the PBM format, let alone use it, and can Linux handle a PBM file?

So, quite a lot of proper weeding needs to happen, and simple replacing 'UNIX' with 'Linux' would be a mistake.

[richmond62]

Ooooh, there is an entry for something called a MetaKey:
-

MetaKey.jpg (232.03 KiB) Viewed 198 times

-
If you know anyone who has a keyboard like this it is probably an extremely valuable antique by now.

[richmond62]

So, my chosen word-of-the-weekend has to be 'Triage'.

And 'triage' in this context means 'read every document that contains Unix' and make some informed (or, quite possibly, ill-informed) decisions on whether to edit it or chuck it out completely.

AND, now, off to do an unpleasantly large amount of greasy washing up . . .

[tperry2x]

The metakey comes into play on windows - in fact, I've always known the metakey to activate this in the screenshot.
However, the dictionary terms it as the 'alt' key on windows, which I'm not so sure about. Either way, It's the part that gets underlined. Normally in a menu (but not limited to it), for full keyboard control. The Metakey confusingly doesn't refer to a physical key on the keyboard. I'll try do a screenshot later.
Edit: It's now later:

altkey.png (12.94 KiB) Viewed 174 times

]

Capture.PNG (21.97 KiB) Viewed 174 times

[richmond62]

Thanks for that.

Hey: if you thought I was a pain-in-the-erm-"bread-basket" before, you ain't seen nothing yet!

So: cracking open acceleratorKey property.txt I find this:

On Unix systems, the key names are listed in the file "/usr/include/X11/keysymdef.h". Don't include the "XK_" prefix in these key names; for example, use "F8" for the key designated as "XK_F8" in the file.

Should I:

1. Just change 'Unix' to 'Linux'.

2. get up off my bahookie, run through to the other room, fire up my Xubuntu laptop, and fossick around to see whether (that type of Linux, at least) contains a file called "/usr/include/X11/keysymdef.h" ?

Why does #1 make me feel uneasy?

Should I:

Drag my laptop through 'here' next to my iMac so I can continually check whether the Linux file structure EXACTLY resembles the UNIX file structure, and, if it does, contains documents with the same names?

AND

'Cos if that be true, all I DO need to do is automagically change all the instances of UNIX to Linux.

OO, Er: https://askubuntu.com/questions/93772/w ... these-days

[richmond62]

I am tempted to delete the UNIX line, but that would NOT help really.

[richmond62]

Screenshot 2024-11-30 at 18.52.39.png (177.99 KiB) Viewed 172 times

-
I am slowly reading through each file, and resaving them into a folder called 'Linux'.

[richmond62]

The next file I find problematic is: boundingBox property.txt

Specifies the value of the "%%BoundingBox" comment in an import|imported PostScript|PostScript file.

Syntax:
set the boundingBox of {EPSObject} to {left}, {top}, {width}, {height}
----

Synonyms:

Params:

Examples:
set the boundingBox of EPS 1 to 100,100,500,600
----

Description:
Use the boundingBox property to control the appearance of an EPS|EPS object.

The %%BoundingBox comment specifies the height, width, and placement on the page of a PostScript file. Use the boundingBox property to find out these properties of the PostScript code in an EPS|EPS object, or to set them if the PostScript|PostScript file did not do so.

The four components of the boundingBox property are equal to the EPS|EPS object's xOffset, yOffset, xExtent, and yExtent properties respectively.

This property is supported only on Unix systems with Display PostScript installed.

Values:
The boundingBox of an EPS|EPS object consists of four integer|integers, separated by commas.

OS:
linux,ios,android

Are EPS images used nowadays? And if so; on Linux/iOS/Android?

[tperry2x]

In fact, if what they mean by the alt / meta key in windows is the same thing - these are referred to as "Access keys" now:

access-keys.png (145.5 KiB) Viewed 169 times

underlined.png (27.51 KiB) Viewed 169 times

Either way "the right of the ctrl key" is the Windows key. The alt key is to the right of the Windows key, that's if they are referring to a physical key after all.

[tperry2x]

Are EPS images used nowadays? And if so; on Linux/iOS/Android?

Well, I can create one. Can't do anything with it though

2024-11-30-17-06-03.png (11.66 KiB) Viewed 165 times

[richmond62]

currentPage property.txt

This property is supported only on Unix systems with Display PostScript installed.

?

[tperry2x]

The next file I find problematic is: boundingBox property.txt
This property is supported only on Unix systems with Display PostScript installed.

Can't find anything for "Display postscript". Also checked through package manager.
I'm going to go see if there's any long-forgotten lib somewhere.

display-postscript.png (21.22 KiB) Viewed 161 times

[tperry2x]

currentPage property.txt

This property is supported only on Unix systems with Display PostScript installed.

?

I'm assuming they mean the current page of an EPS. (But that's a guess), in case you have multipage EPS files (Freehand / Pagemaker)

yeah-multipage-eps.png (27.69 KiB) Viewed 155 times

[tperry2x]

Oh dear. I've disappeared down a "display postscript"-shaped rabbit hole:

[richmond62]

Please can you see if you can import this EPS image?

It should look like this:
-

sheep.jpg (18.22 KiB) Viewed 156 times

[tperry2x]

File > Import as control > Image file
(won't have it). Not listed under "images".

Can't drag and drop it onto a new stack either.
Think I'm going to have to try and track down this mythical "display postscript" library, before the IDE might see it.

inkscape chokes on that EPS image. Generates an error, with undefined postscript data. Illustrator says it was created in a newer version [than 9] of Illustrator, and won't display it.

So, I made my own.

Again, though - can't get it to import this EPS either.
The only way I can do it (which is a bit of a cheat) is with:

Code: Select all

gs -sDEVICE=pngalpha -o output.png -r300 sample-eps-object.eps

(At which point, it's not an EPS anymore, but a PNG) and obviously that displays fine:

2024-11-30-17-44-59.png (302.67 KiB) Viewed 122 times

So I'm off to try and track down this eps library, if it still exists. I found the PDF which proves it was once a thing.

[richmond62]

I don't think the "display postscript" library is mythical any more than my big, furry tail.

Oh, wait a moment, I don't have a big, furry tail: probably something to do with my ancestors losing theirs as they no longer needed them for balancing in trees, and found that they got in the way of bipedal movement.

https://en.wikipedia.org/wiki/Display_PostScript

"Early versions of PostScript display systems were developed at Adobe Systems. During development of the NeXT computers, NeXT and Adobe collaborated to produce the official DPS system, which was released in 1987. NeXT used DPS throughout its history, while versions from Adobe were popular on Unix workstations for a time during the 1980s and 1990s."

emphasis is mine.

https://community.adobe.com/t5/indesign ... p/10778810

"The EPS format has not been updated since the 1990s—when transparency was more or less in its infancy and so not recognized as a feature in the EPS format"

Um: big, furry tails.

Personally I'm in favour of dumping all references to EPS . . .

THOUGHTS?

VOTES?

ABUSE from the "We Love Encapsulated Postscript Fetishists Club of Akron, Ohio".