Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
IrfanView Comment bug?
4 views
Skip to first unread message
Terry Pinnell
Mar 17, 2013, 7:34:53 AM3/17/13
to
I open a JPG in IrfanView, then its Comment dialog. If I enter text which
includes the backslash, such as in c:\test, it gets written as c:\\test.
If Write was used again, it would become c:\\\\test, and so on. Looks
plainly like a bug.
Tests with Picasa and FastStone Image Viewer gave correct handling of the
backslash.
--
Terry, East Grinstead, UK
includes the backslash, such as in c:\test, it gets written as c:\\test.
If Write was used again, it would become c:\\\\test, and so on. Looks
plainly like a bug.
Tests with Picasa and FastStone Image Viewer gave correct handling of the
backslash.
--
Terry, East Grinstead, UK
Robert Coe
Mar 17, 2013, 8:32:10 AM3/17/13
to
On Sun, 17 Mar 2013 11:34:53 +0000, Terry Pinnell <terr...@dial.pipex.com>
wrote:
: I open a JPG in IrfanView, then its Comment dialog. If I enter text which
Irfanview is betraying its Unix (or Linux) origins. In Unix and its
derivatives, the backslash is an escape character, indicating that the
following character is to be taken literally, ignoring any control function it
might otherwise have had. So the backslash itself, if it appears in ordinary
text, must be doubled. Unix needs such a feature to balance its complex,
highly recursive, command line capability. Unix programmers will sometimes
double the backslash, as was done here, to keep it from being lost in a
command scan. Since Windows doesn't need the doubling, the extra backslash
becomes superfluous.
Depending on your point of view, this explains either why the behavior you
describe isn't a bug or why the bug is there.
Bob
wrote:
: I open a JPG in IrfanView, then its Comment dialog. If I enter text which
derivatives, the backslash is an escape character, indicating that the
following character is to be taken literally, ignoring any control function it
might otherwise have had. So the backslash itself, if it appears in ordinary
text, must be doubled. Unix needs such a feature to balance its complex,
highly recursive, command line capability. Unix programmers will sometimes
double the backslash, as was done here, to keep it from being lost in a
command scan. Since Windows doesn't need the doubling, the extra backslash
becomes superfluous.
Depending on your point of view, this explains either why the behavior you
describe isn't a bug or why the bug is there.
Bob
B. R. 'BeAr' Ederson
Mar 17, 2013, 8:35:41 AM3/17/13
to
On Sun, 17 Mar 2013 11:34:53 +0000, Terry Pinnell wrote:
> I open a JPG in IrfanView, then its Comment dialog. If I enter text which
> includes the backslash, such as in c:\test, it gets written as c:\\test.
> If Write was used again, it would become c:\\\\test, and so on. Looks
> plainly like a bug.
Confirmed for both, opening with Unicode plugin and without it. Error
> I open a JPG in IrfanView, then its Comment dialog. If I enter text which
> includes the backslash, such as in c:\test, it gets written as c:\\test.
> If Write was used again, it would become c:\\\\test, and so on. Looks
> plainly like a bug.
is on reading, which assumes the need for character escape sequences.
Such sequences aren't necessary/expected in *.jpeg comments, though.
BeAr
--
===========================================================================
= What do you mean with: "Perfection is always an illusion"? =
===============================================================--(Oops!)===
David Taylor
Mar 17, 2013, 9:51:53 AM3/17/13
to
On 17/03/2013 12:32, Robert Coe wrote:
[]
> Bob
More likely the programmer's use of "C" and its documentation, as there
is no UNIX-like version of IrfanView.
--
Cheers,
David
Web: http://www.satsignal.eu
[]
> Irfanview is betraying its Unix (or Linux) origins.
[]
> Bob
More likely the programmer's use of "C" and its documentation, as there
is no UNIX-like version of IrfanView.
--
Cheers,
David
Web: http://www.satsignal.eu
Mayayana
Mar 17, 2013, 10:23:27 AM3/17/13
to
If you look at the file in a hex editor you'll
see it's been saved properly. It writes whatever
is in the window but escapes all backslashes with
an extra backslash when the text is displayed. It
does seem to be a bug. Unix has nothing to do
with it.
The only thing I can guess is the following:
\ is an operator character in RichText (RTF) such that
an actual \ in plain text (TXT) must be escaped by an
extra \ when converted to RichText.
Windows standard text windows include plain text
and RichText. The IV comments text window is a plain
text window. It may be that it used to be a RichEdit
window -- or that a RichEdit window was planned and n
ot implemented -- and updating of the text display
operation was overlooked.
Just a thought. I can't think of any valid reason for
the way it's working now.
--
--
"Terry Pinnell" <terr...@dial.pipex.com> wrote in message
news:739bk893df8lsqr2v...@4ax.com...
see it's been saved properly. It writes whatever
is in the window but escapes all backslashes with
an extra backslash when the text is displayed. It
does seem to be a bug. Unix has nothing to do
with it.
The only thing I can guess is the following:
\ is an operator character in RichText (RTF) such that
an actual \ in plain text (TXT) must be escaped by an
extra \ when converted to RichText.
Windows standard text windows include plain text
and RichText. The IV comments text window is a plain
text window. It may be that it used to be a RichEdit
window -- or that a RichEdit window was planned and n
ot implemented -- and updating of the text display
operation was overlooked.
Just a thought. I can't think of any valid reason for
the way it's working now.
--
--
"Terry Pinnell" <terr...@dial.pipex.com> wrote in message
news:739bk893df8lsqr2v...@4ax.com...
Terry Pinnell
Mar 17, 2013, 10:57:59 AM3/17/13
to
"Mayayana" <maya...@invalid.nospam> wrote:
> If you look at the file in a hex editor you'll
>see it's been saved properly. It writes whatever
>is in the window but escapes all backslashes with
>an extra backslash when the text is displayed. It
>does seem to be a bug. Unix has nothing to do
>with it.
>
>The only thing I can guess is the following:
>
> \ is an operator character in RichText (RTF) such that
>an actual \ in plain text (TXT) must be escaped by an
>extra \ when converted to RichText.
>
> Windows standard text windows include plain text
>and RichText. The IV comments text window is a plain
>text window. It may be that it used to be a RichEdit
>window -- or that a RichEdit window was planned and n
>ot implemented -- and updating of the text display
>operation was overlooked.
>
> Just a thought. I can't think of any valid reason for
>the way it's working now.
>
>--
Thanks all. I've reported the bug to Irfan and will post back here with
> If you look at the file in a hex editor you'll
>see it's been saved properly. It writes whatever
>is in the window but escapes all backslashes with
>an extra backslash when the text is displayed. It
>does seem to be a bug. Unix has nothing to do
>with it.
>
>The only thing I can guess is the following:
>
> \ is an operator character in RichText (RTF) such that
>an actual \ in plain text (TXT) must be escaped by an
>extra \ when converted to RichText.
>
> Windows standard text windows include plain text
>and RichText. The IV comments text window is a plain
>text window. It may be that it used to be a RichEdit
>window -- or that a RichEdit window was planned and n
>ot implemented -- and updating of the text display
>operation was overlooked.
>
> Just a thought. I can't think of any valid reason for
>the way it's working now.
>
>--
his response.
@BeAr: I agree it's not a common requirement in most everyday text, but
for me it's essential! If I implement my Comment/Captions management with
TXT files as per our parallel discussion, then my comment will have to
include the full filename. I don't want to see that initially with double
backslashes like this
C:\\Docs\\My Pictures\\PHOTOS\\Walks
UK\\TP04\\TP04-All\\Tests\\20040820-111730.JPG
then later, after an edit, quadruple, octuple...
I'm an hour or so into trying ExifTools GUI but have a couple of basic
hangups. Will post in that thread.
B. R. 'BeAr' Ederson
Mar 17, 2013, 11:22:26 AM3/17/13
to
On Sun, 17 Mar 2013 14:57:59 +0000, Terry Pinnell wrote:
[IrfanView Jpeg comment reading bug]
[IrfanView Jpeg comment reading bug]
| Error is on reading, which assumes the need for character escape
| sequences. Such sequences aren't necessary/expected in *.jpeg
| comments, though.
| sequences. Such sequences aren't necessary/expected in *.jpeg
| comments, though.
> @BeAr: I agree it's not a common requirement in most everyday text, but
> for me it's essential!
What I wrote is: *escaping characters* is not necessary/expected. ;-)
> for me it's essential!
Terry Pinnell
Mar 17, 2013, 11:31:33 AM3/17/13
to
"B. R. 'BeAr' Ederson" <br.ed...@expires-2013-03-31.arcornews.de> wrote:
>On Sun, 17 Mar 2013 14:57:59 +0000, Terry Pinnell wrote:
>
>[IrfanView Jpeg comment reading bug]
>| Error is on reading, which assumes the need for character escape
>| sequences. Such sequences aren't necessary/expected in *.jpeg
>| comments, though.
>> @BeAr: I agree it's not a common requirement in most everyday text, but
>> for me it's essential!
>
>What I wrote is: *escaping characters* is not necessary/expected. ;-)
>
>BeAr
OK, my slip!
>On Sun, 17 Mar 2013 14:57:59 +0000, Terry Pinnell wrote:
>
>[IrfanView Jpeg comment reading bug]
>| Error is on reading, which assumes the need for character escape
>| sequences. Such sequences aren't necessary/expected in *.jpeg
>| comments, though.
>> @BeAr: I agree it's not a common requirement in most everyday text, but
>> for me it's essential!
>
>What I wrote is: *escaping characters* is not necessary/expected. ;-)
>
>BeAr
Jon Danniken
Mar 17, 2013, 2:39:14 PM3/17/13
to
On 03/17/2013 05:32 AM, Robert Coe wrote:
> On Sun, 17 Mar 2013 11:34:53 +0000, Terry Pinnell <terr...@dial.pipex.com>
> wrote:
> : I open a JPG in IrfanView, then its Comment dialog. If I enter text which
> : includes the backslash, such as in c:\test, it gets written as c:\\test.
> : If Write was used again, it would become c:\\\\test, and so on. Looks
> : plainly like a bug.
> :
> : Tests with Picasa and FastStone Image Viewer gave correct handling of the
> : backslash.
>
> Irfanview is betraying its Unix (or Linux) origins.
Irfanview has no *nix origins, as it is, and always has been, a Windows
> On Sun, 17 Mar 2013 11:34:53 +0000, Terry Pinnell <terr...@dial.pipex.com>
> wrote:
> : I open a JPG in IrfanView, then its Comment dialog. If I enter text which
> : includes the backslash, such as in c:\test, it gets written as c:\\test.
> : If Write was used again, it would become c:\\\\test, and so on. Looks
> : plainly like a bug.
> :
> : Tests with Picasa and FastStone Image Viewer gave correct handling of the
> : backslash.
>
> Irfanview is betraying its Unix (or Linux) origins.
application.
Perhaps you are thinking of another application?
Jon
Terry Pinnell
Mar 18, 2013, 3:56:03 PM3/18/13
to
Terry Pinnell <terr...@dial.pipex.com> wrote:
>Thanks all. I've reported the bug to Irfan and will post back here with
>his response.
Pleased to report that Irfan fixed it with impressive promptness. A new
>Thanks all. I've reported the bug to Irfan and will post back here with
>his response.
Metadata.dll in the Plugins folder did the trick. I expect Irfan will soon
release it.
--- Start paste ---
"\" is a special character and it was handled like that in the
original read-comment code from the JPG-Library ;-)
=> I removed the special handling, so it should be OK now, I hope no
side effects.
See the new plugin DLL, unzip it over your current DLL.
--- End paste ---
Terry Pinnell
Mar 19, 2013, 8:01:52 AM3/19/13
to
0 new messages