Hello, while trying 2019.0 beta1 lintian found some typos. Trivial patch attached.
cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/20190126142509.GB1352%40argenau.bebt.de. For more options, visit https://groups.google.com/d/optout.
Description: Fix typos Unknow/Therefor/therefor Found by lintian. Author: Andreas Metzler <[email protected]> Origin: vendor Last-Update: 2019-01-26 --- hugin-2019.0.0~beta1+dfsg.orig/doc/cpfind.pod +++ hugin-2019.0.0~beta1+dfsg/doc/cpfind.pod @@ -29,7 +29,7 @@ was successful two keypoints in the two =head2 Rectilinear and fisheye images -Cpfind can find control points in rectilinear and fisheye images. To achieve good control points images with a high horizontal field of view (e.g. ultra wide rectilinear or fisheye) are therefor remapped into a conformal space (cpfind is using the stereographic projection) and the feature matching occurs in this space. Before writing the control points the coordinates are remapped back to the image space. This happens automatic depending on the information about the lens in the input project file. So check that your input project file contains reasonable information about the used lens. +Cpfind can find control points in rectilinear and fisheye images. To achieve good control points images with a high horizontal field of view (e.g. ultra wide rectilinear or fisheye) are therefore remapped into a conformal space (cpfind is using the stereographic projection) and the feature matching occurs in this space. Before writing the control points the coordinates are remapped back to the image space. This happens automatic depending on the information about the lens in the input project file. So check that your input project file contains reasonable information about the used lens. =head2 Using celeste --- hugin-2019.0.0~beta1+dfsg.orig/src/hugin1/hugin/MainFrame.h +++ hugin-2019.0.0~beta1+dfsg/src/hugin1/hugin/MainFrame.h @@ -81,7 +81,7 @@ private: * It contains the menu & statusbar and a big notebook with * the different tabs. It also holds the Panorama model. * - * it therefor also hold operations that determine the lifecycle + * it therefore also hold operations that determine the lifecycle * of the panorama object (new, open, save, quit). */ class MainFrame : public wxFrame, public HuginBase::PanoramaObserver, public AppBase::ProgressDisplay --- hugin-2019.0.0~beta1+dfsg.orig/src/tools/pano_modify.cpp +++ hugin-2019.0.0~beta1+dfsg/src/tools/pano_modify.cpp @@ -787,7 +787,7 @@ int main(int argc, char* argv[]) std::cout << "Setting verdandi arguments to " << blenderArgs << std::endl; break; default: - std::cout << "Unknow blender in pto file." << std::endl; + std::cout << "Unknown blender in pto file." << std::endl; break; }; pano.setOptions(opt); --- hugin-2019.0.0~beta1+dfsg.orig/src/tools/pto_lensstack.cpp +++ hugin-2019.0.0~beta1+dfsg/src/tools/pto_lensstack.cpp @@ -305,7 +305,7 @@ int main(int argc, char* argv[]) else { std::cout << "Warning: Pto project contains only one lens." << std::endl - << " Therefor the lens can not be changed. Use --new-lens instead." << std::endl; + << " Therefore the lens can not be changed. Use --new-lens instead." << std::endl; }; };
