Perhaps you mean our internal string sets defined for each
language, and compiled into the executable copy of AbiWord.
For each language we support, we include a table of translated
dialog, message, menu, and toolbar strings. By editing your
profile (~/.AbiSuite/AbiWord.Profile on Unix), you can set
your MenuLabelSet, StringSet, ToolbarLabelSet to use any
supported language. A default profile might look like:
<AbiPreferences app="AbiWord" ver="1.0">
<Select
scheme="_builtin_"
autosaveprefs="1" />
<Scheme
name="_builtin_"
AutoSpellCheck="1"
KeyBindings="default"
MenuLabelSet="EnUS"
MenuLayouts="Main"
RulerUnits="in"
SpellCheckDirectory="dictionary"
SpellCheckWordList="american.hash"
StringSet="EnUS"
StringSetDirectory="AbiWord/strings"
ToolbarAppearance="icon"
ToolbarLabelSet="EnUS"
ToolbarLayouts="FileEditOps FormatOps"
UnixFontPath="fonts"
/>
<Recent
max="4"
/>
</AbiPreferences>
... you could enable Danish strings by changing the file
to resemble something like the following:
<AbiPreferences app="AbiWord" ver="1.0">
<Select
scheme="mycustom"
autosaveprefs="1" />
<Scheme
name="_builtin_"
AutoSpellCheck="1"
KeyBindings="default"
MenuLabelSet="EnUS"
MenuLayouts="Main"
RulerUnits="in"
SpellCheckDirectory="dictionary"
SpellCheckWordList="american.hash"
StringSet="EnUS"
StringSetDirectory="AbiWord/strings"
ToolbarAppearance="icon"
ToolbarLabelSet="EnUS"
ToolbarLayouts="FileEditOps FormatOps"
UnixFontPath="fonts"
/>
<Scheme
name="custom"
MenuLabelSet="DaDK"
StringSet="DaDK"
ToolbarLabelSet="DaDK"
/>
<Recent
max="4"
/>
</AbiPreferences>
Notice how I had to change the referred scheme at the top and
I then created a new scheme at the bottom with any overriding
preferences.
We will eventually have a user-interface (in the form of a
preferences dialog) in the application, so that editing
this file manually will not be necessary.
If you're wondering how to use our "strings" capabilities to
translate AbiWord to a new language, reply for more information.
-- Shaw Terwilliger