hugin-devs team mailing list archive

[Yuv <687301@xxxxxxxxxxxxxxxxxx>]

Special Characters in Paths

=        ;       :      $       "        %      #               '
(       )       `       &       *       +       ^       ~       <
?      >       and the space character.

Hugin currently does not do plausibility checks on the paths and file
names that are given to it. It relies on the operating system's
conventions and limitations. However Hugin uses make to run the
stitching process, and make has more restrictive limitation than the
operating system.

Please don't use the above characters in your files and folders when you
want to make sure they work with Hugin. If you absolutely need files
named this way, rename them after processing. Do not file bug reports
based on filenames with the above characters. The issue is known,
analyzed, and may be fixed in the future.

** Changed in: hugin
       Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/hugin/+question/137057

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/687301

Title:
  Single quote in path of loaded image causes control point detection to fail

Status in Hugin - Panorama Tools GUI:
  Invalid

Bug description:
  Just ran into a weird issue with Hugin 2010.2. If you load images that have a single quote anywhere in their path, control point detection will always fail, no matter which detector or what settings. Something is not being escaped properly.

E.g., if you're loading images stored in:
/Users/you/Desktop/Friend's Birthday/…

When you click (Align), you'll get errors in the little console window that pops up while control point detection is happening. Unhelpfully, this window appears and disappears so quickly, you can't even read the details. It would be nice if those errors could be written to a log file or something. Very frustrating having the console window immediately vanish when you're trying to see WHAT the damn problem is.

For now the workaround is to just make sure you don't have any single quotes in the path of any images you're loading.