> -Original Message-
> From: Jehan Pag?s
> Yes but the question still remains: if you want to share a XCF, this
> is usually for team working (or similar reasons involving others
> wanting to edit your work). Then if you used a new feature, how do you
> pass your work to someone with
PM
To: gimp-user-list@gnome.org
Subject: Re: [Gimp-user] opening 2.9.3 file in 2.8.14 (NOT)
Perhaps I may add a perspective, please.
Using LibreOffice, one of the major benefits of that package is that it will
open and save as the same nearly all document formats, both old and new.
When on
Michael Natterer writes:
> On Tue, 2015-12-08 at 22:56 +0100, Jernej Simončič wrote:
> > I've seen that, but what I specifically meant was a File -> Export
> > option
> > that writes XCF compatible with older GIMP versions, possibly losing
> > data
> > in the process (which is why it'd be Export,
On Tue, 2015-12-08 at 22:56 +0100, Jernej Simončič wrote:
> On Tue, 8 Dec 2015 22:53:05 +0100, Jehan Pagès wrote:
>
> > Now wanting to sound sarcastic, but have you read my email? There
> > is
> > such an option and I told about it in the email you answer to.
> > Quoting myself:
>
> I've seen
Hi,
On Wed, Dec 9, 2015 at 9:29 PM, Akkana Peck wrote:
> Michael Natterer writes:
>> On Tue, 2015-12-08 at 22:56 +0100, Jernej Simončič wrote:
>> > I've seen that, but what I specifically meant was a File -> Export
>> > option
>> > that writes XCF compatible with older
-list@gnome.org
Subject: Re: [Gimp-user] opening 2.9.3 file in 2.8.14 (NOT)
Hi,
On Wed, Dec 9, 2015 at 9:29 PM, Akkana Peck <akk...@shallowsky.com> wrote:
Michael Natterer writes:
On Tue, 2015-12-08 at 22:56 +0100, Jernej Simončič wrote:
> I've seen that, but what I specifically meant w
On Thu, Dec 10, 2015 at 2:58 AM, Derek Mortimer wrote:
> Moving on to a new format gives significant advantages, but if it makes
> obsolete valid and useful past work, isn't that somewhat arrogant to tell
> users that past work is out of date and cannot be opened in the new version
> of GIMP?
We
ednesday, December 09, 2015 9:58 PM
> To: gimp-user-list@gnome.org
> Subject: Re: [Gimp-user] opening 2.9.3 file in 2.8.14 (NOT)
>
>
> Hi,
>
> On Wed, Dec 9, 2015 at 9:29 PM, Akkana Peck <akk...@shallowsky.com> wrote:
>>
>> Michael Natterer writes:
>>>
Alexandre Prokoudine writes:
> On Thu, Dec 10, 2015 at 2:58 AM, Derek Mortimer wrote:
>
> > Moving on to a new format gives significant advantages, but if it makes
> > obsolete valid and useful past work, isn't that somewhat arrogant to tell
> > users that past work is out of date and cannot be
On Mon, 7 Dec 2015 19:42:24 +0100, Jehan Pagès wrote:
> Maybe a good feature could be to have a small text listing exactly the
> reason(s) why an image cannot be saved in compatibility mode (overlay
> layer, high bit depth, metadata or a mix of 2 or 3 of these features.
> The new compression is
Hi,
On Tue, Dec 8, 2015 at 10:17 PM, Jernej Simončič
wrote:
> On Mon, 7 Dec 2015 19:42:24 +0100, Jehan Pagès wrote:
>
>> Maybe a good feature could be to have a small text listing exactly the
>> reason(s) why an image cannot be saved in compatibility mode (overlay
On Tue, 8 Dec 2015 22:53:05 +0100, Jehan Pagès wrote:
> Now wanting to sound sarcastic, but have you read my email? There is
> such an option and I told about it in the email you answer to.
> Quoting myself:
I've seen that, but what I specifically meant was a File -> Export option
that writes
Hi,
On Sat, Dec 5, 2015 at 7:26 PM, Akkana Peck wrote:
>> scott092707 (for...@gimpusers.com) wrote:
>> > Will this always happen, if I try to open a file saved in an
>> > earlier-vintage
>> > GIMP?
>
> Simon Budig writes:
>> No, this will not always happen, just when you
El sáb, 05-12-2015 a las 13:00 -0500, Steve Kinney escribió:
> On 12/05/2015 11:36 AM, Ofnuts wrote:
>
> > > > Wouldn't it be useful to have a different file extension for
> > > > the new
> > > > high-precision contents?
>
Speaking strictly from a user perspective, it always sucks when you try
On 05/12/15 13:17, Simon Budig wrote:
scott092707 (for...@gimpusers.com) wrote:
2.8.14 told me that "Opening '/data/scott/Desktop/100_0642&5.xcf' failed: XCF
error: unsupported XCF file version 8 encountered" (see screenshot).
Will this always happen, if I try to open a file saved in an
On Sat, Dec 5, 2015 at 5:06 PM, Ofnuts wrote:
>> No, this will not always happen, just when you use features that are not
>> available in the older gimp version - e.g. high precision pixel formats.
>>
> Wouldn't it be useful to have a different file extension for the new
> high-precision
On 12/05/2015 11:36 AM, Ofnuts wrote:
>>> Wouldn't it be useful to have a different file extension for the new
>>> high-precision contents?
>> What's the benefit?
>
> Not endlessly explaining to users that there are two different types
> of XCF. [ ... ]
>> Should file extension be changed
> scott092707 (for...@gimpusers.com) wrote:
> > Will this always happen, if I try to open a file saved in an earlier-vintage
> > GIMP?
Simon Budig writes:
> No, this will not always happen, just when you use features that are not
> available in the older gimp version - e.g. high precision pixel
scott092707 (for...@gimpusers.com) wrote:
> 2.8.14 told me that "Opening '/data/scott/Desktop/100_0642&5.xcf' failed: XCF
> error: unsupported XCF file version 8 encountered" (see screenshot).
>
> Will this always happen, if I try to open a file saved in an earlier-vintage
> GIMP?
No, this will
19 matches
Mail list logo