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

Translations in an RTC list

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

    Translations in an RTC list

    I know all the important people are at the bar in Boston, but I have a question:

    As the snap here shows, I'm creating an e.rtc.List for use as the variable in a dropdown control. I'm replacing the displayed word with the translated word, but still storing the English word.

    As you can see, the rs.data(1) is returning a correct set of characters. When I construct the newline I get the correct set of characters. But I've tried several string/character replacement functions, and am getting garbage characters in the final output list when I try to substitute the translated string. See how the characters to display for Enrichment are nothing like what I'm producing right up to the substitution.

    Any thoughts? Image link here:

    rtcTranslate.png
    -Steve
    sigpic

    #2
    Re: Translations in an RTC list

    Still not resolved. I've discovered something else odd about this. If I display the result in the watch list in "unexpanded" mode, it shows the correct results. But when I expand the view to show the multiple lines of the result, the characters change. Unfortunately, it's the erroneous result that's getting emitted by the function.

    rtcTranslate2.png
    -Steve
    sigpic

    Comment


      #3
      Re: Translations in an RTC list

      Resolved. Anyone who's been to an Alpha Developer's conference, going on during this thread, knows how busy Selwyn is during the conference. Yet he found time to assist here -- we reported it as a bug but he pointed out that we just weren't using the right procedures.

      The solution is just this:

      Code:
      txt = rs.data(1)
      txt = *html_escape(txt)
      -Steve
      sigpic

      Comment


        #4
        Re: Translations in an RTC list

        One more update. Selwyn has pointed out that the dialog to Define Choices for a dropdown box tells us that using this would do the job:

        Code:
        txt = rs.toString()
        txt = "{noUTF8Encode}" + crlf() + txt
        I haven't experimented further -- my variable lists need to display the native language word but store the English word so I have this format in my variable lists:

        Code:
        DisplayThis|StoreThis
        DisplayThat|StoreThat
        Whether applying the above suggestion to this would do the job would just require a little experiment - maybe later or maybe someone else has time to try if needed.
        -Steve
        sigpic

        Comment


          #5
          Re: Translations in an RTC list

          Two quick comments. First, thanks for posting the solutions, Steve. It sets a good example which we should all follow. Even though posting the solution will not benefit you, it will certainly benefit others in the future.
          Second, you are correct that Selwyn was busy during the conference. Once again, anyone who wonders why we Alphaholics are so loyal to this software company should now have that question answered. No software company is more responsive to their customers. And this response is pervasive through Alpha.
          Thanks,
          Jay
          Jay Talbott
          Lexington, KY

          Comment


            #6
            Re: Translations in an RTC list

            Sigh. You'd think by now I'd figured out all the tricks. But now I have an Excel sheet with the Chinese translations for the English keys in the Text_Dictionary.

            At this point I wish I'd just done things with cut & paste -- I'd be done with the 1700 records. But nooo, I had to try this with Xbasic.

            So I'm updating the Text_Dictionary by using AlphaDAO to open the spreadsheet as a usual data source, getting the translated word from the spreadsheet, then trying variations on this:

            Code:
            	tword = rstxt.data("Translated")
            	args.set("Data", convert_acp_to_utf8(tword))
            This and several variations *almost* work, in that many of the entries appear correct, but it's clear that others are not. For instance, I get this:

            域??경만力?

            when I should have this:

            活跃地游泳

            Any ideas?
            -Steve
            sigpic

            Comment


              #7
              Re: Translations in an RTC list

              Talking to myself some more, but putting it up here for posterity (and maybe Jay):

              After no responses on this I asked Selwyn if he had any guidance. He pointed out right away that I should just be going through MS Management Studio to do the job. This was the perfect suggestion. I used Management Studio to import the Excel to a SQL table then ran a query to update my target table -- the text dictionary. Beautiful stuff if you know it's there -- I did not.
              -Steve
              sigpic

              Comment

              Working...
              X