Previous November 27, 1996
Return to CSuite Workshop Index
Landon is developing an option chooser for the installation, but it is not expected to be ready for the next release, as we are not yet clear on all the dependencies.
Nightly installs are continuing on soltst and need testing. Login as guest and register for your own account, and then report on what you can break! ;-)
Discussion ensued as to where we should report back the testing results, and it was agreed that CSuite-Tech@chebucto.ns.ca was appropriate for that traffic.
Csuite-Dev@chebucto.ns.ca will continue to be used for more general and external development issues, and CCN-tech would continue to serve for local tech-team issues not related to development.
Return to Topic List
Subject: host: Short Problem Description <paste in file URL from info page> <paste in output> <note problems observed, inputs given, etc. as appropriate>
For example,
Return to Topic List
If you have trouble editing elsewhere, contact Landon who is working on the script.
Landon and David Potter will arrange access to CVS for the Help-desk Group
Tupdate and tshell will be renamed to update and shell for the distribution.
Return to Topic List
Language support is triggered by settings in the browser. In Lynx, Setup Language [en, fr, ...]; Netscape and other browsers will have similar options - some more sophisticated to give a preference order for different languages. A trial modification has been made to lynx, and will be incorporated in beta-lynx to support the language choices, that will export the HTTP_ACCEPT_LANGUAGE variable to lynx-cgi:, the same as http: references now provide.
Language translation for scripts is not going to be a simple exercise, especially to do it in a way that can be maintained. The current strategy was demonstrated using a version xmfd of the mail forward script. All English text strings (not script terms or HTML tags) are extracted to a dictionary .lang.en (on a per-directory basis) and substituted using suitable keywords prefixed by l_ (lower-case L). Then a translated version of the dictionary is created by the Translation Team. .lang.en -> .lang.fr for example. A few examples will be tried in Portuguese and perhaps other languages, as well.
To facilitate translation, we will try to place all 'Translatable Text' in single quotes as a first step. The file can then be scanned for strings, appropriate keyword phrases can be selected, and substituted for the original text, and the text placed in the English dictionary file. The script, and its dictionary entries, will be referred for translation, and the resulting translated language file installed. It is proposed that, once the method is verified, the Workshop members be offered an opportunity to prep the files (text identification, keyword substitution, English dictionary entries) for an appropriate honorarium. Efforts will be needed to reduce duplication of equivalent phrases in the dictionaries.
In the example, a bug in quoting in the original script was identified 8-)
A special editor might be devised to facilitate this process, displaying both script and substituted vocabulary in choice of languages simultaneously... We also need a way to notify appropriate team members that revised translations were needed, on both an urgent (e.g. motd) and routine basis.
Return to Topic List
Please give us your feedback, and sit with a newbie user to see how it works for them. All comments, via the links on the pages, are welcome. We have had some helpful notes already!
Return to Topic List
Return to Topic List
We plan on looking at ways to restructure the Workshops, so as to improve the development aspects, separate out local tech-team issues, and work out strategies to recruit and make use of new volunteers. A volunteer liaison is also needed.
Return to Topic List
Previous Workshop November 27, 1996
Return to CSuite Workshop Index
Submitted by Ed
Dyer aa146@chebucto.ns.ca
Workshop Coordinator David J Murdoch
djm@chebucto.ns.ca