draft0 - a shared blog by just some people

Go To Navigation
Show/Hide Navigation

All Entries (Page 45)

36C3
File Attachments (30 files)
Comment via email
29C3
File Attachments (22 files)
Comment via email
Automatically Extracting A String For The Use Of Alt Text From An Image File's Metadata
XMP-iptcCore:ExtDescrAccessibility Iptc4xmpCore:ExtDescrAccessibility ExtDescrAccessibility XMP-iptcCore:AltTextAccessibility Iptc4xmpCore:AltTextAccessibility AltTextAccessibility XMP:dc:description dc:description IPTC:Caption-Abstract XMP:ImageDescription XMP:Descrption ImageDescription Description XMP:Headline Headline IPTC:Headline XMP-photoshop:Headline XMP-dc:Title dc:title Title IPTC:ObjectName Iptc4xmpExt:AOTitle AOTitle Some have been left out (uncommon, MS-specific). It's hard to decide where to stop this list. There will always be some tag that some image editing application, some batch script, some online converter or some weird camera writes but no major software ever reads. Some of the above are not according to the respective standard or don't belong in most image file types. But I argue it's worth checking for them because there's not much cost to it and people don't always follow standards exactly, thus manually tagging images or creating software that tags images with fields in the wrong namespace or with the same fields across all image file types. Looking for a string in all of those fields and inserting it as the alt text in <img> is not correct unless you know that a good alt text has been stored there. A script that automatically extracts the first string it find among a list of XMP fields could just as well find an unrelated string, the string 'none', a badly written alt text, one that was written for a different context or a string that was not meant to serve as the alt text to the image. Many of the fields that are listed above are meant to store something else than an alt text. Overall it is entirely expected that this method will not extract a useful alt text from the vast majority of images. I plan to use this method anyway, as a fallback, in the hopes that the cases where a more-than-use-less string will be extracted outnumber the cases where no alt text will be specified because the script is expected to find one. Writing a meaningfiul alt text for the context in which the image is used is still the only way to make sure that there is one. https://www.iptc.org/std/photometadata/specification/IPTC-PhotoMetadata#xmp-namespaces-and-identifiers https://www.iptc.org/std/photometadata/specification/IPTC-PhotoMetadata#xmp-namespaces-and-identifiers-2 https://www.iptc.org/std/photometadata/specification/IPTC-PhotoMetadata#xmp-properties https://www.iptc.org/std/photometadata/specification/IPTC-PhotoMetadata#iim-properties Other fields may be worthwhile to implement (Credit Line, Creator's Contact Info, Copyright Notice or others depending on the application). https://exiftool.org/TagNames/XMP.html https://exiftool.org/TagNames/EXIF.html https://exiftool.org/TagNames/ The above list is for image files in general. Other file type may have other/additional tags that are useful for similar purposes to the img tags alt attribute. Video file formats definitely have sevel different additional description fields. lang-alt fields may have strings in different languages.
Comment via email
Alternative Operating System: ToaruOS
This entry is referencing the entry 'Alternative Operating Systems'.

ToaruOS

🚧

Comment via email
Alternative Operating System: Snowdrop OS
This entry is referencing the entry 'Alternative Operating Systems'.

Snowdrop OS

🚧

Comment via email
Alternative Operating System: Shrine
This entry is referencing the entry 'Alternative Operating Systems'.

Shrine (Github)

Shrine is a fork of TempleOS. Let's not get into the interesting story of how TempleOS came to be. If you don't know it already, you can read about it, or not. Shrine is a fork that mainly gets rid of all the religious stuff but keeps the unique approach of how things are done in this OS. I'm not sure what other changes have been introduced in the fork. Development seems to be stalled. But it definitely is an improved version from TempleOS. There's a lot to say about this very different OS. I'll leave it to a few points: The only screen resolution is 640x480 and it has a text-based windows UI. Everything is very C. It's written in C, config files are C code, commands on the command line are C code, ... Keyboard shortcuts (as well as everything else) don't follow any existing convention. Everything about this OS seems unique and different, or at least alternative. I'm not an author of C stuff. So I didn't get much done in the time I tried Shrine. But I bet it's an interesting experience for others, even without contributing code. I wouldn't be able to use it with all it's blinking and moving title lines because of a lack of space (pixels).

Comment via email
Alternative Operating System: ReactOS and OpenNT
This entry is referencing the entry 'Alternative Operating Systems'.

ReactOS

🚧

OpenNT

Okay, since I've mentioned ReactOS, I'd also like to mention OpenNT.🚧

Comment via email
Alternative Operating System: RISC OS Open
This entry is referencing the entry 'Alternative Operating Systems'.

RISC OS Open

🚧

Comment via email
Mastodon