Menu
▾
▴
[E] /hg/p/enblend/code: Bring spelling in Enblend and Enfuse user gu...
|
From: Enblend <enb...@li...> - 2016-10-07 14:40:19
|
branch: details: http://enblend.hg.sourceforge.net/hgweb/enblend/enblend/hg/p/enblend/code/rev/8e2a8b3cbf12 changeset: 1476:8e2a8b3cbf12 user: Chris <cs...@us...> date: Fri Oct 07 16:16:18 2016 +0200 description: Bring spelling in Enblend and Enfuse user guides in line with usual terms that are used in manual pages. diffstat: VERSION | 2 +- doc/common-advanced-options.tex | 18 ++++++------ doc/common-color-spaces.tex | 34 +++++++++++----------- doc/common-common-options.tex | 14 ++++---- doc/common-expert-options.tex | 13 ++++---- doc/common-helpful-programs.tex | 10 +++--- doc/common-information-options.tex | 2 +- doc/common-interaction.tex | 22 +++++++------- doc/common-known-limitations.tex | 24 ++++++++------- doc/common-layer-selection.tex | 26 ++++++++-------- doc/common-mask-template-characters.tex | 2 +- doc/common-notation.tex | 8 ++-- doc/common-option-delimiters.tex | 4 +- doc/common-response-files.tex | 7 ++-- doc/common-standard-workflow.tex | 4 +- doc/common-understanding-masks.tex | 5 +-- doc/enblend-expert-mask-generation-options.tex | 6 ++-- doc/enblend-flow-charts.tex | 2 +- doc/enblend-image-requirements.tex | 6 ++-- doc/enblend-mask-generation-options.tex | 6 ++-- doc/enblend-overview.tex | 4 ++- doc/enblend-seam-generators.tex | 8 ++-- doc/enfuse-applications.tex | 14 ++++---- doc/enfuse-expert-fusion-options.tex | 19 ++++++------ doc/enfuse-exposure-weighting-user-dynamic.tex | 39 +++++++++++++------------ doc/enfuse-exposure-weighting-user-opencl.tex | 6 ++-- doc/enfuse-exposure-weighting.tex | 2 +- doc/enfuse-image-requirements.tex | 6 ++-- doc/enfuse-local-contrast-weighting.tex | 12 ++++---- doc/enfuse-weighting-functions.tex | 12 ++++---- doc/index-use.tex | 6 ++-- doc/lead-in.tex | 6 ++-- doc/macros.tex | 2 +- 33 files changed, 176 insertions(+), 175 deletions(-) diffs (truncated from 1120 to 500 lines): diff -r 88d1f7a3b72b -r 8e2a8b3cbf12 VERSION --- a/VERSION Wed Oct 05 10:17:59 2016 +0200 +++ b/VERSION Fri Oct 07 16:16:18 2016 +0200 @@ -1,1 +1,1 @@ -4.3-1a152da734bb +4.3-88d1f7a3b72b diff -r 88d1f7a3b72b -r 8e2a8b3cbf12 doc/common-advanced-options.tex --- a/doc/common-advanced-options.tex Wed Oct 05 10:17:59 2016 +0200 +++ b/doc/common-advanced-options.tex Fri Oct 07 16:16:18 2016 +0200 @@ -7,8 +7,8 @@ \genidx{options!advanced}% Advanced Options\commonpart} -Advanced options control e.g.\ the channel depth, color model, and the cropping of the output -image. +Advanced options control for example the channel depth, color model, and the cropping of the +output image. \begin{codelist} \label{opt:blend-colorspace}% @@ -19,7 +19,7 @@ \item[--blend-colorspace=\metavar{COLORSPACE}]\itemend Force blending in selected \metavar{COLORSPACE}. Given well matched images this option should not change the output image much. However, if \App{} must blend vastly different colors (as - e.g.\ anti-colors) the resulting image heavily depends on the \metavar{COLORSPACE}. + for example anti-colors) the resulting image heavily depends on the \metavar{COLORSPACE}. Usually, \App{} chooses defaults depending on the input images: @@ -223,16 +223,16 @@ \gensee{associated alpha channel}{alpha channel, associated}% \gensee{unassociated alpha channel}{alpha channel, associated}% \item[-g] - Save alpha channel as ``associated''. See the + Save alpha channel as ``associated''. See the \uref{\awaresystemsbeextrasamples}{\acronym{TIFF} documentation} for an explanation. \appidx{Gimp}% \appidx{Cinepaint}% \application{The Gimp} before version~2.0 and \application{CinePaint} (see - \appendixName~\fullref{sec:helpful-programs}) exhibit unusual behavior when loading images - with unassociated alpha channels. Use option~\option{-g} to work around this problem. With - this flag \App{} will create the output image with the ``associated alpha tag'' set, even - though the image is really unassociated alpha. + \appendixName~\fullref{sec:helpful-programs}) exhibit problems when loading images with + unassociated alpha channels. Use option~\option{-g} to work around. With this flag \App{} + will create the output image with the ``associated alpha tag'' set, even though the image is + really unassociated alpha. \label{opt:output-mask}% @@ -249,7 +249,7 @@ and nevertheless the final mask is desired after \appisdoing. The output file itself always remains unaffected of this option. In particular it gets its - alpha channel, i.e.\ its mask, whenever the output-file format supports one. To mimick + alpha channel, this is its mask, whenever the output-file format supports one. To mimick option~\option{--output-mask} with such formats, use for example \begin{literal} diff -r 88d1f7a3b72b -r 8e2a8b3cbf12 doc/common-color-spaces.tex --- a/doc/common-color-spaces.tex Wed Oct 05 10:17:59 2016 +0200 +++ b/doc/common-color-spaces.tex Fri Oct 07 16:16:18 2016 +0200 @@ -64,7 +64,7 @@ L = t L_1 + (1 - t) L_2 \quad \mbox{with} \quad 0 \leq t \leq 1, \end{equation} where the luminances~$L_i, i = 1, 2,$ range from zero to their data-type dependent maximum -value~$L_{\mathrm{max}}$, thereby defining a ``luminance interval''. We can always map this +value~$L_{\mathrm{max}}$, thereby defining a ``luminance interval''. We can always map this interval to $(0, 1)$ by dividing the luminances by the maximum, which is why we call the latter \emph{``normalized luminance interval''}: \begin{equation}\label{equ:luminance-normalization} @@ -169,7 +169,7 @@ \end{equation} \noindent which is undone by the inverse transform after blending. Here, $\log(x)$ with a -lower-case initial denotes the natural logarithmic function (i.e.\ to base~$e$). +lowercase initial denotes the natural logarithmic function this is to base~$e$. \figureName~\ref{fig:log-transform} shows the forward transform in the range from $-20$ to~100. Around $L = 0$ function~$\mbox{Log}(L)$ has the series expansion \[ @@ -190,7 +190,7 @@ \begin{itemize} \item - During blending, even completely non-negative images can result in negative pixels. A + During blending, even completely nonnegative images can result in negative pixels. A \LogTransform-transform followed by the inverse guarantees all-positive output. \item @@ -246,7 +246,7 @@ \gensee{sRGB@\acronym{sRGB} color cube}{color cube, \acronym{sRGB}}% In Case~\ref{enum:no-profile}.\ the applications blend grayscale images in the normalized luminance interval and color images inside the \acronym{sRGB}-cube. To override the default -\acronym{sRGB}-profile select the desired profile with +\acronym{sRGB}~profile select the desired profile with option~\flexipageref{\option{--fallback\hyp profile}}{opt:fallback-profile}. In Case~\ref{enum:same-profile}.\ the images first are by default transformed to @@ -282,11 +282,11 @@ for grayscale images and inside the \acronym{RGB}-color cube as given in \eqnref{equ:trivial-rgb-blend}. - This is the fastest color space to do computations within, i.e.\ it consumes by far the least - computing power, because no transform to or from any of the perceptually uniform color spaces - is done. Moreover, this blend-colorspace exhibits no color artifacts even in high contrast - scenes, which is good when fusing. However, it may come up with out-of-whack blended colors, - which is bad when blending. + This is the fastest color space to do computations within, this is it consumes by far the + least computing power, because no transform to or from any of the perceptually uniform color + spaces is done. Moreover, this blend-colorspace exhibits no color artifacts even in high + contrast scenes, which is good when fusing. However, it may come up with out-of-whack blended + colors, which is undesirable when blending. \genidx{colorspace!\acronym{L*a*b*}}% \gensee{L*a*b*@\acronym{L*a*b*} colorspace}{colorspace, \acronym{L*a*b*}}% @@ -299,9 +299,9 @@ approximates human vision, and is perceptually uniform. \App{} uses perceptual rendering intent throughout and either the input profile's white-point - or, if the \acronym{ICC}-profile lacks the \code{cms\shyp Sig\shyp Media\shyp White\shyp - Point\shyp Tag}, falls back to the \acronym{D50} white-point (see, - e.g.\ \uref{\wikipediastandardilluminant}{Standard illuminant}). + or, if the \acronym{ICC} profile lacks the \code{cms\shyp Sig\shyp Media\shyp White\shyp + Point\shyp Tag}, falls back to the \acronym{D50} white-point (see for example + \uref{\wikipediastandardilluminant}{Standard illuminant}). The conversions from and to \acronym{L*a*b*} are moderately fast to compute; \acronym{L*a*b*} mode is two to three times slower than working within the \acronym{RGB}-color cube. It @@ -343,9 +343,9 @@ \end{geeknote} The transformations to \acronym{CIECAM02} color space and back use perceptual rendering - intent, the \acronym{D50} white point (see, e.g.\ \uref{\wikipediastandardilluminant}{Standard - illuminant}), 500\dmn{lumen} surrounding light (``average'' in \acronym{CIECAM02} parlance), - and assume complete adaption. + intent, the \acronym{D50} white point (see for example + \uref{\wikipediastandardilluminant}{Standard illuminant}), 500\dmn{lumen} surrounding light + (``average'' in \acronym{CIECAM02} parlance), and assume complete adaption. Both \acronym{CIELUV} and \acronym{CIELAB} only model the color information generated for small and isolated color samples. They cannot model the contextual effects of color @@ -357,7 +357,7 @@ appreciable number of pixels need additional refinement steps the speed of the transformation further drops. Expect \acronym{CIECAM02} mode to be 8--800 times slower than blending within the \acronym{RGB}-color cube. It operates the \acronym{LittleCMS} color-space conversion - engine in \uref{\littlecmscomunboundedcmm}{unbounded} mode, however it tries very hard to + engine in \uref{\littlecmscomunboundedcmm}{unbounded} mode. However, it tries very hard to recover the visually best-matching color for each pixel thus gone rogue. \end{description} @@ -421,7 +421,7 @@ \fi% enfuse \item - Prefer linear (i.e.\ $\mathrm{gamma} = 1$) color profiles in the input images, when the + Prefer linear, this is $\mathrm{gamma} = 1$, color profiles in the input images, when the contrast of the scene is high. To avoid banding it is advisable to use at that least 16~bits per color channel with linear color profiles. diff -r 88d1f7a3b72b -r 8e2a8b3cbf12 doc/common-common-options.tex --- a/doc/common-common-options.tex Wed Oct 05 10:17:59 2016 +0200 +++ b/doc/common-common-options.tex Fri Oct 07 16:16:18 2016 +0200 @@ -80,7 +80,7 @@ \item[Any other format.]\itemend Other formats do not accept a \metavar{COMPRESSION} setting. However, the underlying \uref{\hciiwrvigra}{\acronym{VIGRA}} library automatically compresses \filename{png}-files - with the \propername{Deflate} method. (\acronym{VIGRA} is the image manipulation library + with the \propername{Deflate} algorithm. (\acronym{VIGRA} is the image manipulation library upon which \App{} is based.) \end{description} @@ -174,15 +174,15 @@ image to be redirected or piped. \begin{geeknote} - We refrain from utilizing the \acronym{TIFF} as fallback output file type, because some of - the libraries which implement \acronym{TIFF} ``seek'' the output image file. Technically, - this means they call fseek(3) or related functions, which would preclude, for example, - \filename{/dev/stdout} to be used as \metavar{FILE}. + \App{} refrains from utilizing the \acronym{TIFF} as fallback output file type, because some + of the libraries which implement \acronym{TIFF} ``seek'' the output image file. + Technically, this means they call fseek(3) or related functions, which would preclude, for + example, \filename{/dev/stdout} to be used as \metavar{FILE}. The \uref{\hciiwrvigra}{\acronym{VIGRA}} implementation of \val{val:default-fallback-output-file-type} does not seek. Moreover, it is completely implemented inside of \acronym{VIGRA}, without referring to another library. The format - supports 8, 16, and 32~bits per channel, gray-scale and color images. The lack of alpha + supports 8, 16, and 32~bits per channel, grayscale and color images. The lack of alpha channels can easily be compensated by adding option~\flexipageref{\option{--output-mask}}{opt:output-mask} to the \appcmd{}~command line. \end{geeknote} @@ -211,7 +211,7 @@ Without an argument, increase the verbosity of progress reporting. Giving more \option{--verbose}~options will make \App{} more verbose; see \sectionName~\fullref{sec:finding-out-details} for an exemplary output. Directly set a - verbosity level with a non-negative integral~\metavar{LEVEL}. + verbosity level with a nonnegative integral~\metavar{LEVEL}. \tableName~\ref{tab:verbosity-levels} shows the messages available at a particular \metavar{LEVEL}. diff -r 88d1f7a3b72b -r 8e2a8b3cbf12 doc/common-expert-options.tex --- a/doc/common-expert-options.tex Wed Oct 05 10:17:59 2016 +0200 +++ b/doc/common-expert-options.tex Fri Oct 07 16:16:18 2016 +0200 @@ -32,7 +32,7 @@ \genidx{RGB-cube@\acronym{RGB}-cube}% \item[--fallback-profile=\metavar{PROFILE-FILENAME}]\itemend Use the \acronym{ICC} profile in \metavar{PROFILE-FILENAME} instead of the default - \acronym{sRGB}. This option only is effective if the input images come \emph{without} color + \acronym{sRGB}. This option only is effective if the input images come \emph{without} color profiles \emph{and} blending is not performed in the trivial luminance interval or \acronym{RGB}-cube. @@ -126,7 +126,7 @@ \sample{--no-parameter}, which takes one or more \metavar{KEY}s and removes them from the list of defined parameters. The special key~\sample{*} deletes all parameters at once. - Parameters allow the developers to change the internal workings of \App{} without the need to + Parameters enable the developers to change the internal workings of \App{} without the need to recompile or relink. \begin{sgquote} @@ -150,7 +150,7 @@ \item[\itempar{-a \\ --pre-assemble}]\itemend Pre-assemble non-overlapping images before each blending iteration. - This overrides the default behavior which is to blend the images sequentially in the order + This overrides the default procedure, which is to blend the images sequentially in the order given on the command line. \App{} will use fewer blending iterations, but it will do more work in each iteration. @@ -166,10 +166,9 @@ \genidx{OpenCL!platform}% \item[--prefer-gpu=\optional{\metavar{PLATFORM}:}\metavar{DEVICE} \restrictednote{\acronym{OpenCL}-enabled versions only.}]\itemend - Direct \App{} towards a particular \acronym{OpenCL} \metavar{DEVICE} on the first - auto-detected \metavar{PLATFORM} or directly to the given \metavar{PLAT\shyp - FORM}\slash\metavar{DE\shyp VICE} combination. Use the numbers of platform and - device found either with + Direct \App{} toward a particular \acronym{OpenCL} \metavar{DEVICE} on the first auto-detected + \metavar{PLATFORM} or directly to the given \metavar{PLAT\shyp FORM}\slash\metavar{DE\shyp + VICE} combination. Use the numbers of platform and device found either with \begin{terminal} \$ \app{} --verbose --version diff -r 88d1f7a3b72b -r 8e2a8b3cbf12 doc/common-helpful-programs.tex --- a/doc/common-helpful-programs.tex Wed Oct 05 10:17:59 2016 +0200 +++ b/doc/common-helpful-programs.tex Fri Oct 07 16:16:18 2016 +0200 @@ -202,17 +202,17 @@ \end{itemize} -\section[Meta-Data Handling]{\label{sec:meta-data-handling}% - \genidx{helpful programs!meta-data handling}% - Meta-Data Handling} +\section[Metadata Handling]{\label{sec:metadata-handling}% + \genidx{helpful programs!metadata handling}% + Metadata Handling} \begin{itemize} \label{app:exiftool}% \prgidx{exiftool}% \genidx{EXIF@\acronym{EXIF}}% \item - \uref{\snophyqueensucaexiftool}{EXIFTool} reads and writes \acronym{EXIF} meta-data. In - particular it copies meta-data from one image to another. + \uref{\snophyqueensucaexiftool}{EXIFTool} reads and writes \acronym{EXIF} metadata. In + particular it copies metadata from one image to another. \label{app:littlecms}% \appidx{LittleCMS}% diff -r 88d1f7a3b72b -r 8e2a8b3cbf12 doc/common-information-options.tex --- a/doc/common-information-options.tex Wed Oct 05 10:17:59 2016 +0200 +++ b/doc/common-information-options.tex Fri Oct 07 16:16:18 2016 +0200 @@ -115,7 +115,7 @@ \optidx[\defininglocation]{--show-signature}% \genidx{signature}% \item[--show-signature]\itemend - Show the user name of the person who compiled the binary, when the binary was compiled, and on + Show the username of the person who compiled the binary, when the binary was compiled, and on which machine this was done. This information can be helpful to ensure the binary was created by a trustworthy builder. diff -r 88d1f7a3b72b -r 8e2a8b3cbf12 doc/common-interaction.tex --- a/doc/common-interaction.tex Wed Oct 05 10:17:59 2016 +0200 +++ b/doc/common-interaction.tex Fri Oct 07 16:16:18 2016 +0200 @@ -15,9 +15,9 @@ \genidx{detailed configuration}% Finding Out Details About \app} -An \appcmd{} binary can come in several configurations. The exact name of the binary may vary +An \appcmd{} binary can come in several configurations. The exact name of the binary may vary, and it may or may not reflect the ``kind of \app''. Therefore, \appcmd{} offers several options -that allow the user to query exactly\dots +to query exactly\dots \begin{compactitemize} \item @@ -319,11 +319,11 @@ prominent image formats. %% With the exception of TIFF, VIFF, PNG, and PNM all file types -%% store only 1 byte (gray scale and mapped RGB) or 3 bytes (RGB) +%% store only 1 byte (grayscale and mapped RGB) or 3 bytes (RGB) %% per pixel. %% %% PNG can store UInt8 and UInt16 values, and supports 1 and 3 -%% channel images. One additional alpha channel is also supported. +%% channel images. One additional alpha channel is also supported. %% %% PNM can store 1 and 3 channel images with UInt8, UInt16 and %% UInt32 values in each channel. @@ -382,7 +382,7 @@ formats themselves, not \App's. The ``Mask''-column indicates whether the format supports an image mask (alpha-channel), see also \chapterName~\ref{sec:understanding-masks}. Column~``Profile'' shows whether the - image format allows for \acronym{ICC}-profiles to be included; see also + image format allows for \acronym{ICC}~profiles to be included; see also \chapterName~\ref{sec:color-spaces}.} \end{table} @@ -527,9 +527,9 @@ \genidx{message!foreign sources}% \item[Foreign Sources:] \appcmd{} depends on various foreign software components that issue - their own messages. We try to catch them and press them in our category scheme, but some of - them invariably slip through. The most prominent members of this rogue fraction are the - notices of \uref{\hciiwrvigra}{\acronym{VIGRA}} as e.g. + their own messages. \App{} tries to catch them and press them in the category scheme, but + some of them invariably slip through. The most prominent members of this rogue fraction are + the notices of \uref{\hciiwrvigra}{\acronym{VIGRA}} as for example \begin{literal} enfuse: an exception occurred \\ @@ -615,9 +615,9 @@ \genidx{OpenMP@\acronym{OpenMP}}% \item[\envvar{OMP\_DYNAMIC}\xitemspace (implicit)\xitemspace \restrictednote{\acronym{OpenMP}-enabled versions only.}]\itemend - Control whether the \uref{\openmporg}{\acronym{OpenMP}} sub-system should parallelize nested + Control whether the \uref{\openmporg}{\acronym{OpenMP}} subsystem should parallelize nested parallel regions. This environment variable will only have an effect is the \acronym{OpenMP} - sub-system is capable of dynamic adjustment of the number of threads (see explanations in + subsystem is capable of dynamic adjustment of the number of threads (see explanations in \sectionName~\fullref{sec:compiled-in-features}). \begin{geeknote} @@ -632,7 +632,7 @@ \item[\envvar{OMP\_NUM\_THREADS}\xitemspace (implicit)\xitemspace \restrictednote{\acronym{OpenMP}-enabled versions only.}]\itemend Control -- which typically means: reduce -- the number of threads under supervision of the - \uref{\openmporg}{\acronym{OpenMP}} sub-system. By default \appcmd{} uses as many + \uref{\openmporg}{\acronym{OpenMP}} subsystem. By default \appcmd{} uses as many \acronym{OpenMP}\hyp{}threads as there are \acronym{CPU}s. Use this variable for example to free some \acronym{CPU}s for other processes than \appcmd. diff -r 88d1f7a3b72b -r 8e2a8b3cbf12 doc/common-known-limitations.tex --- a/doc/common-known-limitations.tex Wed Oct 05 10:17:59 2016 +0200 +++ b/doc/common-known-limitations.tex Fri Oct 07 16:16:18 2016 +0200 @@ -16,7 +16,7 @@ \item Total size of \emph{any} -- even intermediate -- image is limited to $2^{31}$~pixels, this is - two giga-pixels. + two gigapixels. \ifenblend \genidx{blending!sequential}% @@ -32,8 +32,8 @@ \begin{geeknote} The overlap is exclusively defined by the masks of the overlapping images. This is exactly what the input masks are built for. Let $A$ be the number of pixels that overlap in both - masks. We use $A$ as a measure of the overlap area -- something 2\hyp dimensional; - technically it is a pixel count. + masks. \App{} uses $A$ as a measure of the overlap area -- something 2\hyp dimensional; + technically a pixel count. Construct the smallest circumscribed, par-axial rectangle of the overlap area. The rectangle has a circumference @@ -42,14 +42,16 @@ \] which is of course 1-dimensional. Internally $U$ again is a number of pixels just as $A$. - The threshold when we consider a pair of images sufficiently different is when $A$ is larger - than \val{val:overlap-check-threshold}~times the number of pixels on the circumference~$U$ - \[ + The threshold for \App{} to consider a pair of images sufficiently different is if $A$ is + larger than \val{val:overlap-check-threshold}~times the number of pixels on the + circumference~$U$ + \begin{equation}\label{equ:overlap-threshold} A > \val{val:overlap-check-threshold} \times U. - \] - Avoiding the term ``fractal dimension'', we have constructed a simple measure of how 2\hyp - dimensional the overlap area is. This way we steer clear of feeding later processing stages - with nearly 1\hyp dimensional overlap regions, something that wreaks havoc on them. + \end{equation} + Avoiding the term ``fractal dimension'', \eqnref{equ:overlap-threshold} is a simple measure + of how 2\hyp dimensional the overlap area is. This way \App{} steers clear of feeding later + processing stages with nearly 1\hyp dimensional overlap regions, something that wreaks havoc + on them. \end{geeknote} \optidx{--wrap}% @@ -75,7 +77,7 @@ option~\flexipageref{\option{--blend-colorspace}}{opt:blend-colorspace}. \item - Use linear (i.e.\ $\mathrm{gamma} = 1$) color profiles in the input images. Also see + Use linear, this is $\mathrm{gamma} = 1$, color profiles in the input images. Also see \chapterName~\fullref{sec:color-spaces} on ``Color Spaces And Color Profiles''. \end{enumerate} \end{itemize} diff -r 88d1f7a3b72b -r 8e2a8b3cbf12 doc/common-layer-selection.tex --- a/doc/common-layer-selection.tex Wed Oct 05 10:17:59 2016 +0200 +++ b/doc/common-layer-selection.tex Fri Oct 07 16:16:18 2016 +0200 @@ -6,10 +6,10 @@ \genidx[\rangebeginlocation]{layer!selection}% Layer Selection\commonpart} -Some image formats, like for example \acronym{TIFF}, allow for storing more than one image in a +Some image formats, like for example \acronym{TIFF}, permit to store more than one image in a single file, where all the contained images can have different sizes, number of channels, -resolutions, compression schemes, etc. The file there acts as a container for an \emph{ordered} -set of images. +resolutions, compression schemes, and so on. The file there acts as a container for an +\emph{ordered} set of images. \genidx[\defininglocation]{file!multi-page}% \gensee{multi-page file}{file, multi-page}% @@ -38,7 +38,7 @@ To give the user the same flexibility in specifying and ordering images as with single-layer images, both \App{} and \OtherApp{} offer a special syntax to select layers in multi-page files -by appending a \metavar{layer-specification} to the image file name. +by appending a \metavar{layer-specification} to the image filename. \tableName~\ref{tab:layer-selection-grammar} defines the grammar of \metavar{layer-specification}\/s. @@ -73,7 +73,7 @@ The simplest \metavar{layer-specification} are the layer-\metavar{index}es. The first layer gets index~1, the second layer~2, and so on. Zero never is a valid index! For convenience -indexing backwards\footnotemark{} is also possible. This means by prefixing an index with a +indexing backward\footnotemark{} is also possible. This means by prefixing an index with a minus-sign~(\sample{-}) counting will start with the last layer of the \emph{associated} multi-page image, such that the last layer always has index~\code{-1}, the next to last index~\code{-2} and so on. Out-of-range indexes are silently ignored whether forward or @@ -87,7 +87,7 @@ Select a contiguous \metavar{range} of indexes with the range operator~\sample{\val{val:layer-range-separator}}, where the \metavar{range-bound}\/s are -forward or backward indices. Leaving out a bound or substituting the open-range +forward or backward indexes. Leaving out a bound or substituting the open-range indicator~\sample{\val{val:layer-range-empty-index-symbol}} means a maximal range into the respective direction. @@ -117,7 +117,7 @@ \item[\lspec{2 :\ 4 :\ 5}] Select only layers~2, 4, and~5 in this order. -\item[\lspec{2 :\ -4 :\ -3}] Like before, but with some backwards-counting indices. +\item[\lspec{2 :\ -4 :\ -3}] Like before, but with some backward-counting indexes. \item[\lspec{1 \val*{val:layer-range-separator}\ 4}] Layers 1~to 4, this is 1, 2, 3, and~4 in this order. @@ -149,9 +149,9 @@ \end{codelist} \begin{geeknote} - Shell expansion will not work anymore with a file name terminated by a layer specification - expression (or anything else), because to the shell it is not a file name anymore. Work - around with, for example, + Shell expansion will not work anymore with a filename terminated by a layer specification + expression (or anything else), because to the shell it is not a filename anymore. Work around + with, for example, \begin{terminal} \$ \app{} `for x in image-??.tif; do echo \$x[2]; done` @@ -163,7 +163,7 @@ \$ \app{} \$(ls -1 image-??.tif | sed -e 's/\$/[2]/') \end{terminal} - The order of the indices determines the order of the layers, this is, the images. An index + The order of the indexes determines the order of the layers, this is, the images. An index can occur multiple times, which causes layer to be considered \emph{again}. Consequently, this will lead to an error with \application{Enblend}, but may be desired with \application{Enfuse} in \code{soft-mask}~mode to give the image more weight by mentioning it @@ -204,8 +204,8 @@ \textrm{(ImageMagick)}}\command{display} use a \uref{\imagemagickorgcommandlineprocessinginput}{similar syntax} as \App{} to select layers (which in \application{ImageMagick} parlance are called ``frames'') in multi-page files. - Please note that \application{ImageMagick} tools start indexing at zero, whereas we start at - one. + Please note that \application{ImageMagick} tools start indexing at zero, whereas \App{} starts + counting at one. \item \App{} and \OtherApp{} by default apply the \sample{\val{val:layer-selector}} selector (see diff -r 88d1f7a3b72b -r 8e2a8b3cbf12 doc/common-mask-template-characters.tex --- a/doc/common-mask-template-characters.tex Wed Oct 05 10:17:59 2016 +0200 |