Jump to content

Search the Community

Showing results for 'hebrew rtl arabic'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 33 results

  1. Yes, you are 100% correct. except for the “Sofit” letters which makes no problems for us because they have dedicated keys in our keyboard. In Arabic it’s different, and the whole thing about letters being joined into one is a new thing for me and my team. In Hebrew it matters not if the letter is the intro of a word, ends the word and especially if it is written after a specific other letter. Basically - each letter in Hebrew is that letter, no appearance change whatsoever. BUT at the same time, my team and I know nothing about “giving up” nor do we wanna take any part in such way of thinking. I believe our app will help out many people and not just with Affinity’s software. which is why I’m trying to find a few Arabic speaking people (and hopefully some of the other RTL languages speakers) who could join in with this project. And hey - if the person is by any chance a Python developer all the better! if any of the people here can help out we would love to speak with you further via email: support@artwayz.com
  2. Don't hold your breath. I started talking to Serif about Arabic language support in 2008. They choose to ignore a market segment. This is just an opportunity for a competitor to pick up the slack and take over the entire market. They can't be bothered, they are not interested they have no plans to do it. so don't waste your time. I might be wrong, but my impression is, the company has taken a conscious decision not to support RTL languages but just don't want to tell clients flat out that they are not interested in supporting RTL. I can not speculate as to the reasons, but had they really wanted to support Arabic or Hebrew it would have been done by now.
  3. @Amr Please change the title of the post to fix RTL for Arabic, Persian and Hebrew languages to get more comments and votes that will increase the priority of the request.
  4. Why Affinity still does not offer RTL support (for Hebrew, Persian, Arabic etc.) even after many years. However, if this prepares RTL support, it's sure to make a lot of money. Because I'm sure there are thousands of designers who need RTL typography. The question is: Is Affinity incredibly rich, doesn't it need money Or is RTL support not an important part of these professional (!) programs? A place where the mind stops.
  5. Me too. There are many popular RTL languages in the world like Arabic, Hebrew, Persian and ...
  6. Hi everyone, I know that it might come up in few topics, but it was long time ago, and I was wondering if affinity Have any plans to ass RTL option to their apps, for Hebrew and Arabic support. Thank you in advance any answers, Chen
  7. Dear the Affinity team: Middle-east lang support is needed also for people who don't speak and type in Arabic or Hebrew etc, and that's because when you have a LTR document (such as English, etc) if just a few words in any RTL language are mixed in, you will have problems with your text. and that's the reason why i can't join Affinity right now. I hope this feature will be soon, so i will have the ability to buy a few copies from the Affinity suite for my small team. All the best!
  8. This will only work for RTL languages such as Hebrew, where the letter shapes don’t change. It won’t work for Arabic, because the letter shapes depend on the neighbouring letters.
  9. As far i know, there is no Chinese/Japanese UI in Affinity. Bt"w, i'm not sure if we need a completely Arabic/Hebrew/etc UI, we just need that the English version should supports RTL. (My work is usually in English, its simply sucks whenever I have mixed words from other languages).
  10. Hi dominik. Here you can found the reason why they are unwilling to add support for RTL and Complex scripts in the near future. . When i asked Serif directly via email if they would add this support, that's what they answered me: "We understand that there is a large number of users who require RTL support, but it is not something that can be created quickly. There are a lot of intangibles with the different RTL languages, that do not come in to play with Latin languages. Latin languages are very formulaic in there composition, where as right to left languages can vary from Arabic to Hebrew, or from Persian to Urdu. We don't just need to implement the ability to right from right to left, we also need to ensure that all of the technical aspects of these languages are working correctly. We are a tiny company with limited resources. We will do what we can we with the resources that we have. We do not want to focus the coming years focusing on one feature, and if it is something that is feasible then it will be included in the future." --- So, it sounds that we'll have to wait a long time, until we will have support for complex scripts and rtl languages in affinity. Bt"w, in my opinion it's worth to hire programmers only for this purpose. it's a 100 percent guarantee they will get back the money (With large percentages) very fast, taking in mind that they are opening the way for new hundreds of thousands of graphic designers (and maybe millions over the time) who can't work without this supports.
  11. Hi everyone here on the forums! My name is Jace, i'm the chief and founder of a marketing group located in New York with a team of five graphic and web designers on board. so as you can figure out alone, i'm spending a tremendous amount of money in subscribible licence purchases, just to cover my adobe creative apps... When i heard that there is a new competitor to Adobe with a range of 3 productive alternatives apps - overall - a one time purchase, it was very interesting, and i decided to try it out if to check out if it comes on the daily work for my small team, and yes, i can say fully confident that it's really wonderful how they get done such amazing products. In fact, there is one reason why i feel that i can't switch right now to those apps. and no, it's not because there is still a range of features that is currently unavailable in this (1'st) version of affinity, like 'image tracing' and 'scripting' and more, taking in mind that its a new suit of applications, and it will forsure get big updated with the time. The reason why i can't change my office apps to affinity, and in the same time to reduce my adobe bill to half or less (i still need the web and animation tools from them) is simply 'right to left' support. After a deep trial season, i figured that rtl lang. are not supported, and i can't stick with a program that will have problems every time there will be a few words in any of the Middle Eastern languages like arabic or hebrew (something i don't have daily, but also occasionally is enough to be a concern). Actually, i will have now to stay with Adobe. and i'm sure that the day things will change, i will be back with you. the affinity serif apps are super fast and stable! hope it will be soon. All the best!
  12. First I want to congratulate everyone in Serif for creating this awesome software and trio. After being a user of the Publisher Beta and being active in this forum, I have collected a list of features that I need for my work (mostly book interior design) and some that others requested. I'm not saying that Serif should provide them in the near future, but I hope it helps them see what's needed and give an outline for other members of the community. And I hope affinity will release an official roadmap for Publisher soon. Languages: Support for CTL: Complex Text Layout, Indic and RTL languages like Arabic and Hebrew CJK: Vertical text and proper punctuation Text: Footnotes/Endnotes Insert variables based on paragraph/Character styles/Index entries... Paragraph styles spanning through columns Compatibility: Open IDML files Scripting Tables: Tables Spanning through pages Repeat header when a table span to another page Calculations inside tables RegX: Save RegX Find/Replace Execute Saved RegX Find/Replace from inside paragraph styles eBooks: Export to ePub Option to set HTML tag +/- class for each paragraph style. Export to pure HTML file — I wanna know your idea about implementing HarfBuzz for Complex Text Layout —
  13. 100+ for supporting RTL languages like Arabic and Hebrew. your apps are great, but i can't purchase Affinity without this features.
  14. I just suggested that there is a POSSIBILITY, and I'm not saying that every single designer will change to affinity (you may not know with such an amazing application like Designer...). And yes, there are at least millions of graphic designers\Photographers\etc. who using "professional design software" in RTL languages, between the over 420 million people talking and writing in Arabic, 9 million people in Hebrew, 100 million people in Urdu, etc.
  15. Hi all. I'm new to affinity and i'm trying now the Publisher app (beta). i'm really impressed from Serifs amazing apps, but i recognized that thare is no support for RTL text. (incidentally, i don't understand that, there are millions of millions designer in arabic and hebrew around the world needy to this support for their daily basis...) Anyway, my only real problem with this is the "first line indent" on the "left" side from the paragraph. (i'm importing my text from word) Is there some way to get this done on the "right" side?
  16. I also need RTL support and have been waiting for it for years. I can't use Affinity products professionally, no matter how much I love them, without the ability to use Arabic or Hebrew text. At the very least, a work around would be appreciated, or an updated timetable. I'd like to purchase Publisher, but if I'll have to wait years for RTL support then I won't have a use for it.
  17. i trying to use your product but you have problem with Arabic Text From 2015 ( https://forum.affinity.serif.com/index.php?/topic/9580-adding-arabic-text/ ) and now after 4 Years with version 1.7 still with no arabic text , how i change Adobe if u can't fix this stupid bug with RTL , Please help us with that problem , you put Hebrew and Arabic in Typography only we need fast fix please thanks
  18. Hello John, your words are harsh and straight out hostile, i hope that its just a misunderstanding that you are attacking others personally. There is an "infinite amount of users" its the human population growth which is growing each year. Even if there where a theoretical saturation of consumption, Serif would then release a new version - a paid upgrade and the sales begin again. Serif hasn`t even begun yet in catering to at least ~1 billion potential customers which would happen if RTL writing was available inside the Affinity range. Here an image showing the distribution of just one of the many scripts(here is the Arabic script distribution) which happen to be RTL writing, there are more scripts like Hebrew which also is RTL. Subscriptions are like renting a house, you won´t get attached to the area/product and can and will probably move on to other areas/prodcuts like you dear John are doing while abandoning the Adobe renting area.
  19. The patent shouldn't last that long – a patent should protect the technology in about 5 years, after that the technology should be freely available to everybody who want to use it. Adobe Paragraph Composer is much, much older than that (it is ca 15 years old. Adobe World-Ready Paragraph Composer is slightly younger [perhaps 12 years old]). Edit: the HZ algorithm patent expired in 2010! according to Wikipedia. Regarding Knuth-Plass algorithm: You can't copyright a method or algorithm, but you can patent a method or algorithm. The Knuth-Plass algorithm patent is also expired nowadays. Besides, I wish that Affinity Publisher will be world ready from scratch. That will benefit all users, including scientific area where they often take upp source texts in foreign languages, for instance hebrew, arabic, ancient greek etc. It is much easier to support multi language (including LtR and RtL) from scratch than adding afterwords (Adobe had some serious problem for years when they added Hebrew and Arabic into InDesign afterwards (bugs that was very difficult to track etc). Adobe still have some serious issue with Adobe World-Ready Paragraph Composer: Combining Adobe-World Ready Paragraph Composer with Story function (problem with hyphenated words). If you only use Adobe Paragraph Composer together with Story function, then it works very well…
  20. THE Affinity Designer for Mac OS X is a very promising software. I downloaded to test the program very briefly. The only Feature I am missing is support for RTL/BiDi languages like Arabic, Persian, Hebrew, Urdu etc. i hope you consider adding support for RTL writing system already from beginning to make this fantastic software usable for middle eastern user. On Mac OS platform the build in text engine provide a reasonable RTL/BiDi support on system level. Using this OS X possibilities will this task much easier.
  21. I second David request. But if you are committed to support RTL (for Hebrew, Persian, Arabic etc.) then DO IT NOW! before it gets too complicated. It’s like Ginger & Fred. Everything Fred Astaire does, Ginger Rogers does too, but backward (and with high heels)!
  22. As you are surely aware, a huge chunk of your potential users use Right-to-left languages, such as Arabic, Hebrew, Persian, and Urdu. In addition, Mac supports it natively (with Core Text) as does Android, Chrome and Firefox (using Harfbuzz). Even cheapo competitors such as Swift Publisher on the Mac enjoy RTL support, so it looks non-native and poor that you've created your own text engine.
  23. As someone who has used Photoshop extensively and had been complaining about its clunkiness, Affinity Photo (And Designer no less) was a welcomed breath of fresh air. I have been a vocal supporter of the Adobe To Affinity migration ever since I started using product. It runs like butter. It feels like made by designers as advertised. However, one can't help but feel an overwhelming disappointment, if not a bit of humiliation when talking about Affinity to other designers when they pop the question "does it support Right To Left Languages." I live in the UAE; a majority of the designers and artists that work here are Indians, many of whom barely speak a scrab of Arabic, let alone know how to read the language, and yet their biggest concern is being able to go RTL because the market demands it and its kind of awkward when speaking to a client why a simple copy/paste procedure doesn't always work for them When I expanded my work to FNB menu designs, that's when it hit me hard the most. The amount of time spent to implement these insane work arounds just to get arabic written properly on an AF file made me see their point. Any designer worth his salt will know that his main job is to communicate a message; if I'm indeed speaking to designers involved in developing this product, I'll begin my extending my utmost respect to a fine product you guys have going. But I can't help but ask: if we're here to communicate messages through visuals, how can something as crucial as Right-To-Left language support be placed so far down the priority list?! Arabs amount to almost 386 million and the language stands in the top 5 most spoken in the world. This goes without mentioning Hebrew/Cyrillic/Azeri... I mean no disrespect, but I just needed to convey my frustration. I won't pretend to understand how hard development is.
  24. EDITED: This is just a compilation of Affinity Photo and Designer roadmaps by TonyB and MEB's "Common Feature Requests INDEX", just to be easily found. Everything that is already implemented is removed. I hope that Affinity staff would not get angry for doing this on my own. Just want to keep things clear. Designer Phase II transparency flattener Bleed area guides Mesh fill tool Mesh warp/distort tool Knife tool Calligraphic line styles Export slices previews with actual export data Pages Text features including Bullets and Numbering Knockout groups Multiple Effects/Fills/Strokes per shape Convert Pixel selection to Vector shape Replicate/Blend Tracing Tool/Persona Vector Eraser Vector Patterns Feathering Simplify paths / Line Smoothing Arrowheads Photo Looks persona Levels improvements Curve Improvements Export persona - preview with compression and palette optimisation Non destructive Develop Layer Tool Presets User categories in the media browser for shapes and objects Support for image layer Spot channels Crop to Selection Crop & Resize (single step) Freehand Selection Tool more similar to PS Lasso Both User Interface Icons / Customization Progress bar/visual feedback on file loading/saving Remember last used folder used for each type of action (open, save etc). Sticky Settings (remember tools settings) - It's being implemented / work in progress in 1.5 / 1.6 versions Support to RTL (right-to-left) Languages (Arabic, Hebrew etc) Change rulers origin point / relative origin point Allow guide creation from all tools Lock Guides Image/file linking Select objects by attributes (same fill, stroke, font etc) Ability to export/save to the same folder as the source (opened file) Rotate & Scale objects using the Rotation Centre as reference point - Already available in Designer 1.6 Beta Background Blur Layer Effect (FX) Noise/Grain Export PSD text as native text DXF/DWG
  25. And what of the people of the rest of the world? Arabic, Hebrew, & a few other common languages are read RTL; ideographic ones Like Chinese & Japanese can be written in several different directions. Languages do not have a writing direction, standard or otherwise. Scripts do, but that is not the same thing. Moreover, time related concepts like before & after have no inherent spacial aspect like a left to right or a top to bottom direction. There certainly is a tendency to associate such things with one's native written language direction, but it is an entirely arbitrary distinction with no logical basis -- it makes no sense whatsoever to say that an event that occurs before another one occurs to its left or right, or above or below it.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.