Argumentum
Forum Replies Created
-
I also had to add the following code to override the original Related Posts CSS:
@media only screen and (max-width: 640px) { #jp-relatedposts .jp-relatedposts-items .jp-relatedposts-post:nth-child(3n) { clear: none; } }Without that, the 6th post would create a new row (in
max-width: 640px, of course).Forum: Themes and Templates
In reply to: [Gazette] Author bio not showing upHa! That was the problem. Thanks.
Hi,
Sorry to bump this thread, but apparently the WEBP implementation is broken again. See the examples below in Chrome or Opera:
Example 1
Original: http://goo.gl/QeolJQ
Photon: http://goo.gl/Lz9077Example 2
Original: http://goo.gl/jMWjcu
Photon: http://goo.gl/A9WaalNo problems in Firefox or IE.
Thanks again.
Forum: Themes and Templates
In reply to: [Twenty Sixteen] recommended size for featured images1200 pixels wide.
Forum: Themes and Templates
In reply to: [Twenty Sixteen] Where is the documentation for Twenty Sixteen?You can find some information here: https://theme.wordpress.com/themes/twentysixteen/
Forum: Themes and Templates
In reply to: [Twenty Sixteen] Add a logoThe saddest thing about it is that the Twenty Sixteen theme for WordPress.com (https://theme.wordpress.com/themes/twentysixteen/) has a site logo option. I don’t know why they didn’t include that in the WordPress.org theme.
If that’s the case, then yes, I misinterpreted the first sentence, but I still think the documentation should be more clear to avoid such mistakes. I’d suggest: “For JPEGs a setting of 100 will output the image at the original unaltered image quality setting, but the image will be processed using a lossy compression”.
About the second sentence, at least from my point of view, using a lossless optimisation utility doesn’t necessarily mean we will get lossless processing. From our discussion here, it seems clear that it’s impossible to get JPEG lossless processing with Photon, so the second sentence should state it is available only for PNG files.
Is there any proper way to suggest those changes in the documentation?
Thanks.
I agree they’re looking great and any visual change is barely noticeable (if noticeable at all), but that is valid only for high-quality source images. Images with high compression still suffers, but I kind of gave up using them, because, from what I understand, that’s not going to change soon.
In any case, those sentences I quoted are still incorrect. I just think the Photon documentation needs to be (or look) more accurate than it is now.
Come on, guys… Don’t you agree those sentences needs to be changed?
Great. I did some quick tests here and, apparently, now both Chrome and Firefox show the images with a very similar look (as I described above on note #1 – low-quality JPEG images with some colour distortion; high-quality JPEG images with almost no distortion).
I understand and sympathise with your explanation regarding the image processing, but it would be great for users to have more control over it. I am not sure about it (and I am sorry if I am being nonsense here), but at least in my case I think turning off the image processing could mean less stress on Jetpack or WordPress (i.e., less use of its resources).
Anyway, I know it won’t happen (at least soon), but I still hope to see that option one day.
—
As I said above, I may be misreading something, but I think the Photon documentation needs some editing to be more accurate. These sentences don’t look right for me.
https://developer.wordpress.com/docs/photon/api/
For JPEGs a setting of 100 will output the image at the original unaltered image quality.
https://developer.wordpress.com/docs/photon/
Lossless compression is available by specifying a quality setting of 100 in the query arguments.
I’d suggest changing the first sentence to something like: “For JPEGs a setting of 100 will output the image with the best possible quality, but the image will be processed using a lossy compression.” The second would be better like this: “Lossless compression is available only for PNG by specifying a quality setting of 100 in the query arguments. JPEG lossless compression is not available.”
Thanks again for your support and attention.
Great, nice findings. You’re right, I saw all those issues with Chrome. They are also present in Opera, which is Chromium-based. All the images look way better in Firefox, Safari and IE.
After making some additional tests using Firefox, I have this to say:
1. As you said, I do have to use high-quality JPEG images with Photon. When I use a low-quality JPEG image, Photon still distorts the colours a little bit (even when the original image has 2×2, 1×1, 1×1 subsampling and is viewed in Firefox). When I use a high-quality JPEG image, the colour distortion (if there is any) is not easily noticeable.
2. I am sorry for insisting on this point, but that “requirement” (using high-quality JPEG images) apparently only exists because Photon does make changes on files even when
qualityis set to100. I mean, ifquality=100worked the way I want, I could use low-quality JPEG images with no problems. Photon changes both low and high-quality JPEG images. Am I doing something wrong here, or am I misreading the links I posted in my previous posts, or are the sentences I quoted wrong?Thanks again!
David, I forgot to say the Photon images in my examples are results of Photon’s default settings (quality=90), if that makes any difference.
On Image #1, Photon changes the colours even if I save the file with high quality. See the examples below:
Original (XnView 70): http://goo.gl/QeolJQ
Photon (XnView 70 + Photon 90): http://goo.gl/Lz9077So it seems the colour change is not related to the compression level of the file.
EDIT: I added two more examples, this time with quality 80 and 2×2, 1×1, 1×1 subsampling. And guess what… Photon still changes the colours!
Original (XnView 80): http://goo.gl/rGS7lq
Photon (XnView 80 + Photon 90): http://goo.gl/IQEp1p—
Anyway, I know my posts were long, so I am repeating the two questions I made before here:
1. Is it possible to tweak
qualityandstripparameters for each upload?2. Why is quality 100 (on Photon) still compressing/reprocessing my images? Am I misreading something here?
https://developer.wordpress.com/docs/photon/api/
For JPEGs a setting of 100 will output the image at the original unaltered image quality.
https://developer.wordpress.com/docs/photon/
Lossless compression is available by specifying a quality setting of 100 in the query arguments.
—
Just to explain, I like to try using low quality settings on high-resolution JPEG images to see how they look on high-DPI screens. Sometimes a “retina” JPEG image with low quality settings looks better than a low-resolution JPEG image with high quality settings:
https://www.filamentgroup.com/lab/compressive-images.html
http://www.karelia.com/retina/(big edit; ignore this and see post below)
I would like to add some points, just for further clarification. Here are my examples again:
Image #1 (quality 30 with XnView)
Original (71.16 KB): http://goo.gl/8ah2E8
Photon (72.24 KB): http://goo.gl/ObNkdbImage #2 (quality 10 with Photoshop)
Original (230.38 KB): http://goo.gl/Tj9cKQ
Photon (282.38 KB): http://goo.gl/tI5XaqThe labels I’ve used might have caused some confusion. So let me clarify them.
“Original” there means the image that was saved with the aforementioned settings (quality 10/30, XnView/Photoshop) and uploaded to Media Library. “Photon” means the same image, saved with the same settings and uploaded to the same Media Library, that was reprocessed by Photon and hosted at ix.wp.com.
What I did not do: picked one image (source), saved with XnView, called it “Original”. Picked the same image (source), used Photon, called it “Photon”. Compared both.
What I did do: picked one image (source), saved with XnView, called it “Original”. Picked the image saved with XnView (“Original”), used with Photon, called it “Photon”.
So, on Image #1, it’s not XnView (“Original”) vs. Photon (“Photon”). It is XnView (“Original”) vs. XnView + Photon (“Photon”).
Image #2 is not Photoshop vs. Photon. It is Photoshop vs. Photoshop + Photon.
Again, I didn’t mean to compare the compression algorithms of XnView and Photoshop to Photon’s. I just wanted to show what Photon’s compression does to a highly compressed image.
The change in colours of Image #1 is especially bad because Photon is doing something it shouldn’t do. The “Original” image has the same colours of the source image.
Thanks for your reply, David.
I am aware of the concept of “quality” in JPEG, I am sorry if I gave you the wrong impression about it. I now realise that my writing and my examples might confuse some readers, so, just to be clear, I want to state this: I wasn’t saying that Photon’s compression is bad or something. That’s not what I meant.
With my two examples, I did not mean to compare the quality of compression algorithms by XnView, Photoshop or Photon. I just wanted to show what Photon is doing to heavily compressed images that I upload: increasing their size while decreasing their quality.
I didn’t know Photon is intended to be used with a source image with a high quality setting, I think that could be made clearer for the user.
You say:
The source image should be uploaded at a high quality and then Photon should be used to tweak, via the
qualityand optionalstripparameters, until an acceptable visual quality level is attained.I ask: is it possible to do that for each upload? Since each image needs a different treatment, ideally the user would have the option to tweak it easily and individually. Or, better yet, the option to disable the “reprocessing”, allowing him to make the necessary tweaks before the upload. It’s very sad to know that it’s impossible.
By the way, these articles gave me impression (and hope) that it would be possible to disable the reprocessing:
https://developer.wordpress.com/docs/photon/api/
For JPEGs a setting of 100 will output the image at the original unaltered image quality.
https://developer.wordpress.com/docs/photon/
Lossless compression is available by specifying a quality setting of 100 in the query arguments.
That is why I tried to use that filter with quality 100. I though “output the image at the original unaltered image quality” and “lossless compression” meant exactly that. Therefore I ask you a second question: am I misreading something here? Why is quality 100 still compressing/reprocessing my images?
Thanks in advance.