On Tue, 2014-05-20 at 10:59 -0300, Joao S. O. Bueno wrote:
[...]
I pǘe been talking with some heavy users (for professional use, even) -
and one thing they miss is more consistency on asst handling
(you can rename a palette or a gradient inline in the gradient list
dialog, but not a pattern or
I agree with the file-format,
ad I don't think keeping the i18n's in file is a bad thing to do.
The idea of having a file as a pill containing all the translations,
and such seens much
more tasty than having to distribute separated i18n resources when
I publish, say, a color palette on my blog.
On 02/10/2014 03:01 PM, Joao S. O. Bueno wrote:
I agree with the file-format,
ad I don't think keeping the i18n's in file is a bad thing to do.
The idea of having a file as a pill containing all the translations,
and such seens much
more tasty than having to distribute separated i18n resources
On Tue, Feb 11, 2014 at 1:25 AM, Ofnuts wrote:
On 02/10/2014 03:01 PM, Joao S. O. Bueno wrote:
I agree with the file-format,
ad I don't think keeping the i18n's in file is a bad thing to do.
The idea of having a file as a pill containing all the translations,
and such seens much
more tasty
Hi,
I'm curious if we have a plan for assets in v2.10 and onwards now that
16/32 bit is possible. Color palettes and gradients are still based on
raw 8bit RGB values, and pattern files are 8bit as well.
FilmGIMP/Cinepaint fixed that in the past by converting everything
to 16bit integer (afaik,
