Puppy Linux Discussion Forum

I'll shut down browser and start over...

OK, turned of Firefox.esr and rebooted BB(64).
I'll test now. Back in a moment.

OK, downloaded and executed gThumb.
I was able to copy the image and post it in a test email.
I then I attempted to post it here to you.
This is the message I'm getting file to big apparently.
But, look at the properties?
I'll try again.
Opps! Forum rule at bottom of page says:

Maximum filesize per attachment: 512 KiB

I'll try cutting the file shot down in size.
Back in a moment.

OK, I reduced image size using gThumb.
I placed reduced image into an email to myself.
Took forever to send image to myself, but, net is slow tonight.
Finally, the image was sent to my mailbox per normal.
I attached same image to this current post.
There was no complaint by forum that image was too large.
However...
attachment not showing in post preview.

Image shows only if I 'place in line' on this forum post.

Booted a fresh Bionic64 with nothing added. Downloaded a sample .webp image file.
Viewnior does not display it. Neither does mtPaint in this Puppy.
Any of these would need to have been compiled with webp support (linked to libwebp at build time - my builds of mtPaint have webp support).
The only on-board program that does display webp is Palemoon.

The mime-type issue is a bit of an inconvenience.
I did a test fix by adding to /usr/share/mime/packages/puppy.xml the lines:-

<mime-type type="image/webp">
    <comment>WebP image</comment>
    <glob pattern="*.webp"/>
  </mime-type>

Then in terminal

update-mime-database /usr/share/mime

and restart X
This changes the silly audio_x-riff mime-type in ROX to the correct image_webp and makes it easier to set up left-click and right-click associations for any image viewers you install or for Palemoon as the viewer.

mikewalsh wrote:

Unfortunately, all the apps that currently support it are either Windoze apps (need running via WINE) - or 'heavyweight' Linux apps. There simply aren't any small, lightweight, Puppy-type apps that yet support it.

Ahemmm...MMview supports it

I tried Palemoon 28.17.0(64bit) resident in BionicBeaver(64) to download what Firefox.esr 78.5.0 tells me is a .webp file.

Palemoon downloaded the file as JPG.

So, the solution is use Palemoon 28.17.0(64) in BionicBeaver(64) to download .webp files? Right?

Palemoon must have some kind of conversion routine when it encounters .webp files?

I'll mark this thread 'solved' if this is correct.

Thank you Oscar Talks.

Sky

Sky Aisling wrote: ↑Mon Feb 15, 2021 2:24 am

Palemoon downloaded the file as JPG.

Palemoon 28.9.1 downloads a .webp file as WEBP!
Try https://developers.google.com/speed/webp/gallery1

MochiMoppel wrote: ↑Mon Feb 15, 2021 2:01 am

mikewalsh wrote:

Unfortunately, all the apps that currently support it are either Windoze apps (need running via WINE) - or 'heavyweight' Linux apps. There simply aren't any small, lightweight, Puppy-type apps that yet support it.

Ahemmm...MMview supports it

@MochiMoppel :-

Mochi, I take my hat off to you, mate. That's bloody brilliant.

I kind of overlooked this on the old forum. I got the impression, from others mentioning it, that MM_View was simply another file-manager, so I didn't look any closer. I stand corrected..!

This is very like XNView.....only more so. That was the only native Linux app I'd come across that would display both images AND videos in the same application. Well this will (if you count playing your videos via the default media player; in my case, that's SMPlayer, so I'm happy with that), only this also displays just about every other kind of file (and information!) you can think of, too.

I've just set this up in jrb's 'lite' spin on BK's Quirky64 'April' 7.0.1, along with MenuEntries under Filesystem, Graphic and Multimedia. Nice one. This is very much appreciated, my friend. Cheers!

Mike.

If you want to be able to view and edit a .webp image, best thing to do is recompile the very latest mtPaint 3.50.05 from source, making sure to configure for webp support. I have done that. The .PET is here:-
http://smokey01.com/OscarTalks/mtPaint- ... bionic.pet

