For a full explanation of DBT's general approach to supporting various
languages, including the case where more than one language occurs in a
given text, please see section 2.0 of the "Topical How-to Guide" (under
DBT's Help menu).
A quick summary of that section would be that the "base language and
braille code jurisdiction" of a text determines the table that is selected
for translation (on the Document / Translation Tables menu). When the base
language is the only language in the document, there is no need for
[lng~...] codes -- the language is assumed to be the base language
throughout. So the quick answer is: to do a Vietnamese document, select the
Vietnamese tables. This can be done after importing from Word, but must be
done before translation to braille.
As explained in section 3.0 of the "Topical How-to" document, it is
convenient to set up a "template" with settings -- including language table
settings -- that you expect to use frequently. So if you set up a
"Vietnamese" template with those tables (and any other desired settings)
preset, you can just select that template whenever you import a Vietnamese
document from Word.
[lng~...] codes come into play only when a "secondary" language occurs
within a document, e.g. Spanish text within a basically English document.
(That would include the case of a document that is completely in Spanish,
but is to be brailled for use by English-speaking readers who would expect
the braille to follow "English context" conventions for the treatment of
Spanish -- which are not entirely the same as truly Spanish conventions.
Such readers might be beginning students of the Spanish language, for
example.) When that happens, you would use the translation table for the
base language, but insert [lng~...] ... [lng] codes around the
secondary-language text. (A convenient way to do this is to apply an
appropriately defined style -- for example, a "Spanish" style, defined as
[lng~es] ... [lng].) This only works, however, when the secondary language
is supported by the translation table in use. Not all combinations are
available, however, so you need to check in the "Translation Tables Usage
Guide" (under Help) to see which ones are supported in the base translation
table you are using.
At present in DBT, there are no tables that support Vietnamese as a
secondary language -- so if you want to translate Vietnamese, you must use
the Vietnamese table. That means there has been no need so far to define a
[lng~...] code for Vietnamese. However, for future reference, since ISO
639A defines "VI" as the two-letter code for the Vietnamese language, we
would use [lng~vi] when such a definition becomes appropriate.
* * * * This message is via list duxuser at freelists.org. * To unsubscribe, send a blank message with * unsubscribe * as the subject to <duxuser-request@xxxxxxxxxxxxx>. You may also * subscribe, unsubscribe, and set vacation mode and other subscription * options by visiting //www.freelists.org. The list archive * is also located there. * Duxbury Systems' web site is http://www.duxburysystems.com * * *
