Quote:


There are commands such as AddToTranslationTable and @RelabelTreeItem that allow you to replace the text that appears in the Sesame interface.

Quote:


We're not planning on going anywhere.  We can't predict the future, but it is our intent to continue to develop Sesame.

Quote:


That's good to hear. Thank you for letting us know. 

Quote:


We've tried to be very straightforward in the various Q&A translation guides about what does and does not translate, where you can expect issues, and how to minimize translation difficulties.

The trial version is to allow people to try Sesame itself. Clicking "Translate" will only take a moment. It's Sesame that you'll be working with from that point forward.

We do know that we'll do a far better job translating your Q&A database than anything else you could migrate to. 

An upcoming version of Sesame is very likely to have an initialization file that includes a command that adds strings to the translation table on startup (as well as a number of other commands folks have been asking for).

In the meantime, may I suggest that instead of hardcoding the translation table into application programming, use the the file I/O commands to read in a text file containing the "from" strings and "to" strings. That way the end user can make adjustments to the translation as needed without redesigning the app, and the same file can be used across multiple applications.

Remember when using AddToTranslationTable that the "from" string must be an exact and whole match for the entire string to be translated. It is a good idea to try to keep the "to" string as close in length to the "from" string as is practical. Also, note that the translation only affects the display of the string - not the string itself. So if you are changing a command tree string and also using @SelectTreeItem, the @SelectTreeItem call will use the untranslated string - even though the translation appears on the screen.

Good news and bad news:

The good news first - the popups respond well to being translated. To translate the popup you are referring to you will need something like this:

AddToTranslationTable("The current record has been changed and has not been committed to the database.", "Another String")
AddToTranslationTable("Are you sure you want to close this record?", "Yet another string again")
AddToTranslationTable("Yes", "Yup")
AddToTranslationTable("No", "Nope")

The bad news - the individual lines in the spec handler window do not undergo the translation to avoid accidentally translating an LE name. I have since reconsidered and the individual lines in the spec handler window will be translatable in the next release. In addition, I am making it so that that symbol labels may be used in the "to string". This will allow you to replace the "A" and "D" of sorting with a small up or down arrow.

Of course, any changes I am making will be subject to testing and may be re-reconsidered by the marketing folks.