I've had luck with webp by simply right click on the web image, copy, and then paste into gimp and it copies fine. Then can save as whatever from there.

OscarTalks wrote: ↑Mon Feb 15, 2021 2:57 am

If you want to be able to view and edit a .webp image, best thing to do is recompile the very latest mtPaint 3.50.05 from source, making sure to configure for webp support.

Recompiling from source sounds like a lot of work, especially when using multiple Puppy or mtPaint versions. Another way would be to edit as usual in the image editor of choice and then convert the resulting PNG/JPG/GIF image to WEBP. Google offers small, ready-to-use command line tools to convert from/to WEBP and even a simple viewer. Newest versions only 64bit, but the last available 32bit versions contained in package libwebp-0.6.1-rc2-linux-x86-32.tar.gz work fine with older Puppies. All versions available in https://storage.googleapis.com/download ... index.html

Hi All,

The little program gThumb is working pretty good for my needs. A lot better than having the huge GIMP program hanging around.

Sky

I'm starting to have this same problem in viewing webP content in other fora as thread post attachments, using Seamonkey as browser (ver 2.53.15 -- current as of this time) on Bionicpup64.

Yes, I can download a webP file and view in a graphics program like Gimp, but that's way too much work for casual post reading. I'd like to be able to just see web forum photo attachments displayed directly in the browser, as I can with jpgs and pngs.

Is there any solution for this problem for BionicPup64, other than changing browsers? Or have I got something set wrong on my particular system?

Thanks for your help, guys, as usual!

Hmm, just tried the Google WebP gallery, and in fact Seamonkey DOES properly display the images there. Now I'm thinking that the problem is somehow related to the forum attachments themselves, rather than something in Seamonkey. I can download them, but when I click on them the browser reports unsupported format. I'll have to look into that further ...

Okay to get specific, here is an example attachment that seems to be misidentified by Seamonkey as a bin file and only offers to save it.

https://www.modelenginemaker.com/index. ... ach=143088

When downloaded and the file clicked on, Viewnior also cannot display it.

Open in MtPaint works, since it seems to have been compiled with WebP support.

appimage at bottom of page https://github.com/ImageMagick/ImageMag ... g/7.1.0-62
and if you want to write a script for a single usage https://imagemagick.org/script/command- ... essing.php

@vtpup
please check your seamonkey browser
SM built with webp and enabled ?

Thanks williwaw, norgo.

Norgo, yes webp enabled in SM per your about:config

williwaw, for some reason not seeing the appimage....checking again...

Assets just keeps circling, but no code.

Switching over to Firefox. Now I see the appimages. Sites seem to be giving Seamonkey more and more problems.

Switching over to Firefox. Now I see the appimages. Sites seem to be giving Seamonkey more and more problems.

chromium works too. sadly seamonkey works less and less. sometimes I am notified "your browser is not supported" and other times there are web features that just do not show on the page without any apparent way to tell something wrong with the rendering

Sorry, williwaw, what is the imagemagick appimage supposed to do?

I've run it, no change in Seamonkey's inability to open the url I listed earlier as an image.

But, as I've said before, Seamonkey can open inline webP images on the Google webP gallery site.

I'm thinking it's possibly a problem with seamonkey recognizing the mimetype....

If I go to Seamonkey Edit>Preferences>Helper Applications it looks like various image types are recognized, but I don't see WebP

the webp conversion sent me down a rabbit hole searching for apps that can do the conversion and put the links in a reply before I noticed you were looking for a seamonkey solution, I did see a firefox add-on also, maybe that will work in seamonkey?

Okay, my latest theory after some research. Seamonkey (and Firefox) does not look at the file extension (like .webp) to determine a file type. It is actually told by a server what the mime type of the file is when downloading it. It is also told if the file is an attachment image, or an inline image.

"....how a file is processed by a browser is determined by the Content-Type field in the http Response Header; the file suffix should be ignored when there is a Content-Type field. "

