Commit | Line | Data |
---|---|---|
86530b38 AT |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE>MHonArc FAQ: Supported Environments</TITLE></HEAD> | |
5 | <BODY> | |
6 | ||
7 | <!--X-NavButtons-Start--> | |
8 | <p align=center> | |
9 | [<a href="general.html">Prev</a>][<a href="usage.html">Next</a>][<a href="faq.html">TOC</a>][<a href="http://www.mhonarc.org/">Home</a>] | |
10 | </p> | |
11 | <!--X-NavButtons-End--> | |
12 | ||
13 | <!-- ===================================================================== --> | |
14 | <HR> | |
15 | <H2><a name="supenvs">Supported Environments</a></H2> | |
16 | ||
17 | <!--X-TOC-Start--> | |
18 | <ul> | |
19 | <li><a href="#platforms">What platforms can MHonArc run under?</a></li> | |
20 | <li><a href="#mac">What about Mac?</a></li> | |
21 | <li><a href="#vms">What about VMS?</a></li> | |
22 | <li><a href="#perl">What version of Perl is required to run MHonArc?</a></li> | |
23 | <li><a href="#muas">What mail user agents (MUA's) does MHonarc support?</a></li> | |
24 | <li><a href="#mdomodigests">Can MHonArc process Majordomo digests?</a></li> | |
25 | <li><a href="#listprocessor">Can MHonArc process Listprocessor archives?</a></li> | |
26 | <li><a href="#ezmlm">Can MHonArc process ezmlm archives?</a></li> | |
27 | <li><a href="#maildir">Can MHonArc process qmail's maildir style mail folders?</a></li> | |
28 | <li><a href="#netscape">Can MHonArc process Netscape Messenger folders?</a></li> | |
29 | <li><a href="#evolution">Can MHonArc process Evolution folders?</a></li> | |
30 | <li><a href="#compuserve">Can MHonArc process Compuserve messages?</a></li> | |
31 | <li><a href="#otherformats">What about other mailbox/folder formats?</a></li> | |
32 | <li><a href="#nonenglish">Can MHonArc create non-English archives?</a></li> | |
33 | <li><a href="#bilingual">Can I create bilingual archives?</a></li> | |
34 | <li><a href="#unicode">Does MHonArc support Unicode?</a></li> | |
35 | </ul> | |
36 | <!--X-TOC-End--> | |
37 | ||
38 | <!-- ??????????????????????????????????????????????????????????????? --> | |
39 | <hr noshade size=1> | |
40 | <table border=0> | |
41 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
42 | <h3><b><a name="platforms">What platforms can MHonArc run under?</a></b></h3> | |
43 | </td></tr></table> | |
44 | ||
45 | <P>MHonArc is known to run under Unix-based operating systems, | |
46 | MS-DOS/Windows, WinNT, Win95/98, and OS/2. If Perl is available for | |
47 | the system you are using, you can probably run MHonArc. | |
48 | </p> | |
49 | ||
50 | <!-- ??????????????????????????????????????????????????????????????? --> | |
51 | <hr noshade size=1> | |
52 | <table border=0> | |
53 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
54 | <h3><b><a name="mac">What about Mac?</a></b></h3> | |
55 | </td></tr></table> | |
56 | ||
57 | <P>MHonArc has been coded to support MacPerl, and a couple of | |
58 | users have reported that MHonArc will run under MacPerl. I | |
59 | recommend trying it out, and if you have problems, send a message | |
60 | to the MHonArc mailing list. | |
61 | </P> | |
62 | ||
63 | <!-- ??????????????????????????????????????????????????????????????? --> | |
64 | <hr noshade size=1> | |
65 | <table border=0> | |
66 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
67 | <h3><b><a name="vms">What about VMS?</a></b></h3> | |
68 | </td></tr></table> | |
69 | ||
70 | <P>The following includes information from Walter F.J. Mueller, | |
71 | <a href="mailto:W.F.J.Mueller@gsi.de">W.F.J.Mueller@gsi.de</a>: | |
72 | </P> | |
73 | <pre> | |
74 | * The -outdir argument must be specified UNIX style. | |
75 | * Avoid any $ in a filename, some interpolation will certainly mess it up. | |
76 | It ended up defining a few extra logicals like | |
77 | $ define kp3_root kp3$root | |
78 | to have $ free absolute pathnames in the usual $-prone VMS environment. | |
79 | </pre> | |
80 | <p>Also, you will need to use Perl 5.004_04 or later and MHonArc | |
81 | v2.1.1 or later. | |
82 | </p> | |
83 | ||
84 | <!-- ??????????????????????????????????????????????????????????????? --> | |
85 | <hr noshade size=1> | |
86 | <table border=0> | |
87 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
88 | <h3><b><a name="perl">What version of Perl is required to run MHonArc?</a></b></h3> | |
89 | </td></tr></table> | |
90 | ||
91 | <p>Perl 5, or later. Older versions of MHonArc are Perl 4 compatible. | |
92 | So if you are under the unfortunate circumstances of only being able | |
93 | to use Perl 4, you will need to grab an older version of MHonArc. | |
94 | </p> | |
95 | ||
96 | <p>Perl 5 is required for MHonArc v2.3 or later. The last Perl 4 | |
97 | compatible release is v2.2. | |
98 | </p> | |
99 | ||
100 | <!-- ??????????????????????????????????????????????????????????????? --> | |
101 | <hr noshade size=1> | |
102 | <table border=0> | |
103 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
104 | <h3><b><a name="muas">What mail user agents (MUA's) does MHonarc support?</a></b></h3> | |
105 | </td></tr></table> | |
106 | ||
107 | <p>The question is better stated as: <b>"What mail message storage formats | |
108 | MHonArc support?"</b></p> | |
109 | ||
110 | <P>MHonArc can convert mail that is stored in UUCP mailbox | |
111 | format (ie. all messages are in a single file), or in the format used | |
112 | by the | |
113 | <a href="http://www.ics.uci.edu/~mh/">Rand Message Handler</a> | |
114 | (MH) (messages are contained in separate | |
115 | files within a directory). MHonArc is known to work with | |
116 | the following MUAs: <EM>MH/nmh</EM>, <EM>mail</EM>, <EM>Mail</EM>, | |
117 | <EM>Elm</EM>, <EM>Eudora</EM>, <EM>WinVN</EM>, <EM>Windows | |
118 | Trumpet</EM>, and <EM>NUPop</EM>. </P> | |
119 | ||
120 | <DL> | |
121 | <DT><STRONG>NOTE</STRONG> | |
122 | ||
123 | <DD><P>To support some MUA's, it may require redefining the | |
124 | MSGSEP or MHPATTERN resource. Please consult the documentation | |
125 | for more information about these resources.</P> | |
126 | </DL> | |
127 | ||
128 | <!-- ??????????????????????????????????????????????????????????????? --> | |
129 | <hr noshade size=1> | |
130 | <table border=0> | |
131 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
132 | <h3><b><a name="mdomodigests">Can MHonArc process Majordomo digests?</a></b></h3> | |
133 | </td></tr></table> | |
134 | ||
135 | <p>Here is a couple messages from the | |
136 | <A HREF="http://www.rosat.mpe-garching.mpg.de/mailing-lists/mhonarc/" | |
137 | >MHonArc mailing list</A>: | |
138 | </p> | |
139 | <BLOCKQUOTE> | |
140 | <UL> | |
141 | <LI><em>Subject</em>: Re: Majordomo Digest -> MHonarc?</LI> | |
142 | <LI><em>From</em>: "Christopher P. Lindsey" <<A HREF="mailto:lindsey@mallorn.com">lindsey@mallorn.com</A>></LI> | |
143 | <LI><em>Date</em>: Sun, 4 Jan 1998 22:33:31 -0600 (CST)</LI> | |
144 | <LI><em>List-Name</em>: mhonarc</LI> | |
145 | </UL> | |
146 | <PRE> | |
147 | > Hi... | |
148 | > | |
149 | > Has anyone come up with a relatively clean method of converting | |
150 | > majordomo digests to a mailbox format that MHonarc can read? | |
151 | > | |
152 | > I was looking at it, and from what I can see its just a matter of | |
153 | > changing the file so that there is a From <> line at the top of each | |
154 | > message, so that something like: | |
155 | ||
156 | If you have the procmail package, formail should do it for you. | |
157 | ||
158 | formail -ds < digestfile >> newmailbox | |
159 | ||
160 | It auto-generates the initial 'From ' header. Unfortunately, it | |
161 | also leaves the original digest message (probably). If it's the | |
162 | first message output, do this: | |
163 | ||
164 | formail +1 -ds < digestfile >> newmailbox | |
165 | ||
166 | This tells formail to skip the first message (the one that came from | |
167 | list-digest-owner or whatever). | |
168 | ||
169 | Chris | |
170 | </PRE> | |
171 | </BLOCKQUOTE> | |
172 | <BLOCKQUOTE> | |
173 | <hr noshade size=1> | |
174 | <UL> | |
175 | <LI><em>Subject</em>: Majordomo Digests to mbox format for MHonarc (perl script)</LI> | |
176 | <LI><em>From</em>: The Hermit Hacker <<A HREF="mailto:scrappy@hub.org">scrappy@hub.org</A>></LI> | |
177 | <LI><em>Date</em>: Sun, 4 Jan 1998 23:44:43 -0400 (AST)</LI> | |
178 | <LI><em>List-Name</em>: mhonarc</LI> | |
179 | </UL> | |
180 | <PRE> | |
181 | Hi... | |
182 | ||
183 | I've searched the archives for some brain dead simple way of bring in old | |
184 | digests so that MHonarc can use them, and couldn't find anything but some | |
185 | references to procmail and -msgsep...nothing which seemed to work "easily"... | |
186 | ||
187 | So, here is my contribution...a simple, brain dead script that takes a | |
188 | Majordomo digest and converts it to a format that can be used by MHonarc... | |
189 | I don't guarantee it, but if anyone can suggest what is wrong with it, I'd | |
190 | like to know and try to fix it | |
191 | ||
192 | Just run it as: <scriptname> <infile> > <outfile> | |
193 | ||
194 | Marc G. Fournier | |
195 | Systems Administrator @ hub.org | |
196 | primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org | |
197 | ||
198 | #!/usr/local/bin/perl | |
199 | $userid = getlogin(); | |
200 | ||
201 | $ii = 0; | |
202 | while (<>) { | |
203 | if($printline) { | |
204 | $line{$ii} = $_; | |
205 | $ii++; | |
206 | } | |
207 | if (/^----------------------------------------------------------------------/) { | |
208 | $printline = 1; | |
209 | $line{$ii} = "------------------------------"; | |
210 | $ii++; | |
211 | } | |
212 | } | |
213 | ||
214 | for($jj = 0; $jj < $ii; $jj++) { | |
215 | if(/^------------------------------/, $line{$jj}) { | |
216 | if($line{$jj+2} =~ "^Date:") { | |
217 | print "From $userid\n"; | |
218 | $jj += 2; | |
219 | } else { | |
220 | if($line{$jj+2} =~ "^End of") { | |
221 | exit; | |
222 | } | |
223 | } | |
224 | } | |
225 | print $line{$jj}; | |
226 | } | |
227 | ||
228 | </PRE> | |
229 | </BLOCKQUOTE> | |
230 | ||
231 | <!-- ??????????????????????????????????????????????????????????????? --> | |
232 | <hr noshade size=1> | |
233 | <table border=0> | |
234 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
235 | <h3><b><a name="listprocessor">Can MHonArc process Listprocessor archives?</a></b></h3> | |
236 | </td></tr></table> | |
237 | ||
238 | <p>An answer from a MHonArc user: | |
239 | </p> | |
240 | <blockquote> | |
241 | <UL> | |
242 | <LI><em>To</em>: <A HREF="mailto:mhonarc@rosat.mpe-garching.mpg.de">mhonarc@rosat.mpe-garching.mpg.de</A></LI> | |
243 | <LI><em>Subject</em>: re: digest to mbox</LI> | |
244 | <LI><em>From</em>: <A HREF="mailto:KMcCann@idrc.ca">KMcCann@idrc.ca</A></LI> | |
245 | <LI><em>Date</em>: 12 Jun 97 09:15:27 EDT</LI> | |
246 | <LI><em>List-Name</em>: mhonarc</LI> | |
247 | </UL> | |
248 | <!--X-Head-Body-Sep-Begin--> | |
249 | <!--X-Head-Body-Sep-End--> | |
250 | <!--X-Body-of-Message--> | |
251 | <PRE> | |
252 | Here is a simple script I wrote to process the archives of my Listprocessor | |
253 | lists. | |
254 | ||
255 | #!/usr/local/bin/perl5 | |
256 | # | |
257 | # mhonarch.pl - Process all Listprocessor archives using MHonArc | |
258 | # | |
259 | # Kevin McCann | |
260 | # | |
261 | #### Directory locations: | |
262 | # | |
263 | # Listproc, Majordomo, or Listserv top archives dir | |
264 | $ARCHDIR = "/usr/server/archives"; | |
265 | # | |
266 | # MhonArch web archives directory | |
267 | $MONDIR = "/u/www/htdocs/listproc/mhonarc"; | |
268 | # | |
269 | ## Let's figure out what lists exist | |
270 | opendir(DIR,"$ARCHDIR/") || die "Can't open directory"; | |
271 | @dirs = readdir(DIR); | |
272 | @sorteddirs = sort @dirs; | |
273 | closedir(DIR); | |
274 | for (@sorteddirs) { # processing a list | |
275 | $listname = $_; | |
276 | opendir(DIR,"$ARCHDIR/$listname") || die "Can't open directory"; | |
277 | @logs = readdir(DIR); | |
278 | @sortedlogs = sort @logs; | |
279 | closedir(DIR); | |
280 | for (@sortedlogs) { | |
281 | if (/log/) { # processing files with name format | |
282 | 'logYYMM' | |
283 | $log = $_; | |
284 | ||
285 | system("/usr/local/bin/mhonarc -outdir $MONDIR/$listname/$log | |
286 | $ARCHDIR/$listname/$log") | |
287 | ||
288 | # modify the above command line as needed | |
289 | } | |
290 | } | |
291 | } | |
292 | ||
293 | } # end of script | |
294 | ||
295 | ||
296 | I processed over 100 lists that go back to 1995 with this. It took about | |
297 | one hour. There may be more elegant ways to do it, but this was just a | |
298 | quick hack to get the job done. If you are using an RCFILE, don't forget to | |
299 | include it in the long mhonarc command seen above. Oh, and don't forget to | |
300 | change the first line that specifies your Perl location if you need to - | |
301 | mine is set to /usr/local/bin/perl5. | |
302 | ||
303 | Good luck! | |
304 | ||
305 | - Kevin McCann | |
306 | kmccann@idrc.ca | |
307 | www.cruciverb.com | |
308 | </PRE> | |
309 | </blockquote> | |
310 | ||
311 | <!-- ??????????????????????????????????????????????????????????????? --> | |
312 | <hr noshade size=1> | |
313 | <table border=0> | |
314 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
315 | <h3><b><a name="ezmlm">Can MHonArc process ezmlm archives?</a></b></h3> | |
316 | </td></tr></table> | |
317 | ||
318 | <p>From what I read from the <b>ezmlm(5)</b> manpage, the following example | |
319 | command will process all messages of list: | |
320 | </p> | |
321 | <pre> | |
322 | shell> <b>mhonarc <var>/list/archive/</var>[0-9]*</b> | |
323 | </pre> | |
324 | <p>Replace "<tt>/list/archive/</tt>" to what is appropriate for your | |
325 | configuration. | |
326 | </p> | |
327 | <p>Basically, each numeric subdirectory in the "<var>archive</var>" directory | |
328 | follows the same format as MH mail directories. | |
329 | </p> | |
330 | <p>If you are using a shell that cannot handle "<tt>[0-9]*</tt>", the following | |
331 | should work: | |
332 | </p> | |
333 | <pre> | |
334 | shell> <b>mhonarc `find <var>/list/archive/</var> -type d -name '[0-9]*' -print`</b> | |
335 | </pre> | |
336 | <p>Note, make sure to add any additional options to mhonarc as needed | |
337 | to get the effects you desire. | |
338 | </p> | |
339 | ||
340 | <!-- ??????????????????????????????????????????????????????????????? --> | |
341 | <hr noshade size=1> | |
342 | <table border=0> | |
343 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
344 | <h3><b><a name="maildir">Can MHonArc process qmail's maildir style mail folders?</a></b></h3> | |
345 | </td></tr></table> | |
346 | ||
347 | <p>For simplicity, let "<var>MAILDIR</var>" represent the pathname | |
348 | to your qmail mail directory. | |
349 | </p> | |
350 | <p>To have mhonarc process <var>MAILDIR</var>, | |
351 | you pass "<var>MAILDIR</var><tt>/cur</tt>" and/or | |
352 | "<var>MAILDIR</var><tt>/new</tt>" as the mail folder arguments. | |
353 | Which subdirectory you choose to use depends on your needs. | |
354 | </p> | |
355 | <p>Also, you will need to define the MHPATTERN resource to process | |
356 | all non-dotfiles. Example: | |
357 | </p> | |
358 | <pre> | |
359 | shell> <b>mhonarc -mhpattern '^[^\.]' <var>MAILDIR</var>/cur</b> | |
360 | </pre> | |
361 | <p>If all you will ever do is process qmail maildir folders, it may be best | |
362 | to set the M2H_MHPATTERN environment variable so you do not have | |
363 | to respecify each time you invoke mhonarc. Examples: | |
364 | </p> | |
365 | <dl> | |
366 | <dt>csh: | |
367 | <dd><b><tt>setenv M2H_MHPATTERN '^[^\.]'</tt></b> | |
368 | <dt>sh: | |
369 | <dd><b><tt>M2H_MHPATTERN='^[^\.]'; export M2H_MHPATTERN</tt></b> | |
370 | </dl> | |
371 | ||
372 | <!-- ??????????????????????????????????????????????????????????????? --> | |
373 | <hr noshade size=1> | |
374 | <table border=0> | |
375 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
376 | <h3><b><a name="netscape">Can MHonArc process Netscape Messenger folders?</a></b></h3> | |
377 | </td></tr></table> | |
378 | ||
379 | <p>Yes. Each Netscape Messenger folder has a corresponding mailbox file | |
380 | that stores the raw mail messages for the folder. The location | |
381 | of the mailbox file will be in your mail directory. Under Unix, this | |
382 | is normally <b><tt>$HOME/nsmail</tt></b>. For Windows, this is | |
383 | typically | |
384 | <b><tt>C:\Program Files\Netscape\Users\<var><username></var>\Mail</tt></b>. | |
385 | </p> | |
386 | ||
387 | <p>For each Netscape folder, there are two files: | |
388 | <b><tt><i><folder-name></i></tt></b> and | |
389 | <b><tt><i><folder-name></i>.summary</tt></b> (or | |
390 | <b><tt><i><folder-name></i>.snm</tt></b> under Windows). | |
391 | The <b><tt>.summary</tt></b> can be ignored with respect to MHonArc. | |
392 | The other file contains the raw mail messages and can be passed | |
393 | directly to MHonArc for processing. For example, to process all the | |
394 | mail in your Inbox, do something like the following: | |
395 | </p> | |
396 | <pre> | |
397 | shell> <b>mhonarc $HOME/nsmail/Inbox</b> | |
398 | </pre> | |
399 | ||
400 | <p>Note, you may need to compress/compact folders in Netscape before | |
401 | running MHonArc. If not, messages you have deleted from a folder may | |
402 | show up in the archive create by MHonArc. | |
403 | </p> | |
404 | ||
405 | <!-- ??????????????????????????????????????????????????????????????? --> | |
406 | <hr noshade size=1> | |
407 | <table border=0> | |
408 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
409 | <h3><b><a name="evolution">Can MHonArc process Evolution folders?</a></b></h3> | |
410 | </td></tr></table> | |
411 | ||
412 | <p>Yes. Each Evolution folder has a corresponding mailbox file | |
413 | that stores the raw mail messages for the folder. The location | |
414 | of the mailbox file will be in your mail directory which is | |
415 | typically <b><tt>$HOME/evolution/local/<em>folder-name</em></tt></b>. | |
416 | In the directory is a file called <tt>mbox</tt> which contains | |
417 | the raw messages that can be passed into MHonArc directly. | |
418 | </p> | |
419 | ||
420 | <!-- ??????????????????????????????????????????????????????????????? --> | |
421 | <hr noshade size=1> | |
422 | <table border=0> | |
423 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
424 | <h3><b><a name="compuserve">Can MHonArc process Compuserve messages?</a></b></h3> | |
425 | </td></tr></table> | |
426 | ||
427 | <p>Here is a response from a user: | |
428 | </p> | |
429 | <blockquote> | |
430 | <UL> | |
431 | <LI><em>Subject</em>: Re: CompuServe --> html</LI> | |
432 | <LI><em>From</em>: Steve Pacenka <<A HREF="mailto:sp17@cornell.edu">sp17@cornell.edu</A>></LI> | |
433 | <LI><em>Date</em>: Thu, 06 Mar 1997 09:09:00 -0500</LI> | |
434 | </UL> | |
435 | <PRE> | |
436 | At 11:38 AM 3/6/97 +0100, Bernard Frit wrote: | |
437 | ><i>Hi everybody,</i> | |
438 | > | |
439 | ><i>A friend of mine has a lot of archives in CompuServe</i> | |
440 | ><i>thread and message format. He'd like to convert them</i> | |
441 | ><i>in a convenient format (html or whatever) with thread</i> | |
442 | ><i>indexing features as MHonArc is doing it for mail</i> | |
443 | ><i>archives.</i> | |
444 | > | |
445 | ><i>At the first glance, I didn't find out how to configure</i> | |
446 | ><i>MHonArc to do the job.</i> | |
447 | ||
448 | The Compuserve "file cabinet" format is too far from the basic SMTP message | |
449 | format that MHonArc recognizes. | |
450 | ||
451 | Your friend can find software on Compuserve to read the file cabinet format | |
452 | and emit ascii text that is closer to SMTP message format that MHonArc can | |
453 | use. A search of IBMFF using the keywords "cabinet" and "convert" yielded | |
454 | several items including these two: | |
455 | ||
456 | Forum Name: CSNAVSUPPORT Library: Member Uploads (6) | |
457 | Accesses: 839 Size: 11368 | |
458 | File: THRDCO.ZIP Submitted: [72662,70] 26-Aug-94 | |
459 | ||
460 | ||
461 | This program converts forum message threads to a plain text file called | |
462 | COLLECT.TXT. Your favorite word processor can then search for any message | |
463 | on any topic that you have downloaded. It is public domain and was | |
464 | created because I have so many forum thread messages which I can't search. | |
465 | ||
466 | ----- | |
467 | Forum Name: PCEFORUM Library: Telecom/Reseaux (8) | |
468 | Accesses: 32 Size: 30865 | |
469 | File: SHWCIM.ZIP Submitted: [72241,2132] 08-Nov-96 | |
470 | ||
471 | Une fois stockes dans le "Cabinet" CompuServe, les messages des forums et | |
472 | les courriers sont codes dans des fichiers binaires que l'on ne peut pas | |
473 | relire directement. Cet utilitaire a pour but de convertir n'importe quel | |
474 | fichier de la base WinCIM en fichier ASCII pur. Freeware en anglais. | |
475 | ||
476 | -- SP | |
477 | ||
478 | </PRE> | |
479 | </blockquote> | |
480 | ||
481 | <!-- ??????????????????????????????????????????????????????????????? --> | |
482 | <hr noshade size=1> | |
483 | <table border=0> | |
484 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
485 | <h3><b><a name="otherformats">What about other mailbox/folder formats?</a></b></h3> | |
486 | </td></tr></table> | |
487 | ||
488 | <p>The common technique is to convert the foreign format into | |
489 | a format recognized by MHonArc: UUCP mailbox or MH mail folders. The | |
490 | conversion can also rely on the usage of the MSGSEP and MHPATTERN | |
491 | resources to make conversion potentially easier. | |
492 | </p> | |
493 | <p>A potential source for help is | |
494 | <a href="http://mango.human.cornell.edu/kens/MoreFAQ.html#Convert" | |
495 | ><http://mango.human.cornell.edu/kens/MoreFAQ.html#Convert></a>. The | |
496 | URL is part of the Eudora FAQ. However, Eudora does uses UUCP-style | |
497 | mailbox format to store its messagse. Hence, the information | |
498 | provided from the URL can be applicable to MHonArc. | |
499 | </p> | |
500 | ||
501 | <!-- ??????????????????????????????????????????????????????????????? --> | |
502 | <hr noshade size=1> | |
503 | <table border=0> | |
504 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
505 | <h3><b><a name="nonenglish">Can MHonArc create non-English archives?</a></b></h3> | |
506 | </td></tr></table> | |
507 | ||
508 | <p>Yes. With MHonArc's page layout customizations features, | |
509 | you can have MHonArc create pages in any language supported | |
510 | by Web client software. Plus, messages containing non-English text | |
511 | is supported during message conversion via the CHARSETCONVERTERS | |
512 | resource. | |
513 | </p> | |
514 | ||
515 | <dl> | |
516 | <dt>See also:</dt> | |
517 | <dd><a href="#unicde" | |
518 | >Does MHonArc support Unicode?</a></dd> | |
519 | </dl> | |
520 | ||
521 | <!-- ??????????????????????????????????????????????????????????????? --> | |
522 | <hr noshade size=1> | |
523 | <table border=0> | |
524 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
525 | <h3><b><a name="bilingual">Can I create bilingual archives?</a></b></h3> | |
526 | </td></tr></table> | |
527 | ||
528 | <p>Yes. You can actually create archives that have as many | |
529 | indexes as you want in as many languages that you want. Through | |
530 | the OTHERINDEXES resource can define any number of extra indexes | |
531 | to create. For each index, you can redfine the index resources | |
532 | to use whatever text (English or non-English) you desire. | |
533 | </p> | |
534 | <dl> | |
535 | <dt><strong>NOTE</strong></dt> | |
536 | <dd><p>There is no support for mulitple variations of message | |
537 | pages in an archive. Therefore, a single language must be | |
538 | chosen for message pages, or you can include redundant information | |
539 | using multiple languages. | |
540 | </p> | |
541 | </dd> | |
542 | </dl> | |
543 | <dl> | |
544 | <dt><strong>NOTE</strong></dt> | |
545 | <dd><p>Actual message data will be in the language used in the | |
546 | message. MHonArc has no built-in language translation. | |
547 | </p> | |
548 | </dd> | |
549 | </dl> | |
550 | ||
551 | <dl> | |
552 | <dt>See also:</dt> | |
553 | <dd><a href="#unicde" | |
554 | >Does MHonArc support Unicode?</a></dd> | |
555 | </dl> | |
556 | ||
557 | <!-- ??????????????????????????????????????????????????????????????? --> | |
558 | <hr noshade size=1> | |
559 | <table border=0> | |
560 | <tr valign=top><td><img src="monicon.png" align="bottom" alt=""></td><td> | |
561 | <h3><b><a name="unicode">Does MHonArc support Unicode?</a></b></h3> | |
562 | </td></tr></table> | |
563 | ||
564 | <p>Not directly, but it is possible to have MHonArc generate | |
565 | UTF-8 HTML pages. See the <tt>utf-8.mrc</tt> example resource | |
566 | file in the <cite>Appendix: Resource File Examples</cite> section | |
567 | of the documentation for more information and caveats. | |
568 | </p> | |
569 | ||
570 | <!-- ===================================================================== --> | |
571 | <hr> | |
572 | ||
573 | <!--X-NavButtons-Start--> | |
574 | <p align=center> | |
575 | [<a href="general.html">Prev</a>][<a href="usage.html">Next</a>][<a href="faq.html">TOC</a>][<a href="http://www.mhonarc.org/">Home</a>] | |
576 | </p> | |
577 | <!--X-NavButtons-End--> | |
578 | ||
579 | <hr> | |
580 | <address> | |
581 | $Date: 2002/07/20 00:48:48 $ <br> | |
582 | <img align="top" src="monicon.png" alt=""> | |
583 | <a href="http://www.mhonarc.org/" | |
584 | ><strong>MHonArc</strong></a><br> | |
585 | Copyright © 1997-1999, <a href="http://www.earlhood.com/" | |
586 | >Earl Hood</a>, <a href="mailto:mhonarc@mhonarc.org" | |
587 | >mhonarc@mhonarc.org</a><br> | |
588 | </address> | |
589 | </body> | |
590 | </html> |