Carl,
The weird, bright pixels in dark areas are artifacts of the
LCMS color-conversions in so called open color spaces. Experience has
shown that it is hard to catch all of them. However, Enblend/Enfuse
have a lot of (undocumented) command-line parameters that control the
hedging of
Fixed in rev 1c815a028afc.
** Changed in: enblend
Status: New => Fix Committed
** Changed in: enblend
Importance: Undecided => Low
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
--
You received this bug notification because you are a member
I stand corrected. Thanks go to Thomas for poining out
what I ignored!
The documentation was corrected accordingly in
rev f0304648cc0f. See
http://hg.code.sf.net/p/enblend/code/rev/f0304648cc0f
The crucial change is the restriction in the sentence
"Enblend and Enfuse simply copy the pixels
Thanks for reviewing the patch!
Just to demonstrate the power of the multi-level blending:
Again set mu=0 and _reduce_ the number of blend levels with
option `--levels'. You'll find your masked tree sticking
out of the darkness much more prominently. By default
both Enblend and Enfuse maximize
> Perhaps this adaptation mechanism at the border ceases
> to work when the exposure is too far off. There might
> even be a built-in limit to prevent side-effects like
> increased noise.
Neither is there an `adaptation mechanism' nor a `built-in limit'.
What you see is just the Mertens/Kautz/van
want a
different mu, choose as un-masked image the one that best matches your
desired mu.
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
** Changed in: enblend
Status: New => Triaged
--
You received this bug notification because you are a member
** Changed in: enblend
Status: New => Won't Fix
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1647215
Title:
Problems building current default
Status in Enblend:
Won't Fix
Bug
The Autoconf/Automake and the CMake generated Makefiles both
build the documentation up to and including the PostScript
targets by default. We intentionally avoid PDF for the
default target -- obviously for good reasons.
If packagers trigger the PDF targets it is their problem.
I'm inclined to
WOMS. Probably your LaTeX build chain is different.
I have just checked my local Enblend/Enfuse repo
on a Debian system and it builds the complete
documentation.
My prime suspect would be your "epstopdf.pl"
or any driver program that fires it up. The
docu build process is quite complicated.
> When running enblend with --visualize and path debugging, the program
> crashes. The effect is stat output suddenly stops, ...
It is possible that `--parameter=debug-path' does not jibe
well with OMP. (Any `--parameter' lets you rummage in the guts of
Enblend or Enfuse.) Try a non-OMP
The warning is benign. It is not related to the size of a panorama,
but to the location of the tentative seam-line after
Simulated Annealing.
Use `--visualize' to check if there is a connection between the
seam line and the supposed artifacts. For a more detailed look
at the optimizer's job try
** Changed in: enblend
Assignee: (unassigned) => Mikolaj Leszczynski (rosomack)
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1598583
Title:
Missing image parts with graphcut seam
Commit a1fbf734e58a by Thomas gets the CMake system
in lockstep with Autoconf/Automake again. WOMS.
@Terry: THX for venturing out so far.
** Changed in: enblend
Status: New => Fix Committed
** Changed in: enblend
Importance: Undecided => High
--
You received this bug notification
Only the Autoconf/Automake side of configuration is supposed to work right now.
http://hg.code.sf.net/p/enblend/code/rev/062ef888f4cf
If you happened to configure with CMake the breakage is expected.
Surely Thomas will adjust the CMake side as always.
--
You received this bug notification
If using option `--no-ciecam' or future-proof option
`--blend-colorspace=identity' fixes the problem this
report is a duplicate of #752283.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1576862
Probably fixed in rev 1f276a9e5840.
** Changed in: enblend
Status: New => Fix Committed
** Changed in: enblend
Importance: Undecided => Low
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
Should be fixed in rev 78a09bc743b7, which will be backported to 4.2.1.
Given the complexity and sheer mass of checks for the documentation,
I expect more bugs to show up time after time.
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
** Changed in: enbl
Fixed in 4.2.
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1469004
Title:
Problems building 4.2 docs
Status in Enblend:
Fixed in 4.2.
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1475448
Title:
DVI output fails on SMP build
Status in
Fixed in 4.1.4. Version 4.2 does not use Texinfo,
so the problem does not occur.
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
Fixed in 4.2.
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/746653
Title:
FR: 2 Mu parameters instead of 1 (enfuse)
Fixed in 4.1.4 and 4.2.
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1332323
Title:
Fix issues reported by valgrind
Fixed in 4.2.
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1256621
Title:
compilation fails since introduction of timer
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1468524
Title:
convert -3 error building docs
Status in Enblend:
Fix
Fixed in 4.2.
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1356551
Title:
White pixels at 180 wrap and zenith for
Fixed in 4.2.
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1374686
Title:
Enblend adds black to edges of some pictures
Fixed in 4.2.
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1157155
Title:
enblend 4.1 generates brighter images than
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/685105
Title:
enblend fails to blend large pano
Status in Enblend:
Fix
Released version 4.1 Patchlevel 5:
http://hg.code.sf.net/p/enblend/code/file/f8a34cfab8c1/NEWS
** Changed in: enblend
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
Wrt to #5: No gcc-6 here, so dunno. Andreas would have hollered,
though.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1537368
Title:
enblend 4.1.4 build-error with gcc-6
Status in Enblend:
Broken compilation with gcc-6 as reported in #2 should
be fixed in rev 73e6f16de80a.
Dropped the dependency on `boost::assign' at the offending position;
it did not buy us that much anyhow.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed
** Changed in: enblend
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1537368
Title:
enblend 4.1.4 build-error with gcc-6
Status in Enblend:
In
** Changed in: enblend
Status: New => In Progress
** Changed in: enblend
Importance: Undecided => Medium
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin
Develope
Fixed in rev 467a73754dbb.
I had to open up `Patchlevel 5', which is _unreleased_ and which will
remain open for a while in case gcc-6 finds more problems. That
way you can carry on testing/porting.
> This does not apply to HG default!
The offending source does not exist in the current tip of
was replaced with
pure LaTeX.
** Changed in: enblend
Status: Triaged = Fix Committed
** Changed in: enblend
Assignee: (unassigned) = Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https
Fixed in ef895497dff3.
** Changed in: enblend
Status: New = Fix Committed
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1475448
Title:
DVI output fails on SMP build
Status in
I'll postpone the patch #5 indefinitely and
put this issue into state won't fix. The less
we molest Automake the better.
@Bruno: Please reopen and apply a fix à ton goût if
you have a brilliant idea.
** Changed in: enblend
Status: Incomplete = Won't Fix
--
You received this bug
I understand that `make dist' fails. As automake(1) sets up our Makefiles
it _must_ fail after a `make clean'.
Check whether the patch in #5 fixes the problem. If it does I still would
be hesitant to apply it until we get the blessings from some of the
Autoconf/Automake demi-gods.
--
You
Patch rename-share-gnumakefile.diff went into rev 8f3ccaa707e6:
http://hg.code.sf.net/p/enblend/code/rev/8f3ccaa707e6
So this part is patch applied.
I set the issue's status to incomplete until you find out whether
the `dist'-target depends on `all'. See comment #3.
** Changed in: enblend
Actually, #2 is a new and different problem. We do want to support
in-place builds, but make(1) is just overzealous and [ab]uses
GNUmakefile in share/enfuse, which is to be shipped for the
convenience of our users, not for building any part of the
Enblend/Enfuse project. The attached patch
** Patch added: rename-share-gnumakefile.diff
https://bugs.launchpad.net/enblend/+bug/1468520/+attachment/4421969/+files/rename-share-gnumakefile.diff
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
** Patch added: override-dist-target-dependence.diff
https://bugs.launchpad.net/enblend/+bug/1468520/+attachment/4421970/+files/override-dist-target-dependence.diff
** Changed in: enblend
Status: New = Confirmed
--
You received this bug notification because you are a member of Hugin
(GNU automake) 1.14.1
$ autoconf --version
autoconf (GNU Autoconf) 2.69
** Changed in: enblend
Importance: Undecided = Medium
** Changed in: enblend
Assignee: (unassigned) = Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin
Assignee: (unassigned) = Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1468524
Title:
convert -3 error building docs
Status in Enblend:
Fix Committed
Bug description
Thanks Terry for reporting the problem. It is reproducible. The
source of the problems isn't the masks though, it is the topology of the
resulting input images (to Enblend). Sure, exactly the mask-feature
makes creating such a topology so easy.
Requesting the seam-line visualizations
** Changed in: enblend
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1384674
Title:
enblend running out of temp space: poor diagnostics and
: Undecided = Medium
** Changed in: enblend
Assignee: (unassigned) = Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1374686
Title:
Enblend adds black to edges
Importance: Undecided = Medium
** Changed in: enblend
Assignee: (unassigned) = Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1384674
Title:
enblend running out of temp
The ImageCache causing the problem was withdrawn in the
Development Branch, which finally leads to version 4.2. So the
bug is gone there, because the code that caused it was removed.
We have a tentative replacement for the ImageCache in
the mmap_view branch:
The environment variable `TMPDIR' controls the placement of temporary files
as documented in section Tuning Memory Usage of the Enblend and Enfuse
manuals.
The actual, assigned directory for the ImageCache can easily be inquired by
calling Enblend or Enfuse with the option pair `--verbose
** Changed in: enblend
Status: New = Won't Fix
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1372700
Title:
Blending error
Status in Enblend:
Won't Fix
Bug description:
Using
Brief answer: `-a'
Less brief answer: (0, 4, 3, 1, 2)
Readable answer:
In the canonical order, the first pair of images already does
*not* overlap and Enblend issues a (deserved) warning. Re-order the
images e.g. as (0, 4, 3, 1, 2) or stick with the canonical order and
pass the pre-assemble
Rosomack reviewed the proposed patches and found them ok.
Changes applied in revs 255771c2e58b
http://hg.code.sf.net/p/enblend/code/rev/255771c2e58
and 95c7e90f2be8
http://hg.code.sf.net/p/enblend/code/rev/95c7e90f2be8
** Changed in: enblend
Status: In Progress = Fix Committed
Fixed in rev 3e1c4bc71018.
** Changed in: enblend
Status: Incomplete = Fix Committed
** Changed in: enblend
Importance: Undecided = Low
** Changed in: enblend
Assignee: (unassigned) = Christoph Spiel (cspiel)
--
You received this bug notification because you are a member
In a test with a six image project, where the input images were
generated by the current tip of Darktable and given a ProPhoto
ICC profile no warnings show up with Enblend (also current tip of
Dev Branch).
** Changed in: enblend
Status: New = Incomplete
--
You received this bug
Meanwhile I think I know what the problem is. My solution, however, would
break a considerable amount of Enblend code. Therefore, I'll pass on the
issue to another developer. Hopefully he will come up with a less sizable
patch.
--
You received this bug notification because you are a member of
This might be surprising.
FYI, Enblend and Enfuse don't simply compare
the profiles' ASCII names, but judge profile equality by
comparison of the whole profile as returned by
vigra::ImageImportInfo::getICCProfile()
We don't dig deeper into any difference than just throwing the
warning you
THX for the concise example. I can reproduce the bug on my machines.
** Changed in: enblend
Status: New = In Progress
** Changed in: enblend
Importance: Undecided = Medium
** Changed in: enblend
Assignee: (unassigned) = Christoph Spiel (cspiel)
--
You received this bug
We'd need a set of input images for Enblend that clearly reproduce
the problem preferably with the tip of the development branch.
Otherwise we waste our time with guesswork.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
Committed #0001 in
http://hg.code.sf.net/p/enblend/code/rev/18a9c1d411ac.
** Changed in: enblend
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
of them to the stable branch.
** Changed in: enblend
Status: New = In Progress
** Changed in: enblend
Importance: Undecided = Low
** Changed in: enblend
Assignee: (unassigned) = Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin
** Changed in: enblend
Importance: Undecided = Wishlist
** Changed in: enblend
Status: New = Triaged
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1316967
Title:
Maximum TIFF file
This is not an Enblend (or Enfuse)
problem. Both applications rely on the Vigra
library for I/O of images of _any_ format, i.e.
the functions described in
https://ukoethe.github.io/vigra/doc/vigra/group__VigraImpex.html
This is in fact one of the main reasons to use
an imaging library as
** Changed in: enblend
Status: New = Won't Fix
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1305794
Title:
OpenCL enabled build fails
Status in Enblend:
Won't Fix
Bug description:
Technically, your Boost headers (and libraries) are too old.
So, this is not an Enblend/Enfuse problem.
I have just committed a patch that requires at least
Boost version 1.55 to build Enblend and Enfuse.
** Changed in: enblend
Status: Fix Committed = Won't Fix
--
You received this bug
WRT your original errors. They point to outdated OpenCL header files.
Ask your sysadmin to get the most recent versions from
http://www.khronos.org/opencl/
and install them in the appropriate place.
Next thing on her agenda is to update the OpenCL libraries to their
latest versions. Again,
@Frederic: Thanks for investigation the problem!
From revision 502d69450811 Enblend and Enfuse require
at least Little CMS version 2.5. We hope to backport the patch
to the stable series soon.
** Changed in: enblend
Status: Incomplete = Fix Committed
** Changed in: enblend
Lukas,
THX for your minimal example! Admittedly, I cannot
reproduce your foo.tif with rev 6d6c88dcdc63, i.e.
current tip. I tried any image order, NFT, GC, w/optimizer,
and wo/optimizer. The result _always_ looked ok and
never showed any black areas. Moreover the seam line
(`--visualize')
@Lukas: (i) GraphCut is absolutely unchanged in 6d6c88dc,
(ii) after its recent re-implementation it is again WIP
according to its author.
Please run with NFT only to see whether this fundamental
step now works any better. BTW, GraphCut uses NFT as an
educated guess.
If you have a reasonably
** Changed in: enblend
Status: New = Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/685875
Title:
severe ghosting in cloud row
Status in Enblend:
Incomplete
Bug
Check out rev 6d6c88dcdc63 or later. Keep optimization
switched off and -- at your discretion GraphCut -- to get
reliable results.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/785803
Title:
Check out rev 6d6c88dcdc63 or later. Switch off optimization
and -- at your discretion GraphCut -- to get reliable results.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/721136
Title:
** Changed in: enblend
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/785803
Title:
Enblend --no-optimize produces black holes into panoramas
Status in
Please add your (pair of) input images to this issue report
such that we can test with the latest revision of Enblend.
** Changed in: enblend
Status: New = Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
** Changed in: enblend
Status: New = Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/989908
Title:
black lines from graph-cut seam generator
Status in Enblend:
Incomplete
** Changed in: enblend
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/685105
Title:
enblend fails to blend large pano
Status in Enblend:
Fix
THX keafert for trying out Enblend on large panos. You have
convinced me that we can close this issue, because enblend
fails to blend large pano is not a bug in the program. You
proved that it is plain user incompetence, using wanna-be O/Ss,
or, in summary nothing we can fix.
The sizes of more
THX kaefert for trying out Enblend on large panos. You have
convinced me that we can close this issue, because enblend
fails to blend large pano is not a bug in the program. You
proved that it is plain user incompetence, using wanna-be O/Ss,
or, in summary nothing we can fix.
The sizes of more
** Changed in: enblend
Assignee: (unassigned) = Mikolaj Leszczynski (rosomack)
** Changed in: enblend
Status: New = In Progress
** Changed in: enblend
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Hugin
Developers, which is
Fixed in 4.1.2.
** Changed in: enblend
Status: New = Fix Released
** Changed in: enblend
Importance: Undecided = Medium
** Changed in: enblend
Assignee: (unassigned) = Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin
Developers
There you go: fixed in 4.1.2, i.e. rev ac3dd60b8c45.
** Changed in: enblend
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1214004
Title:
Enfuse
** Changed in: enblend
Importance: Undecided = Medium
** Changed in: enblend
Assignee: (unassigned) = Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1214004
Title
(1) You could re-run Enfuse with a higher verbosity setting.
See the Enfuse manual for a description of the levels.
(2) You could re-run Enfuse under the supervision of a debugger.
Keep your fingers crossed that your binary contains (enough)
debugging symbols.
This should give us more
Oops! Sorry, I was off-by-one in the
exponent. 8-/ The largest _signed_ integer
(`int') typically is 2**31 - 1, not 2**32 - 1.
The latter is correct for _unsigned_ integers
(`unsigned int'). However, your calculation
still holds even with the half-as-large limit.
Another thing that would be
Try tip of development branch.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1228601
Title:
Emblend Error Minimizer1D
Status in Enblend:
New
Bug description:
enblend: an exception
Read your own log file and you find Enblend's comment:
enblend: warning: only one input image given.
enblend: warning: Enblend needs two or more overlapping input images in
order to do
enblend: warning: blending calculations. The output will be the same as
the input.
which is
You ran out of disk space. Perhaps the partion where
/tmp gets mounted is small.
The particular version of Enblend you are using (ImageCache)
is best for systems with little memory, but lots of free disk space.
Prefer the version without ImageCache to benefit from lots of RAM.
** Changed in:
We can't smell error messages. You must show them to us in the Bug
Description.
** Changed in: enblend
Status: New = Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1214004
** Changed in: enblend
Status: New = Fix Committed
** Changed in: enblend
Importance: Undecided = Medium
** Changed in: enblend
Assignee: (unassigned) = Kornel (kornel-benko)
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed
OK -- a few words from your chief
maintainer of Enblend/Enfuse.
1. ImageCache
Any ImageCache support has been removed
from the development branches of Enblend and
Enfuse. It won't come back unless some brave,
brilliant, ... hacker steps up and takes
responsibility for the code. Thus,
Martha, my dear -
You are right, I cannot reproduce the problem here on any
of my (Debian/SuSE) Linux boxes.
If EXR is your only problem, I can suggest to you that you switch to
16-bit TIFF, 16-bit PNG, or 32-bit floating-point TIFF. EXR's `half'
float suffers from a short significant
You can just bump the version forward.
Please adjust configure.in accordingly.
Patch is candidate for 4.1.2.
** Changed in: enblend
Status: New = Triaged
** Changed in: enblend
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Hugin
THX for tracking down the problems in detail.
#1: Patch in my local repo; probably will be applied.
#2: Screwing up the output is not the way to go. We can
prevent unwanted whitespace from occurring by terminating
the relevant lines with `@c', though:
@classictimes{}@c
THX for feeding the doc into Texinfo-5.1 again.
I'm still on makeinfo-4.13, so I cannot check myself yet.
Thus, the problem will remain unless someone sends us a patch.
On a medium time-scale I'm inclined to switch to plain LaTeX
and drop Texinfo. The vast majority of users doesn't read the
Can we set the status to Won't Fix or better Invalid?
This looks like an Automake/Autoconf problem.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1155350
Title:
build with texinfo 5.1
Status
** Changed in: enblend
Status: New = Triaged
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1155350
Title:
build with texinfo 5.1
Status in Enblend:
Triaged
Bug description:
The
The patch is nonsense because all Makefile.ins
are re-generated by every run of configure(1).
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1155350
Title:
build with texinfo 5.1
Status in
Please work on the _tips_ of either the development branch
(currently: http://hg.code.sf.net/p/enblend/code/rev/b0b27f8c7de1)
or the stable branch (currently:
http://hg.code.sf.net/p/enblend/code/rev/881360218998),
for your version is
(i) ancient, i.e. we won't fix anything there anyhow and
(ii)
... choosing nft doesn't make a difference
with respect to my problem
You are using a pre-release of Enblend
version 4.1. Therefore, your default PSG is
NFT, I'm on the development tip and GC is the
default here, thus I had to force NFT and you
found no differences. Makes sense.
** Attachment added: Enblend output image
https://bugs.launchpad.net/enblend/+bug/1153546/+attachment/3568485/+files/a.tif
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1153546
Title:
1 - 100 of 142 matches
Mail list logo
