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

Ronald N. Tan

Members
  • Posts

    67
  • Joined

  • Last visited

Contact Methods

  • Website URL
    https://ronaldnztan.com

Profile Information

  • Gender
    Male
  • Location
    Los Angeles, CA, USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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. 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. 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. @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. @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. 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. 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.
  8. 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.
  9. 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.
  10. 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?
  11. 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."
  12. 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.
  13. 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.
  14. 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.
×
×
  • 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.