Beep6581

Ah, then would be good to label this under some "language strings" label ("l10n"?), and assign it to me, then I'll review it when doing #168

Yes, but I meant 1. to add a label to this GitHub issue to easily track all issues related to interface labels and their translations https://github.com/LuminanceHDR/LuminanceHDR/labels 1. to assign the...

@terjebyte ``` luminance-hdr-cli --verbose --save /tmp/landscape.hdr --output /tmp/landscape_tonemapped.tif --ldrTiff 16b --tmo fattal /tmp/landscape*.tif Input file /tmp/landscape_1.tif Input file /tmp/landscape_2.tif Input file /tmp/landscape_3.tif Running in HDR-creation mode. Temporary directory: /tmp Using...

@fcomida I would argue that any standard would be better than no standard, so yes, a proper CSV would be better. When reading a CSV, LibreOffice could then also understand...

I still do not see the extension in f7edae38, see issue #226.

See https://discuss.pixls.us/t/high-bit-depth-tiff-compatability-issues/3725/11

The preview quality is still low in 2.5.0.  

@fcomida looks like the Qt way of doing this is by enabling the "Aliasing" render hint. http://doc.qt.io/qt-5/qpainter.html#RenderHint-enum This could also help: http://stackoverflow.com/questions/17734290/antialiasing-not-working-in-qgraphicsview

@fcomida great! While it's compiling, I wanted to point out that: > QPainter::HighQualityAntialiasing 0x08 This value is obsolete and will be ignored, use the Antialiasing render hint instead.

* Downscaling test * Without patch:  * With patch:  * Upscaling test * Without patch:  * With patch: ...