mirror of
https://github.com/fadden/ciderpress.git
synced 2024-11-23 11:33:58 +00:00
250d1043e3
The original version of CiderPress used a WinHelp help file, built with an application called HelpMatic Pro. This app used a proprietary format, and had no facility for exporting to "raw" HPJ + RTF files, so I decompiled the HLP and imported it into HelpScribble. Using HelpScribble, I cleaned up the help file formatting a little, fixed up the table of contents, and exported as "raw" HtmlHelp (HHP, HHK, HHC, and a whole bunch of HTML). I also split the pop-up help text, which isn't supported by HelpScribble, into a separate text file that Microsoft's HTML Help Workshop understands. I'm checking in the files that HTML Help Workshop needs to generate a CHM, so anyone can update the help text. I'm also checking in the CHM file, rather than adding the help workshop to the build, so that it's not necessary to download and configure the help workshop to build CiderPress. This change adds all of the updated help, but only updates the Help and question mark button actions for one specific dialog. A subsequent change will update the rest of the dialogs. This change is essentially upgrading us from a totally obsolete help system to a nearly-obsolete help system, but the systems are similar enough to make this a useful half-step on the way to something else. The code will centralize help activation in a pair of functions in the main app class, so any future improvements should be more limited in scope. This also adds a build step to copy the CHM to the execution directory.
32 lines
4.4 KiB
HTML
32 lines
4.4 KiB
HTML
<HTML><HEAD>
|
|
|
|
<TITLE>List - Pathname</TITLE>
|
|
<OBJECT TYPE="application/x-oleobject" CLASSID="clsid:1e2a7bd0-dab9-11d0-b93a-00c04fc99f9e">
|
|
<PARAM NAME="Keyword" VALUE="pathname">
|
|
</OBJECT>
|
|
<META NAME="AUTHOR" CONTENT="Copyright (C) 2014 by CiderPress authors">
|
|
<META NAME="GENERATOR" CONTENT="HelpScribble 7.8.8">
|
|
<STYLE> span { display: inline-block; }</STYLE>
|
|
</HEAD>
|
|
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080" ALINK="#FF0000">
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="4">List - Pathname</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">The full pathname of the file. In disk archives that don't support folders (DOS 3.2/3.3, Pascal, CP/M, RDOS), this is just the filename. For ProDOS disks and ShrinkIt archives, the pathname includes all folders out to the "root" of the collection.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">The names are usually presented exactly as they appear in the original, but there are a few exceptions:</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<UL STYLE="margin-top:0;margin-bottom:0;margin-left:10pt;"><LI><FONT FACE="MS Sans Serif" SIZE="2">ProDOS names are converted to lower case based on the case flags. These were added in ProDOS 8 v1.8 to allow the GS/OS FST to put lower case and spaces in names.</FONT>
|
|
<LI><FONT FACE="MS Sans Serif" SIZE="2">AppleWorks filenames stored on a ProDOS disk are converted to lower case based on the aux type. This value overrides the ProDOS flags. (AppleWorks files stored in ShrinkIt archives are simply presented as they were stored.)</FONT>
|
|
<LI><FONT FACE="MS Sans Serif" SIZE="2">The names of files on DOS 3.3 volumes are "sanitized", so that inverse and flashing characters are converted to normal text.</FONT>
|
|
<LI><FONT FACE="MS Sans Serif" SIZE="2">If the appropriate <A HREF="t19.htm">preference</A> is enabled, filenames stored on DOS 3.3 volumes are converted to mixed case based on common rules for English titles. Filenames with lower case in them already -- uncommon but not unheard-of -- are left alone.</FONT>
|
|
<LI><FONT FACE="MS Sans Serif" SIZE="2">If the appropriate preference is enabled, all filenames have spaces converted to underscores. This could be useful for files destined to be served directly from a web site.</FONT></UL>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">The ProDOS volume name is not shown as part of the pathname, except in the entry for the volume directory itself (identifiable as a pathname starting with ':').</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">There may be one of four icons to the left of the filename. A document icon that is "empty" (has a white interior) indicates a ShrinkIt archive entry with an empty comment. Most archives created by GS/ShrinkIt have an empty comment added to the first entry, so this is fairly common. If the document icon is solid yellow, that means there is a comment with information in it. This can be viewed with the <A HREF="t54.htm">file viewer</A> or by using the "<A HREF="t43.htm">edit comment</A>" feature. A red 'X' icon indicates a damaged entry, usually on a disk image. CiderPress was unable to fully process the file, so it has been marked as unavailable. A blue '?' icon indicates a suspicious entry; it's not unreadable, but it doesn't look healthy.</FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2"> </FONT></P>
|
|
<P STYLE="margin-top:0;margin-bottom:0;"><FONT FACE="MS Sans Serif" SIZE="2">Files in a sub-volume, such as a DOS 3.3 disk embedded in a ProDOS disk, are shown as being in a folder (something like "_DOS001"). This is done so that the files will be extracted into a separate folder from the outer-volume content, and also to keep the files grouped together when the file list is sorted by name.
|
|
</FONT>
|
|
</P>
|
|
</BODY></HTML>
|