As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I expect Canadian People to give good advice about International Messages. (A Lasry, if you hear me ...) I am not fond of so many Decodes, and, as a Colbertist Centraliser, prefer a Central Data Base of Messages + a very performant tool to access those Messages. But, as an old craftsman, I perhaps miss new efficient tools and keep clutched to old ideas.
Focus Mainframe 7.6.11 Dev Studio 7.6.11 and !!! PC Focus, Focus for OS/2, FFW Six, MSO
The easiest would probably be to decode a Dialogue Manager Include statement:
-DEFAULT &&LANG = 'FR';
-SET &INC1 = '-INCLUDE INC_LABEL_' || &⟨
&INC1.EVAL
TABLE FILE CAR
SUM SALES AS '&LABEL1'
BY COUNTRY AS '&LABEL2'
END
-RUN
inc_label_en.fex:
-SET &LABEL1 = 'Country';
-SET &LABEL2 = 'Sales';
inc_label_fr.fex:
-SET &LABEL1 = 'Pays';
-SET &LABEL2 = 'Ventes';
Claude's idea of storing the language-based text in a table is another idea...
Claude, Albert can be reached via Skype.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
We have the same problem here in Israel, compounded with the fact that Hebrew is written right-to-left.
When we have to develop a multi-language application, we use only &variables for everything: titles, texts, headings etc. Then our application is developed using our in-house system where all the the forms and all the objects are stored in a central database in many languages. Similarly, we store the values of the &variables in the same central database, also in many languages.
When the application is run, the language is set by ONE variable and automatically all the &variables, forms and objects are given the appropriate values from the central repository.
Adding an extra language becomes very simple and the procedures are invariant.
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006
If you are using 76x, then multi-language can be applied at the master level. Use the meta-data for all of the column title language values. If you place your defines and computes in the master as well, then you could use the same method. That would save you a lot of trouble.
The only thing you should have to use the ampher variables for is report based defines and computes, and page headings/footings.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott