cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Global versions of ADEPT

unknown1
1-Newbie

Global versions of ADEPT

Hi,

I have been creating Japanese documentation using ADEPT global
by translating English SGML sources.
I guess you can use the same DTD and FOSI with ones for English
for your compiling Japanese or Korean SGML sources generally.

Although it was not everything which I performed to DTD and FOSI
for our processing Japanese SGML sources,
translating some strings in the FOSI file (such as "Chapter",
"Section", "Contents", "Index", "Figures" etc.) into Japanese
was major work.

/Takayoshi Oda Compaq Japan

> >>>>> "David" == David L Hintz writes:
>
> David> Hi, Is anyone currently using the global versions of ADEPT products
?
> David> We are currently using ADEPT*Editor and Publisher to produce
> David> English, French, and German versions of our documentation. We woul
d
> David> now like to have our SGML translated to Japanese and Korean. What
> David> sort of work is involved in "converting" the DTD and FOSI to a
> David> multi-byte (unicode?) language. I'd be interested in hearing from
> David> anyone who's been down this path and could offer some insight as to
> David> the problems we should expect to encounter.
>
> Please respond to the list, as at least one other person is interested in
> this subject: Me! 🙂
>
> Ed
> --
> Ed Bailey Red Hat, Inc. http://www.redhat.com/
1 REPLY 1

>>>>> "Takayoshi" == Takayoshi Oda writes:
...
Takayoshi> Although it was not everything which I performed to DTD and FOSI
Takayoshi> for our processing Japanese SGML sources, translating some
Takayoshi> strings in the FOSI file (such as "Chapter", "Section",
Takayoshi> "Contents", "Index", "Figures" etc.) into Japanese was major
Takayoshi> work.
...
We are producing French and German content from English SGML sources, and
have also translated the strings in the FOSI. But what we did was to use
the m4 macro processor (We're primarily a Linux shop, and are running ADEPT
under Solaris). Once we had a FOSI that produced acceptable English
output, we simply replaced each English string in the FOSI with a macro
name (for example, "Chapter" becomes "RH_CHAPTER").

Then we simply set up a file that defines the all the macros appropriately,
and run the "macro-ized" FOSI through m4. Presto -- out comes the original
FOSI. We then only need to have our translation company translate about 30
words or phrases in our macro definitions, and we can produce a
foreign-language FOSI literally in seconds.

If anyone's interested, here's our English m4 file:

divert(-1)
changecom(`')
define(`RH_AND', `and')
define(`RH_APPENDIX', `Appendix')
define(`RH_AUDIENCE', `Audience')
define(`RH_CHAPTER', `Chapter')
define(`RH_CLASS', `Class')
define(`RH_CONTENTS', `Contents')
define(`RH_DATE', `Date')
define(`RH_EDITION', `Edition')
define(`RH_EQUATION', `Equation')
define(`RH_EXAMPLE', `Example')
define(`RH_FIGURE', `Figure')
define(`RH_INDEX', `Index')
define(`RH_IN_SECTION', `in Section')
define(`RH_ISBN', `ISBN')
define(`RH_ISSN', `ISSN')
define(`RH_IX_SEE_ALSO', `See also')
define(`RH_IX_AND', `and')
define(`RH_IX_SEE', `See')
define(`RH_OPTIONAL', `Optional')
define(`RH_OPTIONAL_SUBSTEPS', `Optional substeps')
define(`RH_PART', `Part')
define(`RH_REF', `REF')
define(`RH_SECTION', `Section')
define(`RH_SEE', `See')
define(`RH_SEE_ALSO', `See also')
define(`RH_SEVERITY', `Severity')
define(`RH_SM', `(sm)')
define(`RH_SOURCE', `Source')
define(`RH_TABLE', `Table')
define(`RH_VOID', `void')
divert`'dnl
include(`docbk30.fos.m4')`'dnl

--
Ed Bailey Red Hat, Inc. http://www.redhat.com/
Announcements