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

Language - Translation - SQL

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

    Language - Translation - SQL

    I've just started into the language internationalization, but can't figure out how to handle Korean (and probably Japanese and Chinese - also on my list but not there yet).

    This may be a SQL question more than anything else, but I can't find the answer.

    I'm using the Text_Dictionary table in MS SQL automatically generated by A5. This means that the DATA field is varchar(max). I've offered a couple of my administrators a grid to be used to supply the translations for the DATA field, but all the grid field returns is "??" when we try to insert a Korean-language string. I took it a step further, and now think that the problem may not (necessarily) be in my A5 configuration, but in MS SQL itself. For instance, in MSSMS, I try this:

    Code:
    update text_dictionary set data = '동물' where [key] = 'animals' and language = 'korean'
    But the field still just contains "??" (without the quote marks).

    What to do about this?
    -Steve
    sigpic

    #2
    Re: Language - Translation - SQL

    When you create your SQL table, ensure that you include CHARACTER SET utf8 for the field. This will ensure other language characters are correct.

    I used utf8 when creating tables for my Alpha / Google Translate Utility : http://youtu.be/BFD1t03ffms

    I used MySQL, but I believe it's about the same for MSSQL.

    It's been a while since I did this but... for example...

    Code:
    CREATE TABLE `tbltextdictionary` (
      `KEY` varchar(100) NOT NULL,
      `LANGUAGE` varchar(40) NOT NULL,
      `DATA` longtext CHARACTER SET utf8,
      PRIMARY KEY (`KEY`,`LANGUAGE`)
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    Last edited by Davidk; 02-03-2015, 12:06 AM.

    Comment


      #3
      Re: Language - Translation - SQL

      Nope, not that simple David.

      1. The MS SQL DATA field needs to be set to Nvarchar(max), not the varchar(max) that Alpha created.

      2. The syntax in MSSMS to update a record is:

      Code:
      update text_dictionary set data = [B][COLOR="#FF0000"]N[/COLOR][/B]'동물' where [key] = 'animals' and language = 'korean'
      I can do this without flaw in MSSMS. Still struggling to do this with a grid so I can hand off the translation job to the professionals. Something within the grid is translating the translation and I'm getting garbage back.

      I've taken over the SQL with the onBeforeSQLCommandExecute event, and while debug shows I've got it right, I'm still missing something that's interfering:

      Code:
      if "Korean" $ e.argsXML
      	e.SQLCommandWasHandled = .t.
      	e.cn.PortableSQLEnabled = .f.
      	vNewData = extract_string(e.argsXML, "<Data Type=\"C\">", "</Data>",1)
      	sql = "UPDATE Text_Dictionary SET DATA = N'" + vNewData + "' WHERE ([KEY] = :PKValue_1 AND [LANGUAGE] = :PKValue_2)"
      	dim args as sql::Arguments
      	args.xml = e.argsXML
      	e.cn.execute(sql, args)
      end if
      -Steve
      sigpic

      Comment


        #4
        Re: Language - Translation - SQL

        Hmm, just can't get it.

        As noted I've taken over the SQL. Even trying a connection string forced to UTF-8. And everything in the debug window suggests it's doing everything I want. But when I enter this:

        사건

        I get this stored and returned instead:

        사건


        Anyone have an idea?
        -Steve
        sigpic

        Comment


          #5
          Re: Language - Translation - SQL

          Can you post of a sample grid and the table you're using with a couple of rows of data?

          Comment


            #6
            Re: Language - Translation - SQL

            Steve,

            What do you mean with "Still struggling to do this with a grid" ? If I just copy "동물" from your message & paste that into a grid & submit then it does show ok also in MSSMS. In other words what exactly are you doing ?
            Frank

            Tell me and I'll forget; show me and I may remember; involve me and I'll understand

            Comment

            Working...
            X