Huge Collections of Software Manuals and Knowledgebase

GreatManuals.com
Huge Collections of Software Manuals and Knowledgebase

 
Home Contact Us Request to publish your help manuals Request to remove your help manuals
Introduction
» LangAgent
» System Requirements & Installation
Operational Details
» What is LangAgent?
» LangAgent Working
» Using LangAgent In Projects
LangAgent Reference
» LangAgent Workshop Reference
» LangAgent Editor Reference
» LangAgent Runtime & API Reference
» LangAgent Add-in For Developer Studio
Support Information
» FAQ, Tips & Tricks
» Support & Feedback
 

FAQ, Tips & Tricks

Tips and tricks

  • LangAgent does NOT translate any string that contain a copyright sign (C). This is set by design.
    LangAgent does not translate any control in a dialog if its text begins with the `(back apostrophe) symbol (back apostrophe will be removed at runtime).
  • Current version of LangAgent was designed for and tested on European languages. You may have some troubles with eastern languages. For example, some languages use right-to-left writing which is not yet supported by Lang Agent.
  • English words are short enough, so the translated text can often turn out longer than the original one. Make sure, that a longer text can properly fit into your GUI. Pay special attention to checking all your dialog boxes if there is no control with a truncated text. We recommend you to leave some additional free space in every dialog control to avoid the translated text truncating.
  • LangAgent translates the strings which are loaded using the AfxLoadString function only. LangAgent does NOT translate a string if it is loaded via the WIN32 API functions (such as LoadString or LoadResource).

To handle strings loaded by the LoadString function use the LaGetStr function as follows:

LoadString(hInst, ID_MYSTRING, StrBuffer, sizeof StrBuffer);

LPCTSTR translatedStr = LaGetStr(StrBuffer);

// use translatedStr

FAQ

Q: Should I pay royalties if I use LangAgent in my commercial software?

A: No, LangAgent is royalty-free.

Q: Do you offer translation services?

A: Currently no.

Q: Are there any restrictions for using the LSTR macro?

free windows undelete free undelete download restore windows data
data recovery support recover data from formatted drive data recovery solutions
recover digital photos ipod support mobile forensic investigation

A: Yes. First, the source files scanner is very simple and does not allow you to use strings that span over two or more lines with the LSTR macro. So, the LSTR macro should be located on a single line. A line may contain the multiple LSTR macros. Second, avoid using ambiguous phrases in LSTR macros which can be translated in various ways. Keep in mind that some languages have declinations and conjugations. The endings of adjectives can depend on the gender of a noun.

Q: Is it possible to use formatting in the LSTR macros?

A: Yes. For example, str.Format(LSTR("%d items found"),nItems). Mind, that the translator must preserve all formatting symbols ('%').

Q: What's next?

A: We are going to implement a lot of new exciting features in the coming version:

support for Visual Basic, Java, Delphi and other developer environments.
HTML localization support Webservice to manage and automate developer<->translators interactions translation services.
...and more!...

Q: The caption of CPropertyPage is not localized. What should I do?

A: http://support.microsoft.com/kb/q141487/

Q: My question is not listed here...

A: Don't hesitate to contact us.

Home | Contact Us | Request to publish your help manuals | Request to remove your help manuals