Conclusion? We refuse to use filenames that have "forbidden" characters
in them, and provide the user with sensible feedback.
Shouldn't be too difficult to implement. Does anybody agree with
increasing the importance to medium?
** Changed in: hugin
Status: New => Triaged
** Tags added: characters filename illegal
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679262
Title:
align_image_stack fails on paths with double quotes
Status in Hugin - Panorama Tools GUI:
Triaged
Bug description:
Adriaan van Os reports:
1. align_image_stack silently fails if the pathname to the source
files contains a name between double quotes
2. align_image_stack does some error reporting in this situation,
but, as far as I know, these messages are written to
standard-output rather than standard-error.
3. align_image_stack ignores the internal errors, happily
produces unaligned output images and returns exit code success
(exit code 0).
_______________________________________________
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : [email protected]
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help : https://help.launchpad.net/ListHelp