My guess is that the attached files I'm having a problem with either have a faulty Response Header, or because the image file is tagged as an attachment instead of in-line code, Seamonkey lacks the helper application to deal with webp attachments. It DOES have internal code capable of handling in-line webp files. Attached files and inline files are treated differently.

This does not explain exactly why Firefox does seem able to open those attachments, while Seamonkey doesn't. But Firefox handles them by downloading first, and then displaying in another tab. Not in-line. Typically in a forum, attachments do open in-line. This Firefox handling of these problem files is atypical. Therefore I think there is something problematic about the attachments themselves.

Browsers are apparently allowed to try to interpret the content , or use the extension as a clue IF the Response Header mimetype is absent. Maybe Firefox handles this situation, and Seamonkey is not able to yet for problematic attached WebP images.

@vtpup
in case that your seamonkey version has been compiled with option [ ac_add_options --with-system-webp ]
please check if webp is installed at your system
Could be a reason
I've no problems to view webp contents with seamonkey.

Hi Norgo, thanks!

I have no idea what was compiled into my Seamonkey. It is the standard Linux binary version downloaded directly from the Seamonkey site, and is current.

I also do not have a problem viewing webP images in-line on websites. I can view WebP images on Google's image gallery site.

I am beginning to suspect the Simple Machines Forum (SMF) software on the forum where I'm finding these few specific problem images. If the forum software itself is not handling these images right, and it is assuming that they are binary flles, that would mean that a thumbnail is not generated, and the files can only be downloaded by Seamonkey, unless Seamonkey itself can determine that they are images -- which it seems unable to do. Maybe Firefox recognizes them and is set to display them in a new tab rather than automatically download them.

I just tried uploading one of these webp images to this forum as an attachment and an experiment here, however this forum software does not accept webp image files as attachments. (I'm actually happy about that....).

I'm now wondering if the other forum software is not set up block the .webp extension as an attachment, but treats them as binary files, and does not identify them specifically to the browser.

I think that would explain everything I'm finding....

Here's a screenshot of what see on the other forum: (ps the file attachments labeled .jpg are apparently also mislabeled. They are in fact webp files, on examination)

There is a CLI binary pair (cwebp / dwebp) that I discovered that can convert images back and forth from .webp.

Works under Fossapup64 with JPG images anyway.

See https://developers.google.com/speed/webp
pointing to https://developers.google.com/speed/web ... recompiled

I just picked the Linux64 version, downloaded, Uextracted, found the cwebp binary, added in a JPG and ran ./cwebp input.JPG -q 80 -o output.webp

Still working to get it to go the other way (webp to jpg )!! but it does go back to .png : ./dwebp output.webp -o output2.png

@Geek3579 :-

./dwebp image.webp -o image.jpg

.....DOES seem to work for me. Yeah, I know; according to Google's notes it'll convert both PNG and JPG to WebP.....but only Webp -> PNG is mentioned. (Webp -> JPG still works, though.)

At least, for me it does. I think where you're going wrong is trying to change the name of the converted file AS it's being converted. I know you can do this with the "cp" or "mv" commands, but I don't think the webp binaries are set-up to work like that. I could, of course, be wrong. I frequently am!

Mike.

mikewalsh wrote: ↑Wed Feb 22, 2023 3:35 am

@Geek3579 :-

Code: Select all

./dwebp image.webp -o image.jpg

.....DOES seem to work for me. Yeah, I know; according to Google's notes it'll convert both PNG and JPG to WebP.....but only Webp -> PNG is mentioned. (Webp -> JPG still works, though.)

At least, for me it does. I think where you're going wrong is trying to change the name of the converted file AS it's being converted. I know you can do this with the "cp" or "mv" commands, but I don't think the webp binaries are set-up to work like that. I could, of course, be wrong. I frequently am!

Mike.

Thanks for that. I will try it later. Its a solution that might well work.

@Geek3579 :-

Before I forget, thanks for tracking those down. It wasn't until I read the 'front page' that I realised that WebM & WebP appear to be part of the same project. The 'binary' that interests me is the 'gif2webp'; I'm curious to see how an animated WebP file compares to a normal GIF....

Ta!

Mike.