-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EXIF FNumber is printed in an unexpected form #12718
Comments
Thanks for the report. I will try to improve the What you can try as a workaround is something like:
|
Yup, the workaround works:
Thank you for the quick response. |
bep
added a commit
to bep/imagemeta
that referenced
this issue
Aug 5, 2024
bep
added a commit
to bep/hugo
that referenced
this issue
Aug 6, 2024
Make it support the new upstream rational number type in Exif. See gohugoio#12718
bep
added a commit
to bep/hugo
that referenced
this issue
Aug 6, 2024
Make it support the new upstream rational number type in Exif. See gohugoio#12718
bep
added a commit
that referenced
this issue
Aug 6, 2024
Make it support the new upstream rational number type in Exif. See #12718
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using the following shortcode:
The result is unexpected. For FNumber 3.6, 18/5 is shown:
If the FNumber is printed with format string
%f
, the following appears instead:I think it might be related to #12651.
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes
The text was updated successfully, but these errors were encountered: