Search the Community

1. Big Issue with this V2, I can't select multiple nodes by dragging the selector???? 2. Arabic language doesn't support RTL and perfection for the characters of the language 3. There is no multi-selection for items inside assets categories 4. The Workspaces should have import/export presets

Understood. I admire the existing functions in Affinity apps, just ask if I missed any option for RTL languages. Thanks!

Serif is not saying that they don't implement non-Latin language support, it just takes time and costs. They say they will someday. Search RTL/Arabic in this forum, they are in the same situation.

Are there any plans for adding RTL support?

Thank you for your words Ash - Affinity is the basis of my project and I cannot work without Publisher - Despite some of the quirks the trio are one of the best software in their respective fields - I think it would be better when and where possible to have the BETA testing public to avoid any hiccups and making the software far more robust - Furthermore do a survey on the most frequently requested features once in a while would be great. I personally feel it is often ignored with a "currently no plans to introduce such feature..." is not helpful. A prime example would be RTL Support. The universal licence is good but not always useful as for example I don't use a mac or an iPad so - I don't benefit from it. (Even though I have bought V2). Like many here I started my design with Serif Page Plus in the 90s - so as far as loyalty is concerned you have mine because your software is actually very good and intuitive, coupled with the videos - So you have 3 GEMS which I used EVERYDAY. Let's move forward and thank you once again.

Exactly, it's the same with RTL languages and other localised specifics; commercially it makes no difference how many people speak or write a language, what is important is how many people will buy a particular piece of software because it uses that language! People accuse Serif of being "anti" this or that, or of being "disrespectful" to them, but I'm sure it's simply a case of, with limited time and resources: do you work on features that will benefit the vast majority of people using the apps, or on things that will only benefit a comparatively small group of them! I'm not saying that Serif shouldn't do these things, just that it is a matter of priorities.

An option to convert Spot colors to CMYK or RGB would be awesome. Thanks for the info about the "press ready" black conversion, which profile do you recommend for exporting to Print On Demand platforms like KDP, lulu, IngramSpark... And lastly, Serif should prioritize features that make the apps work for large teams in professional environments like RTL and CJK languages support, print, installation files and collaboration. This is the fastest way to make more money selling multiple licenses.

I'm afraid this is another example of the Affinity apps not having support for RTL languages. And I'm afraid they won't handle your request, either.

now that v2 is here, with many new features, but many pros still needs some to really be comfortable with the Suite... could we please have a minimal roadmap on what you are working on? even something really generic like this Trello roadmap (for the Obsidian app). we know, and you know, that we don't have many other options today.. or Adobe, or Affinity, unless we want to use separate apps for specific works..).. we want to support you, but we need to be kept engagend, and know where you are going! for example: if you aren't goind to support ePub or external texts in Publish.. we aren't goind to use it for next books. if you aren't supporting RTL before 3/5 years, we accept it and use something else from today. if you plan automation in 2 years, we could use a temporary solution... thank you!

While I am all with Serif for the huge undertaking they have been carrying on since years, I have to share Kal's frustration. What I can start to see with V2 is this: - Photo and Designer are strong competitors to the Adobe equivalents. They still miss things, but do so many things well. AI features don't compel me. All considered, I was already mostly happy with the first version. - Integration with the Mac's UI is even worse than before. This may seem a little thing for our fellows using Windows, but it is extremely important for us Mac users. We chose the difficult way of living out of the crowd because we love the comfort and elegance of that UI. Programs interfering with our lifelong meditation can't find good reception. - While adding some extraordinary features, like side notes, and continuing to have the older, like live preview of changes, Publisher is very far from being an InDesign replacement. It can already be fine for someone working in isolation, but not for people working in a team or with collaborators, due to the lack of any way to be integrated in a production flux. It still lacks some fundamental things for long projects, like cross-references. It can't deal with RTL and CJK languages, that are all part of my everyday job. And then, there is the same issue of the application frame breaking the usefulness of the clean, multi-window Mac environment. I was sincerely hoping to be able to finally trash InDesign in the next few months. But at this point I fear it will be several years away from now. The only two solutions, in the meantime, are to either keep a machine (real or virtual) with a current Mac OS just to use InDesign CS6, or to switch to InDesign CC. This latter solution repels me, since it would mean making all the forthcoming documents hostage of Adobe and its aleatory price and plan policies. Not a great situation, in the freelance/small shops publishing world. How bad I feel? I'm considering alternatives to using page layout software, entirely. Paolo

There is any plugin for rtl in v2?

In V2 there is no RTL support and there wasn´t any announcements in that regard nor is there a roadmap of future additions available.

Non-Latin language support like CJK, RTL and CTL is very poor in affinity. And the company even said that this will take a long time to implement and they have other things to focus on. So I won't expect a fix in the near future.

Does Affinity Publisher V2 support Unicode fonts in Indian Languages (complex script option) and RTL languages? The earlier V1 did not handle that. I use extensively all the Indian Languages. Madurai Sridhar

+ for RTL even though I know it'll take a long time to be implemented.

I'm still using Affinity, still didn't buy RTL Fixer, still wondering if I should, and still hope the guys in Serif will add this feature ASAP

After years of begging, and multiple posts and negatives reviews, Serif insists on denying support for Arabic/Hebrew writing. Every release you tell me that the feature is coming, and it is on your roadmap. Kindly, I would like to ask for a refund for my V2 purchases as I am reaching a dead-end with this. I am sticking to Adobe Suite even though it is not free just to use this writing. Thank you for continuous efforts to disappointment. Gmail - Arabic and RTL Support.pdf

Yes, there are important improvements, like this one, notes in Publisher, antialiasing in basic selections in Photo, global object selections, shape builder and warps in Designer, more robust Boolean operations in vector graphics in general, and a few other, well worth getting an upgrade (especially if working on multiple platforms). It is impossible to say if there are BIG changes in code and program architecture that the mentioned words in capital letters imply (perhaps just for me), but I hope I am wrong and we'll see fruits of the kinds of internal changes that have been made, which would make it possible to have, at some point (not necessarily along 2.x path) big (power) usability changes like scripting support or at least improved macro operations (and not just in Photo), improvements in PDF imports and exports, interchange file format supporting edits, improved search and replace with area limits and ability to save GREP definitions, CJK and RTL support, etc.

if Affinity doesn't support RTL What the point buy V2?! Affinity v2 useless for V1 owners the "New features" do not worth buy all the programs again in almost in the same price

Every software company stock plummeted in the last year including zoom, spotify and hardware like AMD, nvidia. The sudden rise is to all stocks too due to the federal bank saying that they'll stop increasing the interest rate. The people who didn't get their needed features implemented got angry. And to be honest, there are things that render the software unusable to for a lot of graphic design work. Luck of complex layout text and RTL languages support, even sino languages users complain all the time from luck of vertical text and punctuation support. And luck of ebook export too. I understand that the company can't add everything at once, and they also has the right to ask for another round of payment after 3-8 years of free updates. But I guess a not of people's work can't wait for another couple of years for them to be implemented and need them now.

I am Chinese and I can assure you too. I can only speak little Japanese so I will reply you in English. CJK text support and vertical texts have been requested for a long long time by we East Asian users. Serif said that if they add these functions to their softwares, they would remake the whole way the softwares compose texts. I think it is time for them to solve these problems, either the support for RTL texts. Internationalization is more and more important to the companies like Serif so it's necessary to remind the dev team of the importance to add then asap.

A little bit disappointed that V2 still doesn't support RTL. There's no reason to upgrade to V2 for me, I guess.

Bumping this thread. As I'm thinking of buying Affinity Publisher 2 but need RTL ability

Personally, I'd have been happy with just RTL support in version 2, and I'd have paid for that. I guess I'd stick to V1 as it covers my needs.

Will RTL languages (ever) be supported by Affinity V2? I ask because the need for Hebrew support is the only thing keeping me tethered to the Adobe ecosystem (and from which I would very much like to be free).