Jump to content
Fritz_H

[By Design] APhoto 1.6.5.135 - Translation missing

Recommended Posts

Hi,

I tried to open a file (created with APhoto beta 1.7.0.293) with APhoto 1.6.5.135 (german):

1658845807_2019-04-1310_55_27-AffinityPhoto.png.8138ec7d7c9ef205005fb0f3295bf882.png

1. This one line is not translated. (not a big issue, I know..)
2. Why? Will upcoming Versions of Affinity-Photo/-Designer use a different File-Format?

Thanks.

kind regards
Fritz

Share this post


Link to post
Share on other sites
3 hours ago, Fritz_H said:

Will upcoming Versions of Affinity-Photo/-Designer use a different File-Format?

Yes, we can assume - considering APublisher integration into Affinity Suite.


Affinity Store: Designer 1.7.3.481, Photo 1.7.3.481, Publisher 1.7.3.481.
Windows 10 Pro, Version 1903, Build 18362.418.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080.
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080.

Share this post


Link to post
Share on other sites

Each new release adds new functions, and the native files (.afdesign, .afphoto, .afpub, and the various export files for brushes, presets etc.) produced by a new release cannot be read by the prior release.


-- Walt

Windows 10 Home, version 1903 (18362.356), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.486 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.486 Beta  / Affinity Publisher 1.7.3.481 and 1.7.3.475 Beta

Share this post


Link to post
Share on other sites

Hi @Fritz_H,

Project files are not backwards compatible. This is by design and will not be changed, purely because features from 1.7 do not exist 1.6. Also, once we roll out 1.7, we will encourage everyone to update from 1.6, so technically there is no reason why one may need to go back :)

Thanks,

Gabe. 

Share this post


Link to post
Share on other sites
6 hours ago, GabrielM said:

Hi @Fritz_H,

Project files are not backwards compatible. This is by design and will not be changed, purely because features from 1.7 do not exist 1.6. Also, once we roll out 1.7, we will encourage everyone to update from 1.6, so technically there is no reason why one may need to go back :)

Thanks,

Gabe. 

OK.. but are you going to provide a correct translation?

kind regards
Fritz

Share this post


Link to post
Share on other sites
42 minutes ago, Fritz_H said:

correct translation?

From your other thread, it is clear, that the problem is not in the wrong translation.

 


Affinity Store: Designer 1.7.3.481, Photo 1.7.3.481, Publisher 1.7.3.481.
Windows 10 Pro, Version 1903, Build 18362.418.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080.
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080.

Share this post


Link to post
Share on other sites
On 4/16/2019 at 11:34 PM, Pšenda said:

From your other thread, it is clear, that the problem is not in the wrong translation.

? trying to be funny or just a language-issue between the 2 of us?

The Translation is missing - regardless the question of file-(in)compatibility.

Fritz

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.