Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

File encoding and multilanguage support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    File encoding and multilanguage support

    Hello,

    Currently I am evaluating A5 v10.5 (build 3553) and my focus is writing web apps that use single language, but different than English. And most problems I met were with the encoding, which is used to store the files (.a5w and .a5wcmp).

    It looks like A5 store files explicitly in ANSI or some other restricted encoding. This leads to some not so nice problems.
    1. In .a5w pages all non-ascii characters are encoded in HTML representation (&#xxxx), which is big pain if the alphabet is totally non-ascii (in my case Cyrillic). Future support and development of such pages is very hard to be done. The only chance is to use the WYSIWYG pane, which is not suitable in most cases when you need to deal with the source directly.

      This is strange limitation because the Content-Type is set to �utf-8� by a <meta> tag put there by A5. I tried to not use the WYSIWYG pane and put the texts directly in the source, but obviously the file is stored in non-utf-8 encoding because on save the texts become unreadable.
      .
    2. The same problem is with most of the components. Yes, there are 3 components already (grid, tabbed ui and page layout builder), which have some kind of Multilanguage support and it can be used as a workaround (even the application is single language). But what about the Navigation component� all the characters in it (I am still talking about Cyrillic alphabet) have to be HTML encoded. You can imagine how look Navigation component in the designer with about 10 top-level options and 3 levels below. This is very hard to be managed later when you need to change something.


      .
    3. However the biggest problem is with the grid component - nevertheless it has Multilanguage support. If you have some non-ascii characters in the SQL query (by example an If() in the SELECT statement, which produces strings with non-ascii characters) then the grid is not working because it seems that on save these characters are encoded incorrectly and as a result the SQL query become invalid.





      In this case even if you substitute the non-ascii characters in the query with the corresponding HTML encoding equivalents they are shown in the grid as &#xxxx, and not as expected single characters. Maybe there is a way to "force" the grid component to not encode the result returned by the SQL query, but I didn�t found a way to do that.



      The only workaround for this situation were to create a view, which contains the correct SQL query (with all the non-ascii characters) and to point the grid to use that view, but this solution is really ugly.


    I suppose that some of the problems could be because of my really short using of A5 (3 weeks yet).

    So, does anybody else have similar problems or decisions for them?

    #2
    Re: File encoding and multilanguage support

    hi,
    are you solved this problems couse I have the same problems with encoding on a5w pages and components ?!?

    thanks
    Best Regards,
    Kamel Jazmati

    [email protected]
    Kamelj.com
    @KamelZJ

    Comment


      #3
      Re: File encoding and multilanguage support

      Hi Kamel,

      We stopped the evaluation of A5 because of this and some other not so nice problems.

      Good luck,
      Emil.

      Comment


        #4
        Re: File encoding and multilanguage support

        Hi,

        I also have the same problem.

        Trying to develop in Turkish Language but crashed in first Navigation component. I typed a Turkish Text to navigator text line and can't see the properties of this node. I cannot delete the node! Can't do anything :(

        Any suggestions from Alpha would be appreciated...

        Thanks,
        Ozgur
        Ozgur Ugur
        Computer Eng.
        Data Yazilim Ltd.
        Izmir - Turkiye

        Comment


          #5
          Re: File encoding and multilanguage support

          hi,
          you have to change the Turkish text to unicode using this website http://konieczny.be/unicode.html
          Best Regards,
          Kamel Jazmati

          [email protected]
          Kamelj.com
          @KamelZJ

          Comment


            #6
            Re: File encoding and multilanguage support

            Thanks for your answer Kamel,

            But as you may guess, this is not very easy to do. Alpha guys should find an acceptable solution for this, esp. if they claim to be global!

            Thanks anyway,
            Ozgur
            Ozgur Ugur
            Computer Eng.
            Data Yazilim Ltd.
            Izmir - Turkiye

            Comment


              #7
              Re: File encoding and multilanguage support

              Thanks for the useful link. However, I'd like to see alpha V have international UI function in the next version.

              Comment

              Working...
              X