Jump to content

Congratulations! And a fantastic offer at launch.


Recommended Posts

Just now, ZombieRofl said:

Don't get me wrong a UI update is welcome, but nothing special, or 'BIG' like it was told us.

I suggest you first explore all of the new features before coming to conclusions.

Cheers,
d.

Affinity Designer 1 & 2   |   Affinity Photo 1 & 2   |   Affinity Publisher 1 & 2
Affinity Designer 2 for iPad   |   Affinity Photo 2 for iPad   |   Affinity Publisher 2 for iPad

Windows 10 21H2 (19044.2251) 64-bit - Core i7 - 16GB - Intel HD Graphics 4600 & NVIDIA GeForce GTX 960M
iPad pro 9.7" + Apple Pencil

Link to comment
Share on other sites

A little disappointed about Designer. I hoped more…

A lot of users asked for a shape builder tool. Never use it with Illustrator but we can do the same with the pathfinder. We spend maybe a little more time but we can achieve the result. 

A Blend shape tool would be more useful.

No vector pattern and no DXF export too.

One more thing : Only for Mac OS 10.15+. Not yet for me…

Link to comment
Share on other sites

  • Moderators

Hi @ZombieRofl,
Thanks for your feedback. It's not just an UI update (for macOS/Win and iPadOS). There's quite a few new tools/features in all apps, improvements to existing tools/features, a large number of bug fixes, and the new Publisher for iPad. All these required quite a bit of work from a relatively small team. Who knows what the future will bring...

Link to comment
Share on other sites

Giving a proper evaluation within such a short time-frame is by all means questionable. I resume my verdict to a later date so that I can see for myself what V2 will do for me.

Link to comment
Share on other sites

All the usual bells and whistles and still NO RTL OR COMPLEX SCRIPT SUPPORT!!!

Just unbelievable! To be honest, this is bordering on being disrespectful! We've been asking for it since 2014! Is it THAT much of a technical issue?! Or is it THAT low on the list of priorities?! Either way, I (as I'm sure many others) feel utterly deflated by this release...

Link to comment
Share on other sites

4 minutes ago, Musaed said:

All the usual bells and whistles and still NO RTL OR COMPLEX SCRIPT SUPPORT!!!

Just unbelievable! To be honest, this is bordering on being disrespectful! We've been asking for it since 2014! Is it THAT much of a technical issue?! Or is it THAT low on the list of priorities?! Either way, I (as I'm sure many others) feel utterly deflated by this release...

The faux outrage is strong in this one. 

 

Marc

Link to comment
Share on other sites

4 minutes ago, Optische Ausrichtung said:

And, have they got the function now?

 

Yes.

-- Walt

Desktop:  Windows 11 Home, version 21H2 (22000.613) 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 
Laptop:  Windows 10 Home, version 21H2 (19044.1706) 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
        Affinity Photo 1.10.6 (.1665) and 2.0.4  and 2.1.0.1709 beta/ Affinity Designer 1.10.6 (.1665)  and 2.0.4  and 2.1.0.1709 beta / Affinity Publisher 1.10.6 (.1665)  and 2.0.4  and 2.1.0.1709 beta
iPad Pro M1, 12.9", iPadOS 16.3.1, Apple Pencil 2, Magic Keyboard

      Affinity Photo 1.10.7 and 2.0.4 and 2.1.0.1713 beta/ Affinity Designer 1.10.7 and 2.0.4 and 2.1.0.1713 beta/ Affinity Publisher 2.0.4 and 2.1.0.1709 beta

Link to comment
Share on other sites

11 minutes ago, Musaed said:

Is it THAT much of a technical issue?!

I feel able to reply to this based on years of preparing Persian/Arabic texts. It is a technical issue as well as a resource issue. RTL cursive text is considerably more complex than LTR Latin text. I still see today RTL texts prepared in things like InDesign and Word with broken characteristics.

An example is below. The font is not broken, the text engine is.

image.png.2b2b8b4bf2df4624c4e6d90d3568a6c2.png

Link to comment
Share on other sites

6 minutes ago, LondonSquirrel said:

I feel able to reply to this based on years of preparing Persian/Arabic texts. It is a technical issue as well as a resource issue. RTL cursive text is considerably more complex than LTR Latin text. I still see today RTL texts prepared in things like InDesign and Word with broken characteristics.

An example is below. The font is not broken, the text engine is.

image.png.2b2b8b4bf2df4624c4e6d90d3568a6c2.png

Thanks for the reply. Yes I understand that it is demanding from a technical point of view, but (sheesh!) Affinity Designer has been out for eight years now! If free stuff like Inkscape and Scribus can support RTL and complex script why can't Affinity?? Personally, I'd like to know whether it is in the pipeline or not at all. For the time being, good ol' Inkscape will have to soldier on for me...

Link to comment
Share on other sites

8 minutes ago, LondonSquirrel said:

I feel able to reply to this based on years of preparing Persian/Arabic texts. It is a technical issue as well as a resource issue. RTL cursive text is considerably more complex than LTR Latin text. I still see today RTL texts prepared in things like InDesign and Word with broken characteristics.

An example is below. The font is not broken, the text engine is.

image.png.2b2b8b4bf2df4624c4e6d90d3568a6c2.png

Read this: https://wolthera.info/2022/10/svg-text-layout-for-krita/  and you'll understand how difficult right to left text support really is...

Link to comment
Share on other sites

6 minutes ago, Musaed said:

Thanks for the reply. Yes I understand that it is demanding from a technical point of view, but (sheesh!) Affinity Designer has been out for eight years now! If free stuff like Inkscape and Scribus can support RTL and complex script why can't Affinity?? Personally, I'd like to know whether it is in the pipeline or not at all. For the time being, Inkscape will have to soldier on for me...

For longer RTL texts I use LibreOffice. Its Harfbuzz engine is better than it used to be, but still has issues with broken kashidas.  Simple RTL texts aligned to the right work well enough. For short snippets (even as long as 10 to 20 words) I use the glyph engine in APub and construct the words one glyph at a time, as shown above. It's slow to use, and what would take me about 1.x seconds to type instead takes a couple of minutes. But the result is acceptable.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.