Jump to content
You must now use your email address to sign in [click for more info] ×

Ronald N. Tan

Members
 View Profile  See their activity

  • Posts

    67

  • Joined

  • Last visited

 Content Type 

Everything posted by Ronald N. Tan

  1. Ronald N. Tan
    With the new funds as resources, does this mean people like me who are interested in RTL Languages will be more of a strong reality in the very soon future as opposed to the usual Serif replies of "having to reprogram from the grounds up because RTL language support" is a complex process? They missed out a huge opportunity to potentially capture the market share in India, Arabic Diaspora, Hebrew, and East Asian (Mandation, Japanese, Etc). Regardless of this news, can we also remember the company's kindness and understanding during the pandemic? Serif for the longest time discounted their softwares to 50%. Does anyone remember this? I have privately expressed my grievances towards Affinity and I refuse to upgrade to any of their software until they include the RTL Languages. For my needs, Publisher 1.X has served me well and will continue to do so. I am a current Adobe CC Photography Plan member and also continue to be perpetual license holder of Capture one 16.3.X. Their Black Friday deal of 50% off the perpetual license was too good to pass up! These fees (to me) are cost of doing business and I'll simply adjust my fees accordingly. Can we be little bit more optimistic and hopeful?!
  2. Ronald N. Tan
    I am currently a V1 user of Publisher and my 30-day trial expired for V2 suite of Affinity apps after the month of release date. Unless I overlooked or missed something, has there been an addition of customization for output (exported) files? It has been a longtime pet-peeve of mine that I absolutely abhor underscores (_) in filenames and usernames on the internet. Normally an underscore is used in the Affinity suite of apps for preexisting string names in the file nomenclature to prevent unwanted overriding. Is output naming customization a planned feature or internally discussed topic to be included in a later point-release update of V2?
  3. Ronald N. Tan
    I have my own personal grievances towards Serif and so I am voicing this dissatisfaction by NOT upgrading or buying V2 and simply continue to use V1 Publisher. We can only remain positive and hopeful that V3 will support RTL and the much needed Indic languages. :-)
  4. Ronald N. Tan
    @mehdy, Salam! I also support you for wanting Serif to have added RTL language support and major Indic languages from the Indian subcontinent. Correct me if I am wrong, but I read something that an OLDER now deprecated software from Serif support RTL, but their newer coded from the grounds up Affinity do not. This is like a "kick in the stomach" sort of feeling. Anyways...yeah. Serif made a HUGE mistake, because of all the potential customers in Arabic-speaking countries, Hebrew-speaking people, and the many Hindi, Telugu, Tamil, Malayalam speakers of India as potential customers.
  5. Ronald N. Tan
    @Sam Neil, Thank you for this tip. I downloaded and tried pasting into my V1 Publisher and it works. No need to use glyphs to individually enter for my preschool level learning of Farsi. Farsi language uses the Arabic alphabets and RTL writing system.
  6. Ronald N. Tan
    I think it's safe to say that this "oddity" affects Serif's other apps of Designer and Photo on Windows. I don't mind that the panels in discussion default to center. The moment we (the end users) position/resize, all three Photo, Designer, and Publisher should remember these custom position/size on subsequent runs of the applications.
  7. Ronald N. Tan
  8. Ronald N. Tan
    I am glad I am not the only way. The next follow-up is how do we gain volume (momentum) to raise to the Serif staff to consider making V2 remember the position and size? I am on Windows 11, latest stable version.
  9. Ronald N. Tan
    Hello everyone! Happy holidays and happy new year. Thank you for reading my post. Am I the only one experiencing this oddity? As in even in version 1 of Publisher, it annoys me that the software doesn't remember the window size and position for say: File >> New or when opening up the Guides Panel to manually add in (type in) guide pixel values. It always centers. Is this a "feature" or is this a bug? In other words, Publisher does not remember window position and size in version 1 and still the same behavior in 2.0.3. Next, how can we can Serif to consider fixing this so that we the end users have absolute control as to where we place and size our tool panels. I am not referring to the Studio Panels, where we can add tool panels and customization. I am talking about the tool panel that pops up when doing File >> New or View >> Guides. Do you see that? No matter where you position and/or resize, the application doesn't remember. It always defaults to center-of-screen.
  10. Ronald N. Tan
    I remain hopeful and positive, but based on the development cycle of Affinity Suite of Applications (Designer, Photo, and Publisher), I am not holding my breath. Here is to hoping that Serif puts Indic and RTL languages on their internal product development roadmap for version 3. Until that day arrives, I will vote with wallet and not upgrade to Publisher 2.X or to the full Suite of Applications.
  11. Ronald N. Tan
    Mea culpa concerning the iOS apps and users on iPad. As a super happy user of Affinity Publisher V1, I know Affinity Suite of Apps started with iOS and MAC platforms, before they became available to the PCs. Going forward, I still would to see Serif (somehow) cutting off the "middle man" and receive/handle all transactions back to them. What if the iOS and MAC versions of Affinity Suite of Applications are strictly 30-day trials? If the iOS and MAC user wants to unlock their apps, they would have to purchase the license at the Affinity Website and not buy at the iOS store. Isn't this possible?
  12. Ronald N. Tan
    I would like to have the ability to have a custom output (export) file naming to the Affinity Suite of Applications. At the moment from version 1 as I am still using Publisher V1 and decided not to upgrade to V2—the output files are named as: FileName FileName_1 FileName_2 Etc. I would like the ability in a point-release/update in V2 of Publisher (and Photo and Designer) so that us users can configure any file naming procedure we like. How difficult would this be from a developing standpoint? As all of us are creatives and designers at various stages of careers, aesthetics of any kind tend to bother us. I think we can all agree on this (creatively). What bothers me (irks) me most is the underscores_in_filenames. I don't like them. I prefer dashes-in-filenames instead. Even if we can't customize filenames, I would be super happy if we can have a preference options in the Preferences to say "Use dashes (-) instead of underscore (_) in output/export filenames."
  13. Ronald N. Tan
    In the context of "Communications" has Serif has a serious internal leadership concerning the buying and paying structure going forward? For example and when version 3 arrives, this is going to years from now, Serif and Affinity Suite of Applications will have name recognition. By then, I would like Serif to drop selling their "apps" in the Apple and Google Play app stores and fully move over selling of APPLICATIONS here at Serif. This way, Serif can provide upgrade paths and every transaction will go to Serif and not having Apple/Google Play app store taking any percentage cuts.
  14. Ronald N. Tan
    This thread is for people (like me) who are interested and hoping for support of Indic languages in Affinity Version 2 (V2). Sadly, there is still no support for Indic languages as of this moment, the 9th November, 2022. Features may be added in a future point-update or point-release. Let's all remain positive and hopeful that the staff and developers at Serif keeps the dialogue for Indic Languages and RTL Language support as open.
  15. Ronald N. Tan
    I will be expressing my disappointment with lack of support for Farsi (Persian Language) by not upgrading to version 2. I remain positive and hopeful that the staff and developers at Serif keeps RTL language an open dialogue and perhaps in version 3 will be fully supported. The workaround at the moment and for short and simple Farsi/Arabic is to use the Glyph Browser and assemble the word(s) and simple phrases glyphs by glyph.
  16. Ronald N. Tan
    As someone who is learning Hindi Devanagari (reading and writing), I will happily take the support of Indic LTR support in V2, which should also include suppose for Dravidian-based languages of South India: Telugu, Tamil, Kannada, Odia, Malayalam, etc. The Devanagari script is used by Hindi, Marathi, and Nepali. I had a good chuckle perusing how much that thread was derailed and went off topic. It's entertainment to kill time until V2 is officially announced. Maybe in V3, there will support for RTL for Farsi, Urdu, Arabic, Hebrew, and several scripts used in China.
  17. Ronald N. Tan
    If not already, I am hoping—going forward with the forthcoming version 2.X—bug reports and any kinds of Support be provided by something like Zendesk or similar. This forum could remain as is for us users to bitch and moan about oddities and be a therapeutic outlet to talk it out amongst ourselves. My Adobe Creative Cloud is about to be auto-renew on August 1 for the 2022—2023 year. Many probably know this already, there is already a private beta testing of Affinity 2.X products. The magazine AEC broke that news in their February 2022 article. Publisher is great for my needs. I am hoping (wishing!!!) that the 2.X release will finally give better support for right-to-left languages and proper support for Indic languages. I remain patient for the new goodies to be release in 2.X soon.
  18. Ronald N. Tan
    With Version 2.0 going forward, I think Serif should sell directly and not via "app stores." The way I see it, professionals don't invest in "apps," rather we invest in "programs or software." Once the proper end-of-life (EOL) is reached for all Affinity Suite of apps, make noticeable descriptions in the app stores. I think Serif can see from their perspective that they would handle all kinds of transaction, while at the same time they are in complete control of pricing decisions. There is now no more commission fees to the app stores. Because each of us already has an account, when purchased any Serif products, future upgrade pricings can take into account our previous version purchase.
  19. Ronald N. Tan
    I don't think it is due to "incompetence" from Serif. The real (and probable) is the lack or resources/research and name recognition. If Adobe representative contacted to notify AMD about such bug, I think AMD would get on finding a solution ASAP due to the enormous(!!!) professional market share that Adobe has. As an owner of Publisher, which I use as a hobby for mainly creating collages for my personal cooking project, Serif can put "professional" at every other word for their Affinity Suite of products. As long as it lacks widespread real-professional adoption and not from hobbyists or part timers, these large GPU companies—nVIDIA and AMD—only see Serif as that "alternative/wannabe" company. If you mention the Affinity Suite not having proper right-to-left (RTL) support for Arabic, Farsi, Hebrew, and several other support for Indic (languages spoken in India and the Indian Diaspora), that is incompetence. Us Publisher users have been begging(!!!) Serif to bring us proper support for footnotes/endnotes/etc and after all these years is silence. That is incompetence. I digress. The saying goes—you get what you pay for. I remain hopeful; Version 2.0 is forthcoming. This is confirmed/verified by an already existence of 2.0 Beta albeit in private testing as reported by AEC Magazine. Let's hope version 2.0 will be surprise for all of us.
  20. Ronald N. Tan
    I don't want my post to be here-say; however, with version 2 of the Affinity Suite around the corner and people seem to be bringing up "Version 2" talk on Twitter via search for the "@affinitybyserif" at-mention, I am truly hoping Serif will have a surprise for us who wants/NEEDS RTL support either for professional reasons or as indicated in my previous post history educational purposes in using Affinity suite of apps. Regardless, as I am still a Creative Cloud subscriber for my profession in photography, Photoshop is my goto and fees for using PS (as the Photography Plan) is write-off for professional reasons, I am glad, grateful, and appreciative of Serif for making software (Publisher and Designer) affordable. This is the AEC Magazine post referencing the already existence of a private version 2 of the Affinity Suite of software: https://aecmag.com/technology/serif-affinity-for-aec-firms/. With this and knowing that 2 is around the corner, I remain hopeful, but will not be holding my breath for RTL support. Have a look at the Affinity Publisher (AP) users' plea for Endnote/Footnote support. That thread has literally 46 pages (!!!) of people asking and the usual Serif employee chirping canned responses.
  21. Ronald N. Tan
    With Version 2.0 around the corner as hinted by AEC Magazine's article on the 2.0 beta version of Affinity Suite of Software, I am truly hoping for the support of right-to-left (RTL) writing system in Affinity Publisher (AP). https://aecmag.com/technology/serif-affinity-for-aec-firms/. RTL is long overdue and I can't believe Serif neglected the potential user-base of customers to poach/tap into. I was recently active in another RTL thread and posts going back to 2019 and some referencing a now expunged post going back even earlier for the lack to RTL support. As always, I remain hopeful and optimistic that Serif will (eventually) deliver on the ability to have proper RTL support.
  22. Ronald N. Tan
    I just figured out (with my extreme limited vocabulary) that the your original Farsi well wishes contained (romanized) nush-e jan or nush-e joon. "نوش جان" Which has the literal meaning of "may it be sweet for your soul" but my Chef Najmieh-joon uses that at the end of all her recipes in the equivalent of "Bon appetit." I have looonnnnng ways to go. I have Amiri font installed and I use PS to paste and made the words super huge on my screen. I know certain circles prefer "durood" (درود) as a teaching way to say "Hello" instead of salam (سلام), which (again) I know has Arabic origins. I apologize in advance as an outside and clearly learning Farsi...why would someone feel slight off, when the entire Persian alphabet is Arabic letters.
  23. Ronald N. Tan
    I had to "cheat" and use Google translate. At the moment, it's not even preschool level. It took me a long time to identify each of the letters in your sentence. Isolated forms of meem and noon clearly stick out. 🙂 متشکرم. Also, at the moment, a lot of my self-learning is memorizing specifically words and names and not yet sentence forming levels, if that make sense. If you had pasted "نجمیه باتمانقلیچ" I would instantly recognize that as the name of the super famous Persian chef, whom I am using her books to learn Persian cooking, etc. Alas...not to get offtopic. 🙂 I make graphics for my self-learning in Affinity Publisher. Each simple word, I identify the individual letters and type them in AP via using Glyph browser. Copying and pasting does not work properly in any of the Affinity softwares. Thats why (someone like me) I would REALLY like to have RTL support in the Affinity softwares.
  24. Ronald N. Tan
    Just to reply as a form of solidarity and voting for the proper and full support of RTL languages, especially Arabic and Farsi. I am currently learning Farsi for the purpose of culinary purposes and as mentioned previously and many...many times...Serif needs to somehow add Arabic, Farsi, Hebrew, Urdu as these are the major Middle Eastern languages with potential to poach users away from Adobe products. My Hindi Devanagari is stronger than my Farsi. I've expressed my disappointment with the lack of proper Indic languages in Affinity trio of products. Indic languages are LTR and should be "more easier" to adapt and implement than RTL. I have to use the Glyph Browser and fix certain merging of Hindi alphabets (as an example). When entering Farsi, say for typing out names of Persian Food, I have to use the glyph and find the specific glyph that corresponds with the alphabet's position. It's cumbersome, but for my use (and needs), it is a band-aid fix. If not for version 1.X, I and many others who are of RTL and LTR languages would like to have this in version 2. Heck, maybe raise the price a little bit. Even with a few raise in price, still BEATS renting software from Adobe!!!
  25. Ronald N. Tan
    I have no idea what those are. I am hoping Serif might find those files and have some kind of leads. Since my last post reply, I was working on entering glyphs of Persian (Farsi) words manually. I haven't had any document loading oddities. Fingers crossed that the oddity doesn't present itself anytime soon.
×
×
  • Create New...

Important Information

Terms of Use | 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.

 Accept Cookies  Reject Cookies