Creating MKS_SHELL_BRANCH, rooted at MKS_SHELL_BASE. This branch

works with the sh.exe in MKS Toolkit.


git-svn-id: svn://10.0.0.236/branches/MKS_SHELL_BRANCH@1101 18797224-902f-48f8-a5cc-f745e15eee43

CVSROOT/modules

@@ -1,293 +0,0 @@
-# Three different line formats are valid:
-#	key	-a    aliases...
-#	key [options] directory
-#	key [options] directory files...
-#
-# Where "options" are composed of:
-#	-i prog		Run "prog" on "cvs commit" from top-level of module.
-#	-o prog		Run "prog" on "cvs checkout" of module.
-#	-e prog		Run "prog" on "cvs export" of module.
-#	-t prog		Run "prog" on "cvs rtag" of module.
-#	-u prog		Run "prog" on "cvs update" of module.
-#	-d dir		Place module in directory "dir" instead of module name.
-#	-l		Top-level directory only -- do not recurse.
-#
-# NOTE:  If you change any of the "Run" options above, you'll have to
-# release and re-checkout any working directories of these modules.
-#
-# And "directory" is a path to a directory relative to $CVSROOT.
-#
-# The "-a" option specifies an alias.  An alias is interpreted as if
-# everything on the right of the "-a" had been typed on the command line.
-#
-# You can encode a module within a module by using the special '&'
-# character to interpose another module into the current module.  This
-# can be useful for creating a module that consists of many directories
-# spread out over the entire source repository.
-
-MozillaSource -a \
-	MozillaSourceWin \
-	MozillaSourceMac \
-	MozillaSourceUnix \
-
-MozillaSourceWin -a MozillaSourceCommon MozillaSourceWinOnly
-
-MozillaSourceMac -a MozillaSourceCommon MozillaSourceMacOnly
-
-MozillaSourceUnix -a MozillaSourceCommon MozillaSourceUnixOnly
-
-MozillaSourceCommon -a \
-    mozilla/LEGAL  \
-    mozilla/LICENSE  \
-    mozilla/CHANGES.html  \
-    mozilla/build  \
-    mozilla/include  \
-    mozilla/jpeg  \
-    mozilla/js  \
-    mozilla/lib/htmldlgs  \
-    mozilla/lib/layout  \
-    mozilla/lib/libcnv  \
-    mozilla/lib/libi18n  \
-    mozilla/lib/liblayer  \
-    mozilla/lib/libmisc  \
-    mozilla/lib/libmime  \
-    mozilla/lib/libmocha \
-    mozilla/lib/libnet  \
-    mozilla/lib/libparse  \
-    mozilla/lib/libpics  \
-    mozilla/lib/libpwcac  \
-    mozilla/lib/libstyle  \
-    mozilla/lib/plugin  \
-    mozilla/lib/xlate \
-    mozilla/lib/xp  \
-    mozilla/modules/edtplug/classes  \
-    mozilla/modules/edtplug/src  \
-    mozilla/modules/edtplug/include \
-    mozilla/modules/libfont/classes  \
-    mozilla/modules/libfont/public  \
-    mozilla/modules/libfont/src  \
-    mozilla/modules/libhook  \
-    mozilla/modules/libimg  \
-    mozilla/modules/libpref  \
-    mozilla/modules/libreg  \
-    mozilla/modules/libutil  \
-    mozilla/modules/progress/src  \
-    mozilla/modules/rdf  \
-    mozilla/modules/schedulr  \
-    mozilla/modules/security/freenav  \
-    mozilla/modules/softupdt/classes  \
-    mozilla/modules/softupdt/include  \
-    mozilla/modules/softupdt/src  \
-    mozilla/modules/xml  \
-    mozilla/modules/zlib/src  \
-    mozilla/nav-java/stubs  \
-    mozilla/nsprpub  \
-    mozilla/xpcom \
-    mozilla/l10n \
-    mozilla/nsprpub \
-    mozilla/dbm  \
-    mozilla/modules/schedulr  \
-    README 
-
-MozillaSourceWinOnly -a \
-    mozilla/client.mak  \
-    mozilla/cmd/makefile.win  \
-    mozilla/cmd/dialup  \
-    mozilla/cmd/wincom  \
-    mozilla/cmd/winfe  \
-    mozilla/config  \
-    mozilla/lib/makefile.win  \
-    mozilla/modules/coreincl  \
-    mozilla/modules/edtplug/makefile.win  \
-    mozilla/makefile.win  \
-    mozilla/modules/libfont/jmcgen  \
-    mozilla/modules/libfont/makefile.win  \
-    mozilla/modules/libfont/producers/makefile.win  \
-    mozilla/modules/libfont/producers/win  \
-    mozilla/modules/libfont/producers/win/classes  \
-    mozilla/modules/libfont/producers/win/classes/netscape  \
-    mozilla/modules/libfont/producers/win/classes/netscape/fonts  \
-    mozilla/modules/libfont/producers/win/src  \
-    mozilla/modules/makefile.win  \
-    mozilla/modules/progress/makefile.win  \
-    mozilla/modules/progress/public  \
-    mozilla/modules/security/makefile.win  \
-    mozilla/modules/softupdt/makefile.win  \
-    mozilla/modules/zlib/makefile.win  \
-    mozilla/nav-java/makefile.win  \
-    JavaStubWin
-
-
-MozillaSourceUnixOnly -a \
-    mozilla/cmd/Makefile  \
-    mozilla/cmd/stubfe  \
-    mozilla/cmd/xfe  \
-    mozilla/config/.cvsignore  \
-    mozilla/config/AIX.mk  \
-    mozilla/config/BSD_OS.mk  \
-    mozilla/config/bsdecho.c  \
-    mozilla/config/bsdecho.c  \
-    mozilla/config/clobber_miss.pl  \
-    mozilla/config/clobber_miss.pl  \
-    mozilla/config/common.mk  \
-    mozilla/config/common.mk  \
-    mozilla/config/config.guess  \
-    mozilla/config/config.mk  \
-    mozilla/config/coreconf.mk  \
-    mozilla/config/coreconf.mk  \
-    mozilla/config/cvsco.pl  \
-    mozilla/config/cvsco.pl  \
-    mozilla/config/fastcwd.pl  \
-    mozilla/config/fastcwd.pl  \
-    mozilla/config/FreeBSD.mk  \
-    mozilla/config/gtscc.c  \
-    mozilla/config/HP-UX.mk  \
-    mozilla/config/IRIX.mk  \
-    mozilla/config/Linux.mk  \
-    mozilla/config/makecopy.c  \
-    mozilla/config/makecopy.c  \
-    mozilla/config/Makefile  \
-    mozilla/config/Makefile  \
-    mozilla/config/mangle.c  \
-    mozilla/config/mangle.c  \
-    mozilla/config/mantomak.c  \
-    mozilla/config/mantomak.c  \
-    mozilla/config/mkdepend  \
-    mozilla/config/NCR.mk  \
-    mozilla/config/NEC.mk  \
-    mozilla/config/NEWS-OS.mk  \
-    mozilla/config/NEXTSTEP.mk  \
-    mozilla/config/nfspwd.pl  \
-    mozilla/config/nfspwd.pl  \
-    mozilla/config/nodl.pl  \
-    mozilla/config/nodl.pl  \
-    mozilla/config/nsinstall.c  \
-    mozilla/config/nsinstall.c  \
-    mozilla/config/OSF1.mk  \
-    mozilla/config/outofdate.pl  \
-    mozilla/config/outofdate.pl  \
-    mozilla/config/pathsub.c  \
-    mozilla/config/pathsub.c  \
-    mozilla/config/pathsub.h  \
-    mozilla/config/pathsub.h  \
-    mozilla/config/pkg2dpth.pl  \
-    mozilla/config/pkg2dpth.pl  \
-    mozilla/config/ports  \
-    mozilla/config/revdepth.pl  \
-    mozilla/config/revdepth.pl  \
-    mozilla/config/Rhapsody.mk  \
-    mozilla/config/rules.mk  \
-    mozilla/config/SCOOS.mk  \
-    mozilla/config/SINIX.mk  \
-    mozilla/config/sj.pl  \
-    mozilla/config/sj.pl  \
-    mozilla/config/SunOS.mk  \
-    mozilla/config/SunOS4.mk  \
-    mozilla/config/SunOS5.mk  \
-    mozilla/config/UNIXWARE.mk  \
-    mozilla/config/xmversion.sh  \
-    mozilla/lib/Makefile  \
-    mozilla/Makefile  \
-    mozilla/modules/edtplug/Makefile  \
-    mozilla/modules/libfont/jmcgen  \
-    mozilla/modules/libfont/Makefile  \
-    mozilla/modules/libfont/producers/Makefile  \
-    mozilla/modules/Makefile  \
-    mozilla/modules/progress/Makefile  \
-    mozilla/modules/progress/public  \
-    mozilla/modules/security/Makefile  \
-    mozilla/modules/softupdt/Makefile  \
-    mozilla/modules/zlib/Makefile  \
-    mozilla/nav-java/Makefile  \
-    mozilla/lib/mariner  \
-    JavaStubUnix
-
-
-MozillaSourceMacOnly -a \
-    mozilla/cmd/dialup  \
-    mozilla/cmd/macfe \
-    mozilla/lib/mac/AutoAdmin  \
-    mozilla/lib/mac/Includes  \
-    mozilla/lib/mac/MacMemoryAllocator  \
-    mozilla/lib/mac/Misc  \
-    mozilla/lib/mac/MoreFiles  \
-    mozilla/lib/mac/NSRuntime  \
-    mozilla/lib/mac/NSStdLib  \
-    mozilla/lib/mac/patches  \
-    mozilla/lib/mac/PowerPlant  \
-    mozilla/lib/mac/UserInterface  \
-    mozilla/modules/coreincl  \
-    mozilla/modules/edtplug/macbuild  \
-    mozilla/modules/libfont/jmcgen/include  \
-    mozilla/modules/libfont/jmcgen/src  \
-    mozilla/modules/libfont/macbuild  \
-    mozilla/modules/progress/macbuild  \
-    mozilla/modules/progress/public  \
-    mozilla/modules/softupdt/macbuild  \
-    mozilla/modules/zlib/macbuild  \
-    mozilla/lib/mariner  \
-    JavaStubMac
-
-JavaStubAll -a \
-	JavaStubWin \
-	JavaStubMac \
-	JavaStubUnix
-
-JavaStubCore -a \
-	mozilla/sun-java/stubs/include \
-	mozilla/sun-java/stubs/src
-
-JavaStubMac -a \
-	JavaStubCore \
-	mozilla/sun-java/stubs/macbuild \
-	mozilla/sun-java/stubs/macjri
-
-JavaStubUnix -a \
-	JavaStubCore \
-	mozilla/sun-java/Makefile \
-	mozilla/sun-java/stubs/jri \
-	mozilla/sun-java/stubs/Makefile
-
-JavaStubWin -a \
-	JavaStubCore \
-	mozilla/sun-java/makefile.win \
-	mozilla/sun-java/stubs/jri \
-	mozilla/sun-java/stubs/makefile.win
-
-######################################################################
-
-#
-# Modules for the raptor layout effort. Note that raptor dist is temporary
-# until raptor is integrated into the mainline build.
-#
-
-RaptorDist -a \
-	mozilla/nsprpub \
-	mozilla/include \
-	mozilla/jpeg \
-	mozilla/modules/libreg \
-	mozilla/xpcom \
-	mozilla/modules/zlib \
-	mozilla/modules/libutil \
-	mozilla/sun-java \
-	mozilla/nav-java \
-	mozilla/js \
-	mozilla/modules/security/freenav \
-	mozilla/modules/libpref \
-	mozilla/modules/libimg \
-	mozilla/lib/xp \
-	mozilla/lib/libnet \
-	mozilla/base
-
-Raptor -a \
-	mozilla/htmlparser \
-	mozilla/dom \
-	mozilla/gfx \
-	mozilla/view \
-	mozilla/widget \
-	mozilla/layout \
-	mozilla/webshell
-
-RaptorAll -a \
-	RaptorDist  \
-	Raptor

README/mozilla/macbuild.htm

@@ -1,875 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=x-mac-roman">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 (Macintosh; I; PPC) [Netscape]">
-   <TITLE>MacFE Build Instructions</TITLE>
-<!--This file created 3/17/98 9:38 PM by Claris Home Page version 3.0 30 Day Trial-->
-</HEAD>
-<BODY BGCOLOR="#FFFFFF">
-
-<H1>
-MacFE Build Instructions</H1>
-This is a general document on how to build, what works, what doesn't, and
-things to watch out for when working on the Mac client. <B>Please read
-the entire document before you start tinkering</B>...heck, you may just
-learn something!
-
-<P>Abbreviations you will probably see in this document:
-<UL>
-<LI>
-<B>MacFE</B> - the Macintosh front end, including all the things you see
-and some you don't.</LI>
-
-<LI>
-<B>XP</B> - cross platform back end code, mostly written in C. You will
-see this used like, "This is an XP problem" which means it's broken everywhere.</LI>
-
-<LI>
-<B>MW</B> - Metrowerks Corporation. They make our build tools (CodeWarrior)
-and PowerPlant</LI>
-
-<LI>
-<B>PP</B> - PowerPlant, the GUI framework on which our app is built</LI>
-
-<LI>
-<B>CWProX</B> - CodeWarrior Pro version X. You'll probably see CWPro1,
-CWPro2, and CWPro3. We may also just refer to this as <B>CW</B>.</LI>
-
-<LI>
-<B>IDE</B> - Integrated Development Environment. CodeWarrior is an IDE.</LI>
-
-<BR><!--<LI>
-<B>NC</B> - the working name for our Aurora technology, the Navigation
-Center.</LI>
-
-<LI>
-<B>HT</B> - HyperTree, a layer of XP APIs over RDF on which the NavCenter
-is built.</LI>--></UL>
-
-<H3>
-<A HREF="#Building">Building</A></H3>
-<!--<H3>
-<A HREF="#NewFeatures">New 5.0 Features</A></H3>
-
-<H3>
-<A HREF="#Unfinished">Unfinished Features</A></H3>-->
-<H3>
-<A HREF="#Pitfalls">Pitfalls</A></H3>
-
-<H3>
-<A HREF="#HistFuture">History and Future</A></H3>
-
-<H2>
-
-<HR><A NAME="Building"></A>Building</H2>
-
-<H4>
-What are the minimum machine requirements?</H4>
-To build Navigator, you need a fast PPC Mac. The faster the better. You
-can't build with a 68K machine because we have too many resources, and
-the build process will crash when trying to generate resources out of our
-cross-platform strings. See the discussion below for a way around this.
-
-<P>You will need about 96 MB of physical RAM to "fast link" the app. You
-can still fast link if you give your machine 96 MB of virtual memory, but
-then the VM hit is large enough to counteract any improvement. One of our
-beta testers had a machine with only 64MB of physical RAM (VM was off)
-and it ran out of memory trying to link. Turning VM on got it to link,
-but build time increased greatly.
-
-<P>The moral of the story: get lots of physical RAM and don't use VM.
-<H4>
-How big of a partition do I need for the source?</H4>
-You should be ok with a 400MB disk partition, even when fully built. This
-does not include tools like the IDE, just source.
-<H4>
-Why do I need CWPro2 or better?</H4>
-We use CodeWarrior as our development environment at Netscape for the MacFE.
-All of the projects and tools are geared towards the CodeWarrior IDE. In
-addition, we make heavy use of PowerPlant and MSL which you can only get
-from Metrowerks.
-
-<P>While we say you need at least CWPro2, you may be able to get by with
-Pro1, but probably not for very long. We haven't tested it, so we don't
-recommend it. Get the upgrade. CodeWarrior kicks serious butt!
-<H4>
-How do I setup my development environment?</H4>
-Here's a list of 3rd party <B>software</B> that we compile into the application
-and where to get it:
-<UL>
-<LI>
-PowerPlant 1.8 - obtainable from the CodeWarrior CD.</LI>
-
-<LI>
-MSL - the Metrowerks Standard Library, obtainable from the CodeWarrior
-CD</LI>
-
-<LI>
-<A HREF="ftp://ftp.boingo.com//dan/WASTE/waste-13.hqx">WASTE 1.3</A></LI>
-
-<LI>
-<A HREF="http://www.bact.wisc.edu/CWASTEEdit/CWASTEEdit.sit.hqx">CWASTE
-1.6.2</A></LI>
-
-<LI>
-<A HREF="ftp://ftp.scripting.com/userland/menuSharingToolkit4.1.sit.hqx">Menu
-Sharing Toolkit</A> (from UserLand)</LI>
-
-<LI>
-<A HREF="ftp://ftp.digitalalchemy.com/pub/digitalalchemy/mercutio-SDK.sit.bin">Mercutio
-1.5 SDK</A> (only download the SDK, not the entire package, else the access
-paths will be wrong)</LI>
-
-<LI>
-<A HREF="ftp://ftp.share.com/pub/internet-configuration/ICProgKit1.4.sit">Internet
-Config 1.4 SDK</A></LI>
-
-<LI>
-<A HREF="http://www.mooseyard.com/Jens/Software/">AEGizmos 1.4.2</A></LI>
-</UL>
-Here's a list of other build <B>tools</B> that you need to install in order
-to build and where to get them:
-<UL>
-<LI>
-<A HREF="ftp://sunsite.cnlab-switch.ch/software/platform/macos/perl/Mac_Perl_519r4_tool.bin">MacPerl
-5 MPW Tool</A></LI>
-
-<LI>
-MakeStub - MPW (installed with CodeWarrior Heaven option). If you choose
-not to install MPW, it is located on the MacOS Tools CD in "CW Pro 2 Tools:CodeWarrior
-MPW:MPW:Tools"</LI>
-
-<LI>
-RunTSScript - in Mozilla source distribution (ns:build:mac:RunTSScript),
-needs to be installed by hand</LI>
-
-<LI>
-<A HREF="ftp://dev.apple.com/devworld/Tool_Chest/Core_Mac_OS_Tools/MPW_etc./MPW-GM/MPW/ToolServer.sit.hqx">ToolServer</A>
-- or in the CW distribution (CW Pro 2 Tools:Apple Development Tools:ToolServer
-3.4.1.sit). <B>We recommend pulling it off the CD</B> because it comes
-with configuration files for CodeWarrior which you would have to create
-manually were you to pull it off the net.</LI>
-
-<LI>
-<A HREF="ftp://dev.apple.com/devworld/Periodicals/develop/develop25/develop_Issue_25_code/ToolFrontEnd.sit.hqx">ToolFrontEnd</A></LI>
-
-<LI>
-<A HREF="http://sunsite.cnlab-switch.ch/ftp/software/platform/macos/src/HTML/MPW_C.html">patch
-2.1</A></LI>
-</UL>
-Once you have all the pieces, here are the steps required to put everything
-together:
-<OL>
-<LI>
-Install CodeWarrior from the CD. While it is large, installing the "CodeWarrior
-Heaven" option will guarantee that you have everything you need. This will
-give you PowerPlant, MSL, and MPW. If you choose to install less, proceed
-at your own risk.</LI>
-
-<LI>
-In the Finder, increase the memory partition of the IDE to 15MB (you can
-get by with 12, if need be).</LI>
-
-<LI>
-Download ToolFrontEnd. After expanding it, in "ToolFrontEnd Folder:Drop-Ins"
-there are three items:</LI>
-
-<UL>
-<LI>
-<I>#include</I></LI>
-
-<LI>
-<I>ToolFrontEnd</I></LI>
-
-<LI>
-<I>ToolFrontEnd Panel</I></LI>
-</UL>
-Create a folder named "Include Scanners". Place the file "#include" into
-the Include Scanners folder. Move the Include Scanners folder to the CodeWarrior
-Plugins folder. Create a folder named "ToolFrontEnd". Place the files "ToolFrontEnd"
-and "ToolFrontEnd Panel" into the ToolFrontEnd folder. Place this folder
-in the CodeWarrior Plugins folder.
-
-<P>Open "ToolFrontEnd Panel" with ResEdit. Change the file type from 'Panl'
-to 'PanL'. Save.
-<LI>
-Uncompress the StuffIt Archive for ToolServer. Place the ToolServer folder
-in the same folder as your CodeWarrior environment (its actual placement
-is not important). Create an alias from the Tools folder that lives in
-the CodeWarrior MPW distribution and place it in the ToolServer folder.
-Now ToolServer and MPW will share the same tool set and you only have to
-maintain one tool repository.</LI>
-
-<LI>
-After installing the MacPerl distribution (run the InstallerVISE application),
-in the "MacPerl €" folder, there will be an MPW tool named "perl". Install
-this in the same location as the rest of the MPW tools for ToolServer.</LI>
-
-<LI>
-Install the "patch" and "MakeStub" MPW Tools in the same location. Note
-that "MakeStub" is automatically installed by the "CodeWarrior Heaven"
-install option.</LI>
-
-<LI>
-Install RunTSScript (found in the Mozilla source distribution) in the compilers
-folder in your build environment</LI>
-
-<LI>
-Next, after downloading all the 3rd party software components, drag WASTE,
-CWASTE, Menu Sharing, Mercutio, Internet Config, and the AEGizmo folders
-(just as they are) into the "MacOS Support" folder in your build environment.</LI>
-
-<LI>
-Start ToolServer from within CodeWarrior (or use MPW if you are brave enough).
-We're about to patch some files. Make sure the ToolServer menu is in the
-CodeWarrior menu bar by turning on the <A HREF="../../../IDEPrefs.gif">preference</A>
-under the "Extras" panel in the IDE Preferences (not the project preferences!).
-The menu bar should look like this:</LI>
-
-
-<P><IMG SRC="IDEMenuBar.gif" X-CLARIS-USEIMAGEWIDTH X-CLARIS-USEIMAGEHEIGHT HEIGHT=20 WIDTH=359 ALIGN=BOTTOM>
-
-<P>Choose "Start ToolServer" from the ToolServer menu (this is the icon
-menu between "Window" and "Help" in the menubar above). You will now see
-a window with no close box. This is your ToolServer Worksheet where you
-will type (or cut &amp; paste) the commands for the following steps.
-
-<P>In case you have never used MPW/ToolServer before, the following is
-<B>very important</B>. Pressing "return" does not execute commands like
-you might think. It just inserts a newline into the worksheet like a normal
-text editor. <B>To actually get ToolServer to execute the command, you
-must press "Enter" (lower right of numeric keypad).</B> This executes the
-line that the cursor is on, and only that line. If you want to execute
-multiple lines at once, select them all and hit Enter.
-<LI>
-Set the shell variables {IDE} and {Source} to the correct paths for your
-build environment. {IDE} is where your CodeWarrior IDE is located. {Source}
-is the folder containing the toplevel "ns" folder of the Mozilla source.
-Mine look like this (don't forget to keep the quotes if your path includes
-spaces), yours will almost certainly be different:</LI>
-
-<PRE>Set IDE "Develop:Source331 Build Environment:CW Pro 2:Metrowerks CodeWarrior:"
-Set Source "Source:FreeSource:"</PRE>
-
-<LI>
-If you are using CWPro2, execute the following lines to patch LDropFlag
-to draw correcly over non-white backgrounds. <B>You do not have to do this
-if you are using Pro3</B> because it has been fixed.</LI>
-
-<PRE>directory "{IDE}MacOS Support:PowerPlant:_In Progress:_Table Classes:"
-patch LDropFlag.cp "{Source}ns:lib:mac:patches:LDropFlag.patch"
-duplicate -y "{Source}ns:lib:mac:patches:DropFlag Icons.rsrc" "{IDE}MacOS Support:PowerPlant:PowerPlant Resources:"</PRE>
-
-<LI>
-Execute the following lines to patch menusharing.c to allow it to compile
-with the new Universal Headers. It references an obsolete header file (GestaltEqu.h).</LI>
-
-<PRE>directory "{IDE}MacOS Support:Menu Sharing Toolkit 4.1:"
-patch menusharing.c "{Source}ns:lib:mac:patches:menusharing.patch"</PRE>
-
-<LI>
-If you are using CWPro2 straight off the CD, you need to patch AppleEvents.r
-to fix a problem with the Universal Headers (the definition of the 'aedt'
-resource was omitted). <B>You do not have to do this if you have applied
-the netborne patch to Pro2 or are using Pro3</B> because it has been fixed.</LI>
-
-<PRE>directory "{IDE}MacOS Support:Headers:Rez Headers:"
-patch AppleEvents.r "{Source}ns:lib:mac:patches:AppleEvents.r.patch"</PRE>
-
-<LI>
-You need to patch stat.mac.h to fix a problem in MSL where lines were omitted
-(both CWPro2 and Pro3 share this problem)</LI>
-
-<PRE>directory "{IDE}Metrowerks Standard Library:MSL C:MSL Mac:Public Includes"
-patch stat.mac.h "{Source}ns:lib:mac:patches:stat.mac.h.patch"</PRE>
-
-<LI>
-If you are using CWPro3, you have to unstuff and copy the old Grayscale
-Appearance classes into the PowerPlant hierarchy. As of Pro3, they are
-now obsolete and are located with the rest of the obsolete PowerPlant files.
-We'll fix this shortly.</LI>
-</OL>
-
-<H4>
-Ok, so how do I build?</H4>
-There is an AppleScript called <B>BuildList</B> located in ns:cmd:macfe:projects.
-This droplet takes, as input, a text file which lists the projects in the
-order which they are to be built. This allows us to build different versions
-of the product just by dropping a different "script" on BuildList (such
-as Debug, Optimized, Navigator stand-alone, or navigator + composer).
-
-<P>These scripts are located in ns:cmd:macfe:projects:client and have names
-like <B>BuildMozPPCDebugList.txt</B>. This script will build a debug version
-of Mozilla (navigator + composer) for PPC. Get it? Good. All you have to
-do is drag this script to the BuildList droplet and watch it crunch away.
-Now go out to dinner. By the time you get back, you should have an executable
-in ns:cmd:macfe:projects:client called, for this particular script, <B>MozillaPPCDebug</B>.
-You will see the following build lists in the client folder, but as of
-3/31, only BuildMozPPCList.txt and BuildMozPPCDebugList.txt are guaranteed
-to work:
-<UL>
-<LI>
-BuildMozPPCList.txt</LI>
-
-<LI>
-BuildMozPPCDebugList.txt</LI>
-
-<LI>
-BuildNavPPCDebugList.txt [ might work ]</LI>
-
-<LI>
-BuildNavPPCList.txt [ might work ]</LI>
-</UL>
-If there were any errors in any of the projects along the way, the script
-will stop at that point and the IDE will tell you the errors. You can fix
-them and make sure they current project builds, but to continue the automation,
-you have to start from the beginning by dropping the script onto BuildList.
-This isn't quite as bad as it sounds because the previous projects are
-already built (unless you changed some major header file).
-
-<P>Don't worry too much about the numerous warnings generated during the
-build. We try our best to get the XP teams to use real compilers, but alas,
-they continue to write warning-laden code. There is also some generated
-code (Java is one example) that has a lot of warnings that we can't help
-either. If you write any new code, please help us in our quest to get zero
-warnings.
-<H4>
-How long does it take to build?</H4>
-On a G3 with the source and IDE on a RAM disk, it takes about 25 minutes.
-On a PowerTowerPro 225 and everything on the hard drive, it takes about
-45mins to an hour. On a 9500/132 it takes over 2 1/2 hours.
-
-<P>The moral of the story: Don't try this on your 6100/66.
-<H4>
-What's special about running the debug build?</H4>
-Running the optimized (non-debug) version is easy, just double-click it
-and it will work. This is because all the shared libraries are compiled
-directly into the application. We don't do this with the debug version
-to facilitate changing bits in projects other than the main one. This way,
-you don't have to relink the entire app (which can take a while) to see
-the changes, just the project that was modified.
-
-<P>As a result, you have to find a way to get all the shared libraries
-from where they are built (scattered throughout the tree) into the same
-folder as the app so CFM can find them. Luckily, the BuildList script will
-create all these aliases for you and put them in the right places!
-
-<P>Another nicety about the debug build is that there is a special "trace"
-function which can be used to display messages about the state of the application
-as it runs through certain blocks of code. To see these messages (since
-the Mac doesn't have stdout or stderr) you need to run an application called
-TraceMonitor. &lt;&lt; where do we distribute this???!?>>
-<H4>
-How do I build a 68K version?</H4>
-For now, you can't. The projects have not been kept up to date and aren't
-even in the tree anymore. If you would like to create them and get all
-the exports right with CFM-68K, go right ahead. We will be so happy!
-<H4>
-Why use IDE_Options.h when all that is in the project file?</H4>
-It was originally intended to make sure that all 300 of us at Netscape
-are using the same environment and compilation flags. If something gets
-turned on/off by accident in the project prefs, it can introduce a subtle
-bug that can take days to track down for naught. Having a file that specifies
-exactly what flags should be used guarantees that this can't happen.
-
-<P>Now that we move to net development, I'm sure you will agree that this
-is even more important.
-<H2>
-
-<HR><A NAME="NewFeatures"></A>New 5.0 Features</H2>
-We can't present this section until after 3/31/98. Please check back here
-after that.&nbsp;<!--
-<H3>
-Navigator Center (Aurora)</H3>
-The Navigation Center (referred to as "Aurora" in press releases) is an
-attempt to make it easier to access and organize information on the web.
-The NC unifies Bookmarks, History, Search, and local files into a sequence
-of workspaces which are accessible from a single location in the browser
-window. One of the ways the NavCenter diverges from a similar concept seen
-from our competition is the ability for users to create their own workspaces
-to organize and store information from both the web and their desktop.
-<UL>
-<LI>
-Main access point is a bar along the left side of the browser.</LI>
-
-<LI>
-Each icon represents a workspace. <B>Click any workspace icon once to slide
-out a hierarchical tree</B> (like the list view in the Finder) that displays
-the information appropriate to that workspace. You can manipulate the URLs
-and folders in the tree while you are surfing the web in the adjacent pane.</LI>
-
-<LI>
-Clicking on another workspace while the shelf is open switches to showing
-the contents of that workspace.</LI>
-
-<LI>
-<B>To hide the shelf, click the close box above the column headers</B></LI>
-
-<LI>
-To create new bookmarks, <B>drag bookmarks from the location bar of the
-browser into the NC</B> and file them where you want. Of course, the old
-methods still work.</LI>
-
-<UL>
-<LI>
-If the NC shelf is not open, drag to the workspace where you want to file
-the bookmark and after a small delay, the <B>shelf will spring open</B>.
-You can now drop your new bookmark exactly where you want.</LI>
-
-<LI>
-If the workspace you want is not displayed, drag over that workspace and
-after a small delay, the contents of that workspace will become visible.</LI>
-</UL>
-
-<LI>
-You can also <B>open a stand-alone NC window</B> from the Communicator
-menu. The standard "cmd-b" and "cmd-h" for bookmarks and history are wired
-to open a new NC window with the appropriate workspace visible.</LI>
-
-<LI>
-You can <B>hide the list of workspaces</B> at the left of the browser window
-by choosing "View:Hide NavCenter Selector". You can show it again by doing
-the same thing. Even when hidden in the browser, the stand-alone versions
-are always available.</LI>
-
-<LI>
-Drag bookmarks to the trash to delete them. You can also hit the "delete"
-key (backspace) to remove bookmarks.</LI>
-
-<LI>
-The NavCenter is fully <B>context-menu savvy</B>. There are many commands
-that are in context menus that are not in the main menubar (right now).</LI>
-
-<LI>
-<B>ToolTip savvy</B>. Both the title and URL can be seen in their entirety
-by hovering over the appropriate column.</LI>
-
-<LI>
-3-state <B>sorting: alphabetical, reverse-alphabetical, none</B>. Like
-in the Finder, setting a sort does not change the hierarchy or make any
-permanent modifications to your organizational structure.</LI>
-</UL>
-
-<H3>
-Personal Toolbar</H3>
-
-<UL>
-<LI>
-A toolbar to store bookmarks, first seen on Win/UNIX in 4.0. Single click
-to load URL in current browser window</LI>
-
-<LI>
-<B>Drag and drop bookmarks to the toolbar to add them.</B> Drag existing
-bookmarks on the toolbar to rearrange the order. Drag bookmarks to the
-trash can to remove them from the toolbar.</LI>
-
-<LI>
-<B>Dynamically allocates horizontal space</B> to buttons on toolbar. Adding
-new buttons shrinks existing ones, removing buttons distributes the vacated
-space to existing buttons. Changing the window width reallocates space
-accordingly.</LI>
-
-<LI>
-You can further manipulate, rename, rearrange, add to and remove the URLs
-in the folder that represents the personal toolbar in the Navigation Center.</LI>
-
-<LI>
-ToolTips show the full title.</LI>
-</UL>
-
-<H3>
-Navigator</H3>
-
-<UL>
-<LI>
-new "Mariner" technology makes table layout much faster and does not reload
-the page when the window is resized.</LI>
-
-<LI>
-buttons/popup menus in the chrome now look more like MacOS controls.</LI>
-</UL>
-
-<H3>
-Composer Features</H3>
-
-<UL>
-<LI>
-Drag and Drop</LI>
-
-<LI>
-Direct manipulation editing of tables</LI>
-</UL>
--->
-<H2>
-
-<HR><A NAME="Unfinished"></A>Unfinished "Features"</H2>
-We can't present this section until after 3/31/98. Please check back here
-after that.&nbsp;<!--
-This source release is not of beta quality, hence it will have lots of
-bugs that a normal beta (or even an alpha) would not have. There are many
-features which we are not even close to being finished with, let alone
-knowing what the final UI will be. Here are some things that we know about
-but didn't have time to get to before the code left the building. Feel
-inclined to help us out? Grrrrrrreat!
-<H3>
-Aurora</H3>
-Aurora is definitely a work in progress. Here are the bugs that we just
-don't have time to fix
-<UL>
-<LI>
-Real icons for files on disk</LI>
-
-<LI>
-changing view from XP code (e.g., JavaScript) has not been tested, but
-should work</LI>
-
-<LI>
-move vs. copy notification (cursor doesn't change, etc. No XP support for
-this yet)</LI>
-
-<LI>
-double-click on the text of an item should launch the url, not trigger
-an in-place edit</LI>
-
-<LI>
-separator needs UI consensus and its own icon</LI>
-
-<LI>
-drag &amp; drop</LI>
-
-<UL>
-<LI>
-can't disallow drags to trash when pane is read only. Trash will still
-highlight even though nothing will happen.</LI>
-
-<LI>
-occasional -49 error when dragging repeatedly to browser window. I think
-the DragManager is corrupt because -49 is not a drag manager error and
-d&amp;d doesn't work anywhere else after that.</LI>
-
-<LI>
-drag feedback doesn't work correctly when view is sorted or when some items
-are local vs. remote.</LI>
-
-<LI>
-Composer needs to correctly handle HT_Node flavor</LI>
-
-<LI>
-Sometimes things will move, other times they will copy. Its an XP thing.</LI>
-</UL>
-
-<LI>
-Chrome properties not correctly respected (relies on personal toolbar being
-hidden to hide NavCenter)</LI>
-
-<LI>
-sort state of columns not saved (nor is anything else with columns)</LI>
-
-<LI>
-we shouldn't be using HT_SetNodeName(). Use HT_SetNodeData() instead</LI>
-
-<LI>
-Open/Close context menu does not redraw disclosure triangle after executing</LI>
-
-<LI>
-There are currently no user configurable prefs for Aurora. This will change.</LI>
-
-<LI>
-You can't edit the URL field because RDF uses this as the key in its database.
-As a result, having two bookmarks in the same workspace can lead to odd
-behavior</LI>
-
-<LI>
-Undo/redo does not work yet (XP problem)</LI>
-
-<LI>
-Cut deletes nodes, it does not put them on a clipboard. Copy/paste do nothing.
-This is an XP problem.</LI>
-</UL>
-Still major work to do:
-<UL>
-<LI>
-create new workspaces with d&amp;d</LI>
-
-<LI>
-rollover feedback on selector</LI>
-
-<LI>
-sitemap notification</LI>
-
-<LI>
-scroll selector bar</LI>
-
-<LI>
-HTML pane/search pane</LI>
-
-<LI>
-spring-loaded folders on d&amp;d</LI>
-</UL>
-
-<H3>
-General FE Problems</H3>
-
-<UL>
-<LI>
-<B>DNS lookups may hang up the machine for up to a minute. Don't worry,
-your mac did not freeze!</B></LI>
-
-<LI>
-FTP doesn't work quite right. URLs typed into the location bar will not
-load and the MIME mappings (save to disk, etc) are broken so everything
-is loaded into the browser window instead of saving to disk.</LI>
-
-<LI>
-frame around current tab group broken</LI>
-
-<LI>
-tabbing around to text entry areas and back to the Location field is broken</LI>
-
-<LI>
-can't drag from Navigator when app is in background</LI>
-
-<LI>
-Folders on personal toolbar. Sigh, unless we can rewrite the bookmarks
-menu code, we just don't have enough hierarchical menu id's to put menus
-on personal toolbar folders. They still act as drop sites, so you can drop
-urls into them but clicking on them will just beep.</LI>
-
-<LI>
-Printing is....sub-optimal.</LI>
-
-<LI>
-"Mariner" layout improvements are nice, but on very complicated pages the
-machine will hang for a few seconds while it is relaying out the page.
-This can last 4-6 seconds sometimes. This really looks bad when the NavCenter
-shelf is sliding out during a drag and drop. If you are patient enough,
-you will be rewarded, but it is slow.</LI>
-</UL>
--->
-<H2>
-
-<HR><A NAME="Pitfalls"></A>Pitfalls</H2>
-There are a couple of pitfalls that we have to keep straight when it comes
-to editing resources.
-<H4>
-Why do I keep getting messages about unknown custom types in Constructor?</H4>
-For starters, make sure you have an alias to the following two files in
-your Constructor folder:
-<UL>
-<LI>
-ns:cmd:macfe:rsrc:CrossProduct:Mozilla_Custom_CPPbs</LI>
-
-<LI>
-ns:cmd:macfe:rsrc:Communicator:MailNewsCppbs.cnst</LI>
-</UL>
-You may have to explicitly open these files up while running Constructor
-to be able to see the new types, especially for the ones in MailNewsCppbs.cnst.
-Not sure why yet.
-
-<P>For editing other kinds of resources, we have a TMPL file for ResEdit/Resourcerer.
-Place these in the appropriate location for your resource editor
-<UL>
-<LI>
-ns:cmd:macfe:rsrc:CrossProduct:Mozilla_Custom_TMPLs</LI>
-
-<LI>
-ns:cmd:macfe:rsrc:CrossProduct:Other_Comm_TMPLS.rsrc</LI>
-</UL>
-
-<H4>
-Why don't my toolbar buttons work anymore in the browser window?</H4>
-Because of the way we have the toolbars as CIncludeViews (which work in
-a similar way to #include in C/C++), the RidL will be messed up if you
-edit the main browser window PPob. Constructor regenerates this list based
-on all the controls that are in the view when you save, but because we
-use CIncludeView, the toolbar buttons aren't actually in the view so the
-RidL is empty. They will still show up when you build, but they won't do
-anything because they are not registered with the browser window. Until
-we fix this, just use Resourcer to replace the incorrectly generated one
-with an old version. The old version is about 58 bytes long and the new
-one is about 10 so you should be able to easily tell which is which.
-<H4>
-Why are there so many damn resources?</H4>
-As you may have noticed, we've got too many damn resources. Most of them
-are 'STR ' resources which are generated at build time and contain all
-of our cross-platfrom strings. We would like to generate these resources
-more intelligently (into 1/10 the number of 'STR#' resources maybe) but
-ran out of time before the source had to go out. Before you rush out and
-change it for us, <B>stop</B>! There are some constraints on the final
-solution, mostly to do with i18n and l10n being able to leverage existing
-work on older product to do new products. If you want to help us out with
-this, please send us some email and we can have out i18n team talk with
-you to make sure it gets done correctly!
-<H4>
-Why doesn't it work better with Internet Config?</H4>
-For starters, the main reason why we never drank the IC kool-aid was that
-there was no support for multiple profiles. Being one of the main features
-which our competition did not have, we thought this was pretty important.
-There are rumblings in the IC world that IC 2.0 will support multiple profiles.
-Great! That still leaves us with the second reason: there are many, many,
-many preferences that we use that are not reflected in IC. As a result,
-we already have to maintain prefs for those that are not covered by IC
-so we can't be totally IC dependent.
-
-<P>Of course, now that the source is free, maybe we can drive the direction
-of IC to include all of our wacky networking prefs.
-<H4>
-Where are all my old 4.0X bookmarks and prefs?</H4>
-In the process of getting the source ready for distribution, we removed
-all mentions of "Netscape" from the product. As you may know, the 4.0X
-preferences are stored in a folder called "Netscape Users." Well, that
-folder is now called "Navigator Users" and the preference file is now called
-"Navigator Preferences" instead of "Netscape Preferences."
-
-<P>It's probably best not to use any of your old prefs at this point since
-some of them rely on security calls that are no longer in the free source
-product. After you create a new profile (and you will have to when you
-start the free source), copy your bookmarks.html file from your old profile
-into the new user profile folder and replace the empty one that's already
-there (if there is one).
-
-<P><B>For your old bookmarks to be seen, you must throw away the "NavCntr"
-folder</B> created in your new profile folder. After you do that bookmarks
-will be imported into Aurora automagically. Note that changes that you
-make to your bookmarks in 5.0 will not (as of today) be written back to
-the Bookmarks.html file, but instead are stored in a database within the
-"NavCntr" folder. If anything gets corrupted in the NavCenter, you can
-always throw this folder into the trash and your original bookmarks will
-be reimported.
-
-<P>Also note that these new bookmarks and preferences are totally separate
-from your 4.0X prefs.
-<H2>
-
-<HR><A NAME="HistFuture"></A>History and Future</H2>
-
-<H3>
-History</H3>
-Excuse me while I ramble...
-<UL>
-<LI>
-Built using Metrowerks PowerPlant, the client has been PPC native from
-day one. 68K support was dropped in 5.0 due to the high cost of maintenance.
-Any takers?</LI>
-
-<LI>
-Mail/News was added in 2.0 and Composer was added in 3.0 (called Navigator
-Gold). Both were dramatically improved with 4.0.</LI>
-
-<LI>
-Java came to the Mac in 3.0, even though Windoze and unix had it in 2.0.</LI>
-
-<LI>
-Multi-byte language support for inline edit fields added in 4.0</LI>
-
-<LI>
-The preferences used to be STR# resources. Now they are done in javascript.</LI>
-
-<LI>
-Because of the sheer number of resources (and the "theoretical limit" on
-the number of resources in a file imposed by the Resource manager -- which
-we still exceed on a daily basis), a number of strings and icons were moved
-out of the main application and into a file called "Netscape Resources"
-in 4.0</LI>
-
-<LI>
-For plain-text email/form composition, we used VText up through 4.0. For
-5.0, we switched to WASTE because of its minimal impact on the PowerPlant
-hierarchy. VText caused us fits every time we wanted to upgrade to a newer
-version of PowerPlant because it wrapped its tentacles around every limb
-of PowerPlant.</LI>
-
-<LI>
-4.0 included a new memory management scheme which drastically reduced the
-amount of memory used by the client. This is why the memory partition of
-4.0 is about half of 3.0.</LI>
-
-<LI>
-A version of Navigator sans Mail/News/Composer debuted with 4.03, and again
-two days later with 4.03.1.</LI>
-</UL>
-
-<H3>
-Future</H3>
-There is certainly a lot to do. In order to not duplicate too much work
-(since we are still working on this full time here at Netscape), I've put
-together a list of what we plan on doing and what we want to do but probably
-won't get around to because of time constraints.
-
-<P>Things that we are going to focus on:
-<UL>
-<LI>
-More NavCenter work</LI>
-
-<LI>
-Solve the issues with too many 'STR ' resources (see note on <A HREF="#Pitfalls">issues
-page</A>)</LI>
-
-<LI>
-Modularization (HTML display isolated from networking, etc)</LI>
-
-<LI>
-use new Appearance Manager classes in PowerPlant</LI>
-
-<LI>
-Navigation Services (new open/save dialogs in Allegro) support. We have
-an ancient SDK and have integrated it in a few places, but the current
-implemenation that we have doesn't work very well. It's cool, though.</LI>
-
-<LI>
-More drag and drop in composer.</LI>
-
-<LI>
-More support for Internet Config (see note on <A HREF="#Pitfalls">issues
-page</A>).</LI>
-
-<LI>
-external Java VM support (MRJ, etc)</LI>
-</UL>
-Things we would like some help on:
-<UL>
-<LI>
-printing support</LI>
-
-<LI>
-68K version</LI>
-
-<LI>
-Context Menu Manager support</LI>
-
-<LI>
-bug fixes of any kind</LI>
-
-<LI>
-performance tuning of any kind</LI>
-
-<LI>
-getting around the limitation of 255 hierarchical menus imposed by the
-OS. This would let us do a "real" personal toolbar with folders that have
-popup menus.</LI>
-
-<LI>
-Fixing the build system so it uses makefiles without having to give up
-the CW IDE for source browsing/editing.</LI>
-
-<LI>
-better publishing in Composer</LI>
-
-<LI>
-add NavCenter to Composer window</LI>
-
-<LI>
-better table editing in Composer</LI>
-</UL>
-
-<ADDRESS>
-
-<HR>Mike Pinkerton (<A HREF="mailto:pinkerton@netscape.com">pinkerton@netscape.com</A>)</ADDRESS>
-
-<BR>
-<HR WIDTH="100%">
-<CENTER><FONT SIZE=-1>Copyright &copy; 1998 <A HREF="http://home.netscape.com/misc/contact_info.html">Netscape
-Communications Corporation</A></FONT></CENTER>
-
-</BODY>
-</HTML>

README/mozilla/unixbuild.htm

@@ -1,82 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Unix Build Instructions</TITLE>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF">
-
-<H2>
-<FONT FACE="Arial,Helvetica">Unix Build Instructions</FONT></H2>
-This document explains how to build Mozilla for Unix.
-<BR>
-<HR WIDTH="100%">
-<PRE>Requirements:
-
-&nbsp; Memory:
-&nbsp;&nbsp;&nbsp; 32MB of RAM, 128MB of swap, recommended 64MB of RAM.
-
-&nbsp; Tools:
-&nbsp;&nbsp;&nbsp; GNU C/C++ compiler 2.7.2 or better
-&nbsp;&nbsp;&nbsp; GNU make 3.74 or better
-&nbsp;&nbsp;&nbsp; Motif 1.2 (Lesstif has been used with limited success)
-
-&nbsp; Tools that will be helpful later:
-&nbsp;&nbsp;&nbsp; Perl 5.0
-&nbsp;&nbsp;&nbsp; CVS 1.8.1
-&nbsp;&nbsp;&nbsp; RCS
-&nbsp;&nbsp;&nbsp; gdb 4.16
-
-&nbsp; NOTE:
-&nbsp;&nbsp;&nbsp; * gcc version 2.8 has been used successfully.
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Your mileage may vary.
-
-Build:
-
-&nbsp; Untar the tar.gz file with the following (or your favorite variant thereof):
-
-&nbsp;&nbsp;&nbsp; gzip -dc tarball.tar.gz | tar -xvf -
-
-&nbsp; Set the following environment variables:
-&nbsp;&nbsp;&nbsp; csh/tcsh:&nbsp;
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; setenv NO_SECURITY 1
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; setenv MOZ_MEDIUM 1
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; setenv MOZILLA_CLIENT 1
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; setenv NO_MDUPDATE 1
-
-&nbsp;&nbsp;&nbsp; sh/bash/ksh:
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NO_SECURITY=1
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOZ_MEDIUM=1
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MOZILLA_CLIENT=1
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NO_MDUPDATE=1
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; export NO_SECURITY MOZ_MEDIUM MOZILLA_CLIENT NO_MDUPDATE
-
-&nbsp; Debug build is default; optimized build:
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; setenv BUILD_OPT 1
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (BUILD_OPT=1; export BUILD_OPT)
-
-&nbsp; On AIX, <B>ap</B>pend /usr/lpp/xlC/bin to your PATH.
-&nbsp; On Solaris, SINIX, and UnixWare, <B>pre</B>pend /usr/ccs/bin to your PATH.
-
-&nbsp; Build it.&nbsp; Default target is "export libs install":
-&nbsp;&nbsp;&nbsp; cd ns
-&nbsp;&nbsp;&nbsp; gmake -k
-
-NOTE:
-
-If you haven't got perl:
-
-setenv PERL /bin/echo
-
-gmake -ek
-
-Run the app:
-&nbsp; Executable lives in ns/cmd/xfe/{ARCHITECTURE}.{DBG|OPT}.OBJ
-&nbsp;&nbsp;&nbsp; (e.g. ns/cmd/xfe/Linux2.0.31_x86_DBG.OBJ/mozilla-export)
-&nbsp; Statically-linked app is "mozilla-export"
-&nbsp; dynamically-linked app is "moz-export"</PRE>
-
-<HR WIDTH="100%">
-<CENTER><FONT SIZE=-1>Copyright &copy; 1998 <A HREF="http://home.netscape.com/misc/contact_info.html">Netscape
-Communications Corporation</A></FONT></CENTER>
-
-</BODY>
-</HTML>

README/mozilla/winbuild.htm

@@ -1,220 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=x-mac-roman">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.05 [en]C-NSCP  (WinNT; U) [Netscape]">
-   <META NAME="KeyWords" CONTENT="client, source, documentation">
-   <META NAME="Author" CONTENT="Chris Yeh">
-   <TITLE>WinFE Build Instructions</TITLE>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF">
-
-<H2>
-<FONT FACE="Arial,Helvetica">WinFE Build Instructions</FONT></H2>
-This document explains how to build Mozilla for the Windows platform. WinFE
-is the Windows front end module.&nbsp;
-<HR><B><FONT SIZE=+1>Required Tools:</FONT></B>
-<UL>
-<LI>
-<B>Microsoft Visual C++ version 4.2 or later</B></LI>
-
-<LI>
-<B>GNU Tools for Windows:</B>You can find these all over the web. Specifically,
-you'll need:</LI>
-
-<PRE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; cp.exe
-
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rm.exe</PRE>
-
-<UL>Here are some sample download sites to find these:
-<LI>
-<A HREF="http://www.cygnus.com/misc/gnu-win32">Cygnus</A></LI>
-
-<LI>
-<A HREF="http://www.gnu.org/order/ftp.html">GNU home page</A></LI>
-
-<LI>
-<A HREF="ftp://prep.ai.mit.edu/pub/gnu">MIT</A></LI>
-</UL>
-Netscape has internally modified version of gmake, shmsdos and win32gnu
-that we use to get around some problems we were having keeping in sync
-with the Unix version of gmake. This version of gmake and it's source is
-included in the Mozilla source distribution. The specific files pertaining
-to this are:
-<PRE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; gmake.exe
-
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; shmsdos.exe
-
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; uname.exe</PRE>
-These are located in the \tools\bin directory of the source package. All
-of these tools need to be put in your path.
-<LI>
-Additionally, there are Netscape-developed tools that need to be built
-prior to your first compile. These are covered in the build section.</LI>
-</UL>
-<B><FONT SIZE=+1>Setting up:</FONT></B>
-<UL>
-<LI>
-You need a Pentium with at least a 133 MHz processor and at least 250 megs
-(NTFS partition) or 500 megs (FAT partition) of hard drive space. You need
-to have a minimum of 64 megs of memory in order to build this tree. Having
-at least 128 megs of memory will make your debugging experience noticeably
-less agonizing</LI>
-
-<LI>
-The preferred platform is NT 4.0. NT 3.51 will also work, and Win95 might
-work if you're lucky. Maybe.</LI>
-
-<LI>
-Install MSVC. If you don't choose to have the MSVC install modify your
-environment variables for PATH, INCLUDE, and LIB information, be sure to
-run VCVARS32.BAT out of the MSVC bin directory prior to attempting to build.</LI>
-
-<LI>
-Download and install GNU tools. Put them in your path.</LI>
-
-<LI>
-Install Mozilla source.</LI>
-
-<LI>
-There are several environment variables you will need to set, either manually
-or via a script within a command session, or by setting them in your system
-environment located through the Control Panel | System icon. Those variables
-are:</LI>
-
-<UL>
-<LI>
-set MOZ_BITS=32</LI>
-
-<LI>
-set MOZ_DEBUG=1 (don't set this if you want to build an optimized release
-build)</LI>
-
-<LI>
-set MOZ_GOLD=1</LI>
-
-<LI>
-set MOZ_MEDIUM=1</LI>
-
-<LI>
-set MOZ_NT=351 (if running NT 3.51, don't set otherwise)</LI>
-
-<LI>
-set MOZ_OUT=(location of resulting executable and totally optional, see
-Notes for more details)</LI>
-
-<LI>
-set MOZ_SRC=(top of your tree, drive letter and path, i.e. set MOZ_SRC=d:\mozilla_src.
-The topmost directory under this should be ns)</LI>
-
-<LI>
-set MOZ_TOOLS=(location of the bin directory containing your GNU tools.
-The build looks for MOZ_TOOLS\bin\gmake.exe, so make sure your MOZ_TOOLS
-is figured appropriately)</LI>
-
-<LI>
-set NO_SECURITY=1</LI>
-
-<LI>
-set NSPR20=1</LI>
-
-<LI>
-if you are running VC++ 5.0 or higher: set _MSC_VER=1100</LI>
-</UL>
-</UL>
-<B><FONT SIZE=+1>Building:</FONT></B>
-<UL>
-<LI>
-You need to be running a vanilla command prompt. Other shells may work,
-but you might have to tweak makefiles.</LI>
-
-<LI>
-<B>Build the tools:</B> This generates several tools that handle things
-like dependency generation</LI>
-
-<UL>
-<LI>
-cd ns\config</LI>
-
-<LI>
-nmake /f makefile.win</LI>
-</UL>
-
-<LI>
-<B>Build the whole lizard:</B> This will do a complete build of the source
-tree. You will end up with a mozilla.exe at the end.</LI>
-
-<UL>
-<LI>
-cd ns</LI>
-
-<LI>
-nmake /f client.mak</LI>
-</UL>
-</UL>
-&nbsp;
-<UL>
-<LI>
-If you want to build communicator a piece at a time, these are the steps
-that client.mak steps through. If you successfully ran the client.mak step
-above, you don't need to do this.</LI>
-
-<LI>
-<B>Build the back end:</B> This builds cross platform components like NSPR
-and the shared library modules. All of the interesting output from this
-part of the build will end up in ns\dist, under public\ if it's a library
-header, and under WIN32_D.OBJ\ (or WIN32_O.OBJ\ for an optimized build)
-if it's a dynamic or static library. The exception is the NSPR public headers,
-which live in WIN32_D.OBJ\include.</LI>
-
-<UL>
-<LI>
-cd ns</LI>
-
-<LI>
-nmake /f makefile.win</LI>
-</UL>
-
-<LI>
-<B>Build the front end:</B> This builds and links into the final executable,
-mozilla.exe.</LI>
-
-<UL>
-<LI>
-cd ns\cmd\winfe\mkfiles32</LI>
-
-<LI>
-nmake /f mozilla.mak DEPEND=1</LI>
-
-<LI>
-nmake /f mozilla.mak</LI>
-</UL>
-</UL>
-<B><FONT SIZE=+1>Notes:</FONT></B>
-<UL>
-<LI>
-MOZ_OUT: If you don't set this, mozilla.exe will be generated into ns\cmd\winfe\mkfiles32\x86dbg
-(or x86rel for optimized builds)</LI>
-
-<LI>
-This build process does not use Visual C++ generated project files for
-several reasons having to do with (among other things) size, maintainability,
-and the long term desire to start using more of tools like gmake, or plug
-and play developer tools. This does not preclude you from using the Visual
-C++ IDE, or it's debugger (somebody fill this out with more detail).</LI>
-
-<LI>
-All of the DLLs that you need to run mozilla.exe get copied automagically
-into your output directory as the last part of build, so all you need to
-do is cd into x86dbg and run mozilla.exe to get a runnable browser.</LI>
-
-<LI>
-On a Pentium II 266 MHz machine with 128 megs of memory, it takes approximately
-30 minutes to build. Your mileage may vary.</LI>
-</UL>
-
-<HR WIDTH="100%">
-<CENTER><FONT SIZE=-1>Copyright &copy; 1998 <A HREF="http://home.netscape.com/misc/contact_info.html">Netscape
-Communications Corporation</A></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

README/mozilla/wininstall.htm

@@ -1,53 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Chris Yeh">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.05 [en]C-NSCP  (WinNT; U) [Netscape]">
-   <TITLE>Running Mozilla...</TITLE>
-</HEAD>
-<BODY>
-
-<H2>
-<FONT FACE="Arial,Helvetica">Running Mozilla Without Trashing Netscape
-Installation</FONT></H2>
-This document explains how to run <TT>mozilla.exe</TT> separately from
-<TT>netscape.exe</TT> without trashing your regular installation of Netscape
-Communicator. This is necessary if, for example, you want to use Communicator's
-mail client while you work on Mozilla development.
-<BR>
-<HR WIDTH="100%">
-<OL>
-<LI>
-Before running <TT>mozilla.exe</TT>, create a new user profile either from
-a Netscape 4.0x installation using the "User Profile Manager" shortcut
-in the Utilities folder (on Windows) or by using&nbsp; the <TT>-new_account</TT>
-option on the command line of either <TT>netscape.exe</TT> or <TT>mozilla.exe</TT>.&nbsp;
-We suggest calling the profile "<TT>mozilla</TT>."</LI>
-
-<LI>
-Always use that new account when running <TT>mozilla.exe</TT>, and never
-run <TT>netscape.exe</TT> using that same account profile.</LI>
-</OL>
-To make things easier, you can start the application with the user account
-on the command line, for example:
-<UL><TT>mozilla.exe -P"mozilla"</TT></UL>
-This assures that prefs and the cache will not interfere between the two
-versions. This will be especially
-<BR>important as new prefs are added to the Mozilla product. Note that
-you must use quotes around the name and there can be no space between the
-"P" and the profile name. Otherwise, the application won't catch the profile
-switch, and it will try to load the profile name as the initial URL.
-
-<P>
-<HR WIDTH="100%">
-<BR>You can copy your <TT>bookmark.htm</TT> file from an existing profile
-to your new profile directory if you want to share bookmarks.
-
-<P>After the initial 3/31 release, we will add some code to Mozilla to
-prevent running with a profile that is already being used by <TT>netscape.exe</TT>.
-<BR>&nbsp;
-<HR WIDTH="100%">
-<BR><FONT SIZE=-1>Copyright &copy; 1998 <A HREF="http://home.netscape.com/misc/contact_info.html">Netscape
-Communications Corporation</A></FONT>
-</BODY>
-</HTML>

README/raptor/winbuild.html

@@ -1,180 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=x-mac-roman">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="KeyWords" CONTENT="client, source, documentation">
-   <META NAME="Author" CONTENT="Kipp E.B. Hickman">
-   <TITLE>Raptor Windows Build Instructions</TITLE>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF">
-
-<H2>
-<FONT FACE="Arial,Helvetica">Raptor Windows Build Instructions</FONT></H2>
-This document explains how to build Raptor for the Windows platform.
-<HR><B><FONT SIZE=+1>Required Tools:</FONT></B>
-<UL>
-<LI>
-<B>Microsoft Visual C++ version 4.2 or later</B></LI>
-
-<LI>
-<B>The same set of tools for building <A HREF="http://www.mozilla.org/docs/tplist/catBuild/winbuild.htm">Mozilla</A></B></LI>
-</UL>
-<B><FONT SIZE=+1>Setting up:</FONT></B>
-<UL>
-<LI>
-You need a Pentium with at least a 133 MHz processor and at least 250 megs
-(NTFS partition) or 500 megs (FAT partition) of hard drive space. You need
-to have a minimum of 64 megs of memory in order to build this tree. These
-numbers are approximations.</LI>
-
-<LI>
-The preferred platform is NT 4.0. NT 3.51 will also work, and Win95 might
-work if you're lucky. Maybe.</LI>
-
-<LI>
-Install MSVC. If you don't choose to have the MSVC install modify your
-environment variables for PATH, INCLUDE, and LIB information, be sure to
-run VCVARS32.BAT out of the MSVC bin directory prior to attempting to build.</LI>
-
-<LI>
-Download and install GNU tools. Put them in your path.</LI>
-
-<LI>
-Install Raptor source.</LI>
-
-<UL>
-<LI>
-cd &lt;your-source-area></LI>
-
-<LI>
-unzip -o -q win-19980415.zip</LI>
-</UL>
-
-<LI>
-There are several environment variables you will need to set, either manually
-or via a script within a command session, or by setting them in your system
-environment located through the Control Panel | System icon.<P>
-<B>Note: There is an additional variable for building Raptor!
-Use this list carefully!</B><P>
-The variables are:</LI>
-
-<UL>
-<LI>
-set MOZ_BITS=32</LI>
-
-<LI>
-set MOZ_DEBUG=1 (don't set this if you want to build an optimized release
-build)</LI>
-
-<LI>
-set MOZ_GOLD=1</LI>
-
-<LI>
-set MOZ_MEDIUM=1</LI>
-
-<LI>
-set MOZ_NT=351 (if running NT 3.51, don't set otherwise)</LI>
-
-<LI>
-set MOZ_OUT=(location of resulting executable and totally optional, see
-Notes for more details)</LI>
-
-<LI>
-set MOZ_SRC=(top of your tree, drive letter and path, i.e. set MOZ_SRC=d:\mozilla_src.
-The topmost directory under this should be ns)</LI>
-
-<LI>
-set MOZ_TOOLS=(location of the bin directory containing your GNU tools.
-The build looks for MOZ_TOOLS\bin\gmake.exe, so make sure your MOZ_TOOLS
-is figured appropriately)</LI>
-
-<LI>
-set NO_SECURITY=1</LI>
-
-<LI>
-set NSPR20=1</LI>
-
-<LI>
-if you are running VC++ 5.0 or higher: set _MSC_VER=1100; if you are running
-VC++ 4.2 then set MOZ_VCVER=42</LI>
-
-<LI>
-<B>set STANDALONE_IMAGE_LIB=1</B></LI> 
-
-</UL>
-</UL>
-<B><FONT SIZE=+1>Building:</FONT></B>
-<UL>
-<LI>
-You need to be running a vanilla command prompt. Other shells may work,
-but you might have to tweak makefiles.</LI>
-
-<LI>
-<B>Build the tools:</B> This generates several tools that handle things
-like dependency generation</LI>
-
-<UL>
-<LI>
-cd ns\config</LI>
-
-<LI>
-nmake /f makefile.win</LI>
-</UL>
-
-<LI>
-<B>Build the Raptor:</B> This will do a complete build of the source tree.
-You will end up with a viewer.exe at the end. The viewer.exe will be in
-your dist\win32_[OD].obj\bin directory (O will be used when you don't set
-MOZ_DEBUG; D will be used when you set MOZ_DEBUG).</LI>
-
-<UL>
-<LI>
-cd ns</LI>
-
-<LI>
-nmake /f raptor.mak</LI>
-</UL>
-</UL>
-<B><FONT SIZE=+1>Running:</FONT></B>
-<UL>
-<LI>
-Once you have built the system, do this to run the viewer program (the
-viewer program is a simple test program that uses the nsIWebWidget API
-to embed a web widget object). The viewer program has a few basic menu
-items, include "Samples" which load sample tests.</LI>
-
-<UL>
-<LI>
-cd ns\dist\win32_[OD].obj\bin</LI>
-
-<LI>
-.\viewer.exe</LI>
-</UL>
-</UL>
-<B><FONT SIZE=+1>Notes:</FONT></B>
-<UL>
-<LI>
-This build process does not use Visual C++ generated project files for
-several reasons having to do with (among other things) size, maintainability,
-and the long term desire to start using more of tools like gmake, or plug
-and play developer tools. This does not preclude you from using the Visual
-C++ IDE, or it's debugger. Once you have built a viewer.exe do this to
-run it under the debugger:</LI>
-</UL>
-
-<UL>
-<UL>
-<LI>
-cd ns\dist\win32_[OD].obj\bin</LI>
-
-<LI>
-msdev viewer.exe</LI>
-</UL>
-</UL>
-
-<HR WIDTH="100%">
-<CENTER><FONT SIZE=-1>Copyright &copy; 1998 <A HREF="http://home.netscape.com/misc/contact_info.html">Netscape
-Communications Corporation</A></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

buildtools/windows/bin/README

@@ -1,26 +0,0 @@
-Building NSPR on Windows NT Using Netscape's gmake and Other Tools
-
-This directory contains the following tools:
-- gmake.exe: GNU make 3.74, modified to use shmsdos.exe as the shell
-- shmsdos.exe: a lightweight shell developed by Netscape programmers.
-      It has most of the file manipulation operations (such as cp,
-      rm, mkdir as well as Netscape's own nsinstall) as built-in
-      commands, so even if you have these
-      file utilities installed on your NT machine, they won't be invoked
-      by gmake and shmsdos.  Also, since shmsdos is not a full-blown
-      shell and its built-in file commands are not fully compatible
-      with the true Unix file utilities, our makefiles have had to
-      avoid some features of sh and work around the incompatibilities
-      on Windows NT.
-- uname.exe: this uname.exe returns the OS as "WINNT", which is what
-      our makefiles assume.  Do not use a uname.exe that returns other
-      strings, such as "Windows_NT".
-
-Binaries for the x86 processors can be found in the 'x86' subdirectory.
-Binaries for the alpha processors can be found in the 'alpha'
-subdirectory.
-
-INSTALLATION:
-
-Install gmake.exe, shmsdos.exe, and uname.exe in any directory.
-Add that directory to your Path environment variable.

buildtools/windows/source/make/job.c

@@ -30,7 +30,7 @@ the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.  */
 
 /* Default shell to use.  */
 #if defined(NETSCAPE)
-char default_shell[] = "shmsdos";
+char default_shell[] = "sh.exe";
 #else
 char default_shell[] = "/bin/sh";
 #endif
@@ -1471,8 +1471,7 @@ exec_command (argv, envp)
 			     "logout", "set", "umask", "wait", "while", "for",
 			     "case", "if", ":", ".", "break", "continue",
 			     "export", "read", "readonly", "shift", "times",
-			     "trap", "switch", "mkdir", "echo", "cp", "rm",
-			     "touch", "nsinstall", "test", "mv", 0 };
+			     "trap", "switch", "test", 0 };
 #else
   static char sh_chars[] = "#;\"*?[]&|<>(){}$`^";
   static char *sh_cmds[] = { "cd", "eval", "exec", "exit", "login",

buildtools/windows/source/make/main.c

@@ -1921,8 +1921,8 @@ print_version ()
  * #define BUILD_NUMBER 19970918
  */
 
-#define DEFAULT_SHELL "shmsdos"
-#define BUILD_NUMBER 19980324
+#define DEFAULT_SHELL "sh.exe"
+#define BUILD_NUMBER 19980501
 
 #if defined(DEFAULT_SHELL) && defined(BUILD_NUMBER)
 

buildtools/windows/source/shmsdos/README

@@ -1,27 +0,0 @@
-This directory contains the source files for shmsdos.exe and
-nsinstall.exe, which are used in conjunction with gmake.exe
-to build some components of the Mozilla client on Win32.
-
-The tool shmsdos.exe is a very lightweight shell.  It is
-the default shell for our gmake.exe.  shmsdos.exe implements
-several common Unix utilities as built-in commands, such as
-mv, cp, rm, echo, mkdir, etc.  It only implements very
-limited shell features.  It can do if-then-else and for loops,
-but it can't do variables, pipes, standard I/O redicrection, etc.
-
-It is possible to use a real Bourne shell with our gmake.exe
-by defining the SHELL variable in your makefiles.  Our gmake.exe
-works with the Korn shell (sh.exe) of MKS Toolkit.  If you go
-this route, you will also need nsinstall.exe.  (nsinstall is
-a built-in command for shmsdos.exe.) 
-
-To build shmsdos.exe, you need Microsoft Visual C++ and nmake.
-Just issue the command:
-    nmake /f shmsdos.mak
-The output is Release\shmsdos.exe.  Copy it to a directory on
-your Path.
-
-To build nsinstall.exe, issue the command:
-    nmake /f nsinstall.mak
-The output is Release\nsinstall.exe.  Copy it to a directory
-on your Path.

buildtools/windows/source/shmsdos/nsinstall.c

@@ -1,697 +0,0 @@
-/*
- * The nsinstall command for Win32
- *
- * Our gmake makefiles use the nsinstall command to create the
- * object directories or installing headers and libs to ns/dist.
- * The shmsdos shell has nsinstall as a built-in command.  However,
- * if we use another shell like MKS toolkit's sh, we need to have
- * the nsinstall command separately.
- *
- * This file was generated by just taking the part of shmsdos.c
- * needed by nsinstall and deleting the recursive directory copy code.
- *
- * To build, say
- *     nmake /f nsinstall.mak
- */
-
-#include <direct.h>
-#include <stdio.h>
-#include <string.h>
-#include <assert.h>
-#include <windows.h>
-#pragma hdrstop
-
-/*
- * sh_FileFcn --
- *
- * A function that operates on a file.  The pathname is either
- * absolute or relative to the current directory, and contains
- * no wildcard characters such as * and ?.   Additional arguments
- * can be passed to the function via the arg pointer.
- */
-
-typedef BOOL (*sh_FileFcn)(
-        char *pathName,
-        WIN32_FIND_DATA *fileData,
-        void *arg);
-
-static int shellCp (char **pArgv); 
-static int shellNsinstall (char **pArgv);
-static int shellMkdir (char **pArgv); 
-static BOOL sh_EnumerateFiles(const char *pattern, const char *where,
-        sh_FileFcn fileFcn, void *arg, int *nFiles);
-static const char *sh_GetLastErrorMessage(void);
-static BOOL sh_DoCopy(char *srcFileName, DWORD srcFileAttributes,
-        char *dstFileName, DWORD dstFileAttributes,
-        int force, int recursive);
-
-/* changes all forward slashes in token to back slashes */
-void changeForwardSlashesTpBackSlashes ( char *arg )
-{
-	if ( arg == NULL )
-		return;
-
-	while ( *arg ) {
-		if ( *arg == '/' )
-			*arg = '\\';
-		arg++;			
-	}
-}
-
-int main(int argc, char *argv[ ])
-{
-	return shellNsinstall ( argv + 1 );
-}
-
-static int
-shellNsinstall (char **pArgv)
-{
-	int retVal = 0;		/* exit status */
-	int dirOnly = 0;	/* 1 if and only if -D is specified */
-	char **pSrc;
-	char **pDst;
-
-	/*
-	 * Process the command-line options.  We ignore the
-	 * options except for -D.  Some options, such as -m,
-	 * are followed by an argument.  We need to skip the
-	 * argument too.
-	 */
-	while ( *pArgv && **pArgv == '-' ) {
-		char c = (*pArgv)[1];  /* The char after '-' */
-
-		if ( c == 'D' ) {
-			dirOnly = 1;
-		} else if ( c == 'm' ) {
-			pArgv++;  /* skip the next argument */
-		}
-		pArgv++;
-	}
-
-	if ( !dirOnly ) {
-		/* There are files to install.  Get source files */
-		if ( *pArgv ) {
-			pSrc = pArgv++;
-		} else {
-			fprintf( stderr, "nsinstall: not enough arguments\n");
-			return 3;
-		}
-	}
-
-	/* Get to last token to find destination directory */
-	if ( *pArgv ) {
-		pDst = pArgv++;
-		if ( dirOnly && *pArgv ) {
-			fprintf( stderr, "nsinstall: too many arguments with -D\n");
-			return 3;
-		}
-	} else {
-		fprintf( stderr, "nsinstall: not enough arguments\n");
-		return 3;
-	}
-	while ( *pArgv ) 
-		pDst = pArgv++;
-
-  	retVal = shellMkdir ( pDst );
-	if ( retVal )
-		return retVal;
-	if ( !dirOnly )
-		retVal = shellCp ( pSrc );
-	return retVal;
-}
-
-static int
-shellMkdir (char **pArgv) 
-{
-	int retVal = 0;			/* assume valid return */
-	char *arg;
-	char *pArg;
-	char path[_MAX_PATH];
-	char tmpPath[_MAX_PATH];
-	char *pTmpPath = tmpPath;
-
-	/* All the options are simply ignored in this implementation */
-	while ( *pArgv && **pArgv == '-' ) {
-		if ( (*pArgv)[1] == 'm' ) {
-			pArgv++;  /* skip the next argument (mode) */
-		}
-		pArgv++;
-	}
-
-	while ( *pArgv ) {
-		arg = *pArgv;
-		changeForwardSlashesTpBackSlashes ( arg );
-		pArg = arg;
-		pTmpPath = tmpPath;
-		while ( 1 ) {
-			/* create part of path */
-			while ( *pArg ) {
-				*pTmpPath++ = *pArg++;
-				if ( *pArg == '\\' )
-					break;
-			}
-			*pTmpPath = '\0';
-
-			/* check if directory alreay exists */
-			_getcwd ( path, sizeof (path) );
-			if ( _chdir ( tmpPath ) != -1 ) {
-				_chdir ( path );
-			} else {
-				if ( _mkdir ( tmpPath ) == -1 ) {
-//				while ( waitForDebug );
-					printf ( "%s: ", tmpPath );
-					perror ( "Could not create the directory" );
-					retVal = 3;
-					break;
-				}
-			}
-			if ( *pArg == '\0' )	/* complete path? */
-				break;
-			/* loop for next directory */
-		}
-
-		pArgv++;
-	}
-	return retVal;
-}
-
-static const char *
-sh_GetLastErrorMessage()
-{
-    static char buf[128];
-
-    FormatMessage(
-            FORMAT_MESSAGE_FROM_SYSTEM,
-            NULL,
-            GetLastError(),
-            MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT),  /* default language */
-            buf,
-            sizeof(buf),
-            NULL
-    );
-    return buf;
-}
-
-/*
- * struct sh_FileData --
- *
- * A pointer to the sh_FileData structure is passed into sh_RecordFileData,
- * which will fill in the fields.
- */
-
-struct sh_FileData {
-    char pathName[_MAX_PATH];
-    DWORD dwFileAttributes;
-};
-
-/*
- * sh_RecordFileData --
- *
- * Record the pathname and attributes of the file in
- * the sh_FileData structure pointed to by arg.
- *
- * Always return TRUE (successful completion).
- *
- * This function is intended to be passed into sh_EnumerateFiles
- * to see if a certain pattern expands to exactly one file/directory,
- * and if so, record its pathname and attributes.
- */
-
-static BOOL
-sh_RecordFileData(char *pathName, WIN32_FIND_DATA *findData, void *arg)
-{
-    struct sh_FileData *fData = (struct sh_FileData *) arg;
-
-    strcpy(fData->pathName, pathName);
-    fData->dwFileAttributes = findData->dwFileAttributes;
-    return TRUE;
-}
-
-static BOOL
-sh_DoCopy(char *srcFileName,
-          DWORD srcFileAttributes,
-          char *dstFileName,
-          DWORD dstFileAttributes,
-          int force,
-          int recursive
-)
-{
-    if (dstFileAttributes != 0xFFFFFFFF) {
-        if ((dstFileAttributes & FILE_ATTRIBUTE_READONLY) && force) {
-            dstFileAttributes &= ~FILE_ATTRIBUTE_READONLY;
-            SetFileAttributes(dstFileName, dstFileAttributes);
-        }
-    }
-
-    if (srcFileAttributes & FILE_ATTRIBUTE_DIRECTORY) {
-        fprintf(stderr, "nsinstall: %s is a directory\n",
-                srcFileName);
-        return FALSE;
-    } else {
-        if (!CopyFile(srcFileName, dstFileName, FALSE)) {
-            fprintf(stderr, "nsinstall: cannot copy %s to %s: %s\n",
-                    srcFileName, dstFileName, sh_GetLastErrorMessage());
-            return FALSE;
-        }
-    }
-    return TRUE;
-}
-
-/*
- * struct sh_CpCmdArg --
- *
- * A pointer to the sh_CpCmdArg structure is passed into sh_CpFileCmd.
- * The sh_CpCmdArg contains information about the cp command, and
- * provide a buffer for constructing the destination file name.
- */
-
-struct sh_CpCmdArg {
-    int force;                /* -f option, ok to overwrite an existing
-                               * read-only destination file */
-    int recursive;            /* -r or -R option, recursively copy
-                               * directories. Note: this field is not used
-                               * by nsinstall and should always be 0. */
-    char *dstFileName;        /* a buffer for constructing the destination
-                               * file name */
-    char *dstFileNameMarker;  /* points to where in the dstFileName buffer
-                               * we should write the file component of the
-                               * destination file */
-};
-
-/*
- * sh_CpFileCmd --
- *
- * Copy a file to the destination directory
- * 
- * This function is intended to be passed into sh_EnumerateFiles to
- * copy all the files specified by the pattern to the destination
- * directory.
- *
- * Return TRUE if the file is successfully copied, and FALSE otherwise.
- */
-
-static BOOL
-sh_CpFileCmd(char *pathName, WIN32_FIND_DATA *findData, void *cpArg)
-{
-    BOOL retVal = TRUE;
-    struct sh_CpCmdArg *arg = (struct sh_CpCmdArg *) cpArg;
-
-    strcpy(arg->dstFileNameMarker, findData->cFileName);
-    return sh_DoCopy(pathName, findData->dwFileAttributes,
-            arg->dstFileName, GetFileAttributes(arg->dstFileName),
-            arg->force, arg->recursive);
-}
-
-static int
-shellCp (char **pArgv) 
-{
-    int retVal = 0;
-    char **pSrc;
-    char **pDst;
-    struct sh_CpCmdArg arg;
-    struct sh_FileData dstData;
-    int dstIsDir = 0;
-    int n;
-
-    arg.force = 0;
-    arg.recursive = 0;
-    arg.dstFileName = dstData.pathName;
-    arg.dstFileNameMarker = 0;
-
-    while (*pArgv && **pArgv == '-') {
-        char *p = *pArgv;
-
-        while (*(++p)) {
-            if (*p == 'f') {
-                arg.force = 1;
-            }
-        }
-        pArgv++;
-    }
-
-    /* the first source file */
-    if (*pArgv) {
-        pSrc = pArgv++;
-    } else {
-        fprintf(stderr, "nsinstall: not enough arguments\n");
-        return 3;
-    }
-
-    /* get to the last token to find destination */
-    if (*pArgv) {
-        pDst = pArgv++;
-    } else {
-        fprintf(stderr, "nsinstall: not enough arguments\n");
-        return 3;
-    }
-    while (*pArgv) {
-        pDst = pArgv++;
-    }
-
-    /*
-     * The destination pattern must unambiguously expand to exactly
-     * one file or directory.
-     */
-
-    changeForwardSlashesTpBackSlashes(*pDst);
-    sh_EnumerateFiles(*pDst, *pDst, sh_RecordFileData, &dstData, &n);
-    assert(n >= 0);
-    if (n == 1) {
-        /*
-         * Is the destination a file or directory?
-         */
-
-        if (dstData.dwFileAttributes & FILE_ATTRIBUTE_DIRECTORY) {
-            dstIsDir = 1;
-        }
-    } else if (n > 1) {
-        fprintf(stderr, "nsinstall: %s: ambiguous destination file "
-                "or directory\n", *pDst);
-        return 3;
-    } else {
-        /*
-         * n == 0, meaning that destination file or directory does
-         * not exist.  In this case the destination file directory
-         * name must be fully specified.
-         */
-
-        char *p;
-
-        for (p = *pDst; *p; p++) {
-            if (*p == '*' || *p == '?') {
-                fprintf(stderr, "nsinstall: %s: No such file or directory\n",
-                        *pDst);
-                return 3;
-            }
-        }
-
-        /*
-         * Do not include the trailing \, if any, unless it is a root
-         * directory (\ or X:\).
-         */
-
-        if (p > *pDst && p[-1] == '\\' && p != *pDst + 1 && p[-2] != ':') {
-            p[-1] = '\0';
-        }
-        strcpy(dstData.pathName, *pDst);
-        dstData.dwFileAttributes = 0xFFFFFFFF;
-    }
-
-    /*
-     * If there are two or more source files, the destination has
-     * to be a directory.
-     */
-
-    if (pDst - pSrc > 1 && !dstIsDir) {
-        fprintf(stderr, "nsinstall: cannot copy more than"
-                " one file to the same destination file\n");
-        return 3;
-    }
-
-    if (dstIsDir) {
-        arg.dstFileNameMarker = arg.dstFileName + strlen(arg.dstFileName);
-
-        /*
-         * Now arg.dstFileNameMarker is pointing to the null byte at the
-         * end of string.  We want to make sure that there is a \ at the
-         * end of string, and arg.dstFileNameMarker should point right
-         * after that \. 
-         */
-
-        if (arg.dstFileNameMarker[-1] != '\\') {
-            *(arg.dstFileNameMarker++) = '\\';
-        }
-    }
-	
-    if (!dstIsDir) {
-        struct sh_FileData srcData;
-
-        assert(pDst - pSrc == 1);
-        changeForwardSlashesTpBackSlashes(*pSrc);
-        sh_EnumerateFiles(*pSrc, *pSrc, sh_RecordFileData, &srcData, &n);
-        if (n == 0) {
-            fprintf(stderr, "nsinstall: %s: No such file or directory\n",
-                    *pSrc);
-            retVal = 3;
-        } else if (n > 1) {
-            fprintf(stderr, "nsinstall: cannot copy more than one file or "
-                    "directory to the same destination\n");
-            retVal = 3;
-        } else {
-            assert(n == 1);
-            if (sh_DoCopy(srcData.pathName, srcData.dwFileAttributes,
-                    dstData.pathName, dstData.dwFileAttributes,
-                    arg.force, arg.recursive) == FALSE) {
-                retVal = 3;
-            }
-        }
-        return retVal;
-    }
-
-    for ( ; *pSrc != *pDst; pSrc++) {
-        BOOL rv;
-
-        changeForwardSlashesTpBackSlashes(*pSrc);
-        rv = sh_EnumerateFiles(*pSrc, *pSrc, sh_CpFileCmd, &arg, &n);
-        if (rv == FALSE) {
-            retVal = 3;
-        } else {
-            if (n == 0) {
-                fprintf(stderr, "nsinstall: %s: No such file or directory\n",
-                        *pSrc);
-                retVal = 3;
-            }
-        }
-    }
-
-    return retVal;
-}
-
-/*
- * sh_EnumerateFiles --
- *
- * Enumerate all the files in the specified pattern, which is a pathname
- * containing possibly wildcard characters such as * and ?.  fileFcn
- * is called on each file, passing the expanded file name, a pointer
- * to the file's WIN32_FILE_DATA, and the arg pointer.
- * 
- * It is assumed that there are no wildcard characters before the
- * character pointed to by 'where'.
- *
- * On return, *nFiles stores the number of files enumerated.  *nFiles is
- * set to this number whether sh_EnumerateFiles or 'fileFcn' succeeds
- * or not.
- *
- * Return TRUE if the files are successfully enumerated and all
- * 'fileFcn' invocations succeeded.  Return FALSE if something went
- * wrong.
- */
-
-static BOOL sh_EnumerateFiles(
-        const char *pattern,
-        const char *where,
-        sh_FileFcn fileFcn,
-        void *arg,
-        int *nFiles
-        )
-{
-    WIN32_FIND_DATA fileData;
-    HANDLE hSearch;
-    const char *src;
-    char *dst;
-    char fileName[_MAX_PATH];
-    char *fileNameMarker = fileName;
-    char *oldFileNameMarker;
-    BOOL hasWildcard = FALSE;
-    BOOL retVal = TRUE;
-    BOOL patternEndsInDotStar = FALSE;
-    BOOL patternEndsInDot = FALSE;  /* a special case of
-                                     * patternEndsInDotStar */
-    int numDotsInPattern;
-    int len;
-    
-    /*
-     * Windows expands patterns ending in ".", ".*", ".**", etc.
-     * differently from the glob expansion on Unix.  For example,
-     * both "foo." and "foo.*" match "foo", and "*.*" matches
-     * everything, including filenames with no dots.  So we need
-     * to throw away extra files returned by the FindNextFile()
-     * function.  We require that a matched filename have at least
-     * the number of dots in the pattern.
-     */
-    len = strlen(pattern);
-    if (len >= 2) {
-        /* Start from the end of pattern and go backward */
-        const char *p = &pattern[len - 1];
-
-        /* We can have zero or more *'s */
-        while (p >= pattern && *p == '*') {
-            p--;
-        }
-        if (p >= pattern && *p == '.') {
-            patternEndsInDotStar = TRUE;
-            if (p == &pattern[len - 1]) {
-                patternEndsInDot = TRUE;
-            }
-            p--;
-            numDotsInPattern = 1;
-            while (p >= pattern && *p != '\\') {
-                if (*p == '.') {
-                    numDotsInPattern++;
-                }
-                p--;
-            }
-        }
-    }
-
-    *nFiles = 0;
-
-    /*
-     * Copy pattern to fileName, but only up to and not including
-     * the first \ after the first wildcard letter.
-     *
-     * Make fileNameMarker point to one of the following:
-     * - the start of fileName, if fileName does not contain any \.
-     * - right after the \ before the first wildcard letter, if there is
-     *   a wildcard character.
-     * - right after the last \, if there is no wildcard character.
-     */
-
-    dst = fileName;
-    src = pattern;
-    while (src < where) {
-        if (*src == '\\') {
-            oldFileNameMarker = fileNameMarker;
-            fileNameMarker = dst + 1;
-        }
-        *(dst++) = *(src++);
-    }
-
-    while (*src && *src != '*' && *src != '?') {
-        if (*src == '\\') {
-            oldFileNameMarker = fileNameMarker;
-            fileNameMarker = dst + 1;
-        }
-        *(dst++) = *(src++);
-    }
-
-    if (*src) {
-        /*
-         * Must have seen the first wildcard letter
-         */
-
-        hasWildcard = TRUE;
-        while (*src && *src != '\\') {
-            *(dst++) = *(src++);
-        }
-    }
-    
-    /* Now src points to either null or \ */
-
-    assert(*src == '\0' || *src == '\\');
-    assert(hasWildcard || *src == '\0');
-    *dst = '\0';
-
-    /*
-     * If the pattern does not contain any wildcard characters, then
-     * we don't need to go the FindFirstFile route.
-     */
-
-    if (!hasWildcard) {
-        /*
-         * See if it is the root directory, \, or X:\.
-         */
-
-        assert(!strcmp(fileName, pattern));
-        assert(strlen(fileName) >= 1);
-        if (dst[-1] == '\\' && (dst == fileName + 1 || dst[-2] == ':')) {
-            fileData.cFileName[0] = '\0';
-        } else {
-            /*
-             * Do not include the trailing \, if any
-             */
-
-            if (dst[-1] == '\\') {
-                assert(*fileNameMarker == '\0');
-                dst[-1] = '\0';
-                fileNameMarker = oldFileNameMarker;
-            } 
-            strcpy(fileData.cFileName, fileNameMarker);
-        }
-        fileData.dwFileAttributes = GetFileAttributes(fileName);
-        if (fileData.dwFileAttributes == 0xFFFFFFFF) {
-            return TRUE;
-        }
-        *nFiles = 1;
-        return (*fileFcn)(fileName, &fileData, arg);
-    }
-
-    hSearch = FindFirstFile(fileName, &fileData);
-    if (hSearch == INVALID_HANDLE_VALUE) {
-        return retVal;
-    }
-
-    do {
-        if (!strcmp(fileData.cFileName, ".")
-                || !strcmp(fileData.cFileName, "..")) {
-            /* 
-             * Skip over . and ..
-             */
-
-            continue;
-        }
-
-        if (patternEndsInDotStar) {
-            int nDots = 0;
-            char *p = fileData.cFileName;
-            while (*p) {
-                if (*p == '.') {
-                    nDots++;
-                }
-                p++;
-            }
-            /* Now p points to the null byte at the end of file name */
-            if (patternEndsInDot && (p == fileData.cFileName
-                    || p[-1] != '.')) {
-                /*
-                 * File name does not end in dot.  Skip this file.
-                 * Note: windows file name probably cannot end in dot,
-                 * but we do this check anyway.
-                 */
-                continue;
-            }
-            if (nDots < numDotsInPattern) {
-                /*
-                 * Not enough dots in file name.  Must be an extra
-                 * file in matching .* pattern.  Skip this file.
-                 */
-                continue;
-            }
-        }
-
-        strcpy(fileNameMarker, fileData.cFileName);
-        if (*src && *(src + 1)) {
-            /*
-             * More to go.  Recurse.
-             */
-
-            int n;
-
-            assert(*src == '\\');
-            where = fileName + strlen(fileName);
-            strcat(fileName, src);
-            sh_EnumerateFiles(fileName, where, fileFcn, arg, &n);
-            *nFiles += n;
-        } else {
-            assert(strchr(fileName, '*') == NULL);
-            assert(strchr(fileName, '?') == NULL);
-            (*nFiles)++;
-            if ((*fileFcn)(fileName, &fileData, arg) == FALSE) {
-                retVal = FALSE;
-            }
-        }
-    } while (FindNextFile(hSearch, &fileData));
-
-    FindClose(hSearch);
-    return retVal;
-}

buildtools/windows/source/shmsdos/nsinstall.mak

@@ -1,141 +0,0 @@
-# NMAKE file for building nsinstall.exe.
-#
-# This file is edited from an NMAKE file generated by
-# Microsoft Developer Studio, Format Version 4.20
-#
-# To build, say
-#     nmake /f nsinstall.mak CFG=Release
-# or
-#     nmake /f nsinstall.mak CFG=Debug
-# If CFG is omitted, a release build is assumed.
-
-!IF "$(CFG)" == ""
-CFG=Release
-!MESSAGE No configuration specified.  Defaulting Release.
-!ENDIF 
-
-!IF "$(CFG)" != "Release" && "$(CFG)" != "Debug"
-!MESSAGE Invalid configuration "$(CFG)" specified.
-!MESSAGE You can specify a configuration when running NMAKE on this makefile
-!MESSAGE by defining the macro CFG on the command line.  For example:
-!MESSAGE 
-!MESSAGE NMAKE /f "nsinstall.mak" CFG="Debug"
-!MESSAGE 
-!MESSAGE Possible choices for configuration are:
-!MESSAGE 
-!MESSAGE "Release" (based on "Win32 Console Application")
-!MESSAGE "Debug" (based on "Win32 Console Application")
-!MESSAGE 
-!ERROR An invalid configuration is specified.
-!ENDIF 
-
-!IF "$(OS)" == "Windows_NT"
-NULL=
-!ELSE 
-NULL=nul
-!ENDIF 
-################################################################################
-# Begin Project
-CPP=cl.exe
-RSC=rc.exe
-
-!IF  "$(CFG)" == "Release"
-
-OUTDIR=.\Release
-INTDIR=.\Release
-
-ALL : "$(OUTDIR)\nsinstall.exe"
-
-CLEAN : 
-	-@erase "$(INTDIR)\nsinstall.obj"
-	-@erase "$(OUTDIR)\nsinstall.exe"
-
-"$(OUTDIR)" :
-    if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"
-
-CPP_PROJ=/nologo /ML /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE"\
- /Fp"$(INTDIR)/nsinstall.pch" /YX /Fo"$(INTDIR)/" /c 
-CPP_OBJS=.\Release/
-CPP_SBRS=.\.
-BSC32=bscmake.exe
-BSC32_FLAGS=/nologo /o"$(OUTDIR)/nsinstall.bsc" 
-BSC32_SBRS= \
-	
-LINK32=link.exe
-LINK32_FLAGS=/nologo\
- /subsystem:console /incremental:no /pdb:"$(OUTDIR)/nsinstall.pdb"\
- /out:"$(OUTDIR)/nsinstall.exe" 
-LINK32_OBJS= \
-	"$(INTDIR)\nsinstall.obj"
-
-"$(OUTDIR)\nsinstall.exe" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
-    $(LINK32) @<<
-  $(LINK32_FLAGS) $(LINK32_OBJS)
-<<
-
-!ELSEIF  "$(CFG)" == "Debug"
-
-OUTDIR=.\Debug
-INTDIR=.\Debug
-
-ALL : "$(OUTDIR)\nsinstall.exe"
-
-CLEAN : 
-	-@erase "$(INTDIR)\nsinstall.obj"
-	-@erase "$(INTDIR)\vc40.idb"
-	-@erase "$(INTDIR)\vc40.pdb"
-	-@erase "$(OUTDIR)\nsinstall.exe"
-	-@erase "$(OUTDIR)\nsinstall.ilk"
-	-@erase "$(OUTDIR)\nsinstall.pdb"
-
-"$(OUTDIR)" :
-    if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"
-
-CPP_PROJ=/nologo /MD /W3 /Gm /GX /Zi /Od /D "WIN32" /D "_DEBUG" /D "DEBUG"\
- /D "_CONSOLE" /Fp"$(INTDIR)/nsinstall.pch" /YX /Fo"$(INTDIR)/"\
- /Fd"$(INTDIR)/" /c 
-CPP_OBJS=.\Debug/
-CPP_SBRS=.\.
-BSC32=bscmake.exe
-BSC32_FLAGS=/nologo /o"$(OUTDIR)/nsinstall.bsc" 
-BSC32_SBRS= \
-	
-LINK32=link.exe
-LINK32_FLAGS=/nologo\
- /subsystem:console /incremental:yes /pdb:"$(OUTDIR)/nsinstall.pdb" /debug\
- /out:"$(OUTDIR)/nsinstall.exe" 
-LINK32_OBJS= \
-	"$(INTDIR)\nsinstall.obj"
-
-"$(OUTDIR)\nsinstall.exe" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
-    $(LINK32) @<<
-  $(LINK32_FLAGS) $(LINK32_OBJS)
-<<
-
-!ENDIF 
-
-.c{$(CPP_OBJS)}.obj:
-   $(CPP) $(CPP_PROJ) $<  
-
-.c{$(CPP_SBRS)}.sbr:
-   $(CPP) $(CPP_PROJ) $<  
-
-################################################################################
-# Begin Target
-
-################################################################################
-# Begin Source File
-
-SOURCE=.\nsinstall.c
-DEP_CPP_SHMSD=\
-	{$(INCLUDE)}"\sys\stat.h"\
-	{$(INCLUDE)}"\sys\types.h"\
-	
-
-"$(INTDIR)\nsinstall.obj" : $(SOURCE) $(DEP_CPP_SHMSD) "$(INTDIR)"
-
-
-# End Source File
-# End Target
-# End Project
-################################################################################

buildtools/windows/source/shmsdos/shmsdos.mak

@@ -1,141 +0,0 @@
-# NMAKE file for building shmsdos.exe.
-#
-# This file is edited from an NMAKE file generated by
-# Microsoft Developer Studio, Format Version 4.20
-#
-# To build, say
-#     nmake /f shmsdos.mak CFG=Release
-# or
-#     nmake /f shmsdos.mak CFG=Debug
-# If CFG is omitted, a release build is assumed.
-
-!IF "$(CFG)" == ""
-CFG=Release
-!MESSAGE No configuration specified.  Defaulting Release.
-!ENDIF 
-
-!IF "$(CFG)" != "Release" && "$(CFG)" != "Debug"
-!MESSAGE Invalid configuration "$(CFG)" specified.
-!MESSAGE You can specify a configuration when running NMAKE on this makefile
-!MESSAGE by defining the macro CFG on the command line.  For example:
-!MESSAGE 
-!MESSAGE NMAKE /f "shmsdos.mak" CFG="Debug"
-!MESSAGE 
-!MESSAGE Possible choices for configuration are:
-!MESSAGE 
-!MESSAGE "Release" (based on "Win32 Console Application")
-!MESSAGE "Debug" (based on "Win32 Console Application")
-!MESSAGE 
-!ERROR An invalid configuration is specified.
-!ENDIF 
-
-!IF "$(OS)" == "Windows_NT"
-NULL=
-!ELSE 
-NULL=nul
-!ENDIF 
-################################################################################
-# Begin Project
-CPP=cl.exe
-RSC=rc.exe
-
-!IF  "$(CFG)" == "Release"
-
-OUTDIR=.\Release
-INTDIR=.\Release
-
-ALL : "$(OUTDIR)\shmsdos.exe"
-
-CLEAN : 
-	-@erase "$(INTDIR)\shmsdos.obj"
-	-@erase "$(OUTDIR)\shmsdos.exe"
-
-"$(OUTDIR)" :
-    if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"
-
-CPP_PROJ=/nologo /ML /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE"\
- /Fp"$(INTDIR)/shmsdos.pch" /YX /Fo"$(INTDIR)/" /c 
-CPP_OBJS=.\Release/
-CPP_SBRS=.\.
-BSC32=bscmake.exe
-BSC32_FLAGS=/nologo /o"$(OUTDIR)/shmsdos.bsc" 
-BSC32_SBRS= \
-	
-LINK32=link.exe
-LINK32_FLAGS=/nologo\
- /subsystem:console /incremental:no /pdb:"$(OUTDIR)/shmsdos.pdb"\
- /out:"$(OUTDIR)/shmsdos.exe" 
-LINK32_OBJS= \
-	"$(INTDIR)\shmsdos.obj"
-
-"$(OUTDIR)\shmsdos.exe" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
-    $(LINK32) @<<
-  $(LINK32_FLAGS) $(LINK32_OBJS)
-<<
-
-!ELSEIF  "$(CFG)" == "Debug"
-
-OUTDIR=.\Debug
-INTDIR=.\Debug
-
-ALL : "$(OUTDIR)\shmsdos.exe"
-
-CLEAN : 
-	-@erase "$(INTDIR)\shmsdos.obj"
-	-@erase "$(INTDIR)\vc40.idb"
-	-@erase "$(INTDIR)\vc40.pdb"
-	-@erase "$(OUTDIR)\shmsdos.exe"
-	-@erase "$(OUTDIR)\shmsdos.ilk"
-	-@erase "$(OUTDIR)\shmsdos.pdb"
-
-"$(OUTDIR)" :
-    if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"
-
-CPP_PROJ=/nologo /MD /W3 /Gm /GX /Zi /Od /D "WIN32" /D "_DEBUG" /D "DEBUG"\
- /D "_CONSOLE" /Fp"$(INTDIR)/shmsdos.pch" /YX /Fo"$(INTDIR)/"\
- /Fd"$(INTDIR)/" /c 
-CPP_OBJS=.\Debug/
-CPP_SBRS=.\.
-BSC32=bscmake.exe
-BSC32_FLAGS=/nologo /o"$(OUTDIR)/shmsdos.bsc" 
-BSC32_SBRS= \
-	
-LINK32=link.exe
-LINK32_FLAGS=/nologo\
- /subsystem:console /incremental:yes /pdb:"$(OUTDIR)/shmsdos.pdb" /debug\
- /out:"$(OUTDIR)/shmsdos.exe" 
-LINK32_OBJS= \
-	"$(INTDIR)\shmsdos.obj"
-
-"$(OUTDIR)\shmsdos.exe" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
-    $(LINK32) @<<
-  $(LINK32_FLAGS) $(LINK32_OBJS)
-<<
-
-!ENDIF 
-
-.c{$(CPP_OBJS)}.obj:
-   $(CPP) $(CPP_PROJ) $<  
-
-.c{$(CPP_SBRS)}.sbr:
-   $(CPP) $(CPP_PROJ) $<  
-
-################################################################################
-# Begin Target
-
-################################################################################
-# Begin Source File
-
-SOURCE=.\shmsdos.c
-DEP_CPP_SHMSD=\
-	{$(INCLUDE)}"\sys\stat.h"\
-	{$(INCLUDE)}"\sys\types.h"\
-	
-
-"$(INTDIR)\shmsdos.obj" : $(SOURCE) $(DEP_CPP_SHMSD) "$(INTDIR)"
-
-
-# End Source File
-# End Target
-# End Project
-################################################################################

buildtools/windows/source/uname/README

@@ -1,9 +0,0 @@
-This directory contains the source for uname.exe on Win32.
-This version of uname.exe returns the string "WINNT" when
-you say 'uname -s' on Windows NT.
-
-To build it, you need Microsoft Visual C++ and nmake.
-Issue the command:
-    nmake /f uname.mak
-The output is Release\uname.exe.  Copy it to a directory
-on your Path.

buildtools/windows/source/uname/uname.c

@@ -1,155 +0,0 @@
-/***********************************************************
- *	uname - returns name of OS
- **********************************************************/
-#include <windows.h>
-#include <stdlib.h> 
-#include <stdio.h>
-
-#define	index(s, c)	strchr((s), (c))
-#define streq(a, b) (strcmp ((a), (b)) == 0)
-
-static char ** getlistOfOptions (char **pArgv, char * pOptions);
-static void getUnameOption ( char option );
-
-/***********************************************************************
- * -a    Print all information.
- *
- * -m    Print the machine hardware name.
- *
- * -n    Print the nodename (the nodename is the name by  which
- *      the system is known to a communications network).
- *
- * -p    Print the current host's processor type.
- *
- * -r    Print the operating system release.
- *
- * -s    Print the name of the operating system.  This  is  the
- *      default.
- *
- * -v    Print the operating system version.
- *
- * -S systemname
- *      The nodename may be changed by specifying a system name
- *      argument.   The  system  name argument is restricted to
- *      SYS_NMLN characters.   SYS_NMLN  is  an  implementation
- *      specific  value  defined  in <sys/utsname.h>.  Only the
- *      super-user is allowed this capability.
- ***********************************************************************/
-
-main( int argc, char *argv[ ], char *envp[ ] )
-{
-	char options[1024];
-	char *pOptions;
-	char **pArgv;
- 	char c;
-
-	pArgv = &argv[1];
-	pArgv = getlistOfOptions (pArgv, options);
-
-	/* if no options specified, then return operating system */
-	pOptions = options;
-	if ( *pOptions == '\0' ) {
-		options[0] = 's';
-		options[1] = '\0';
-	}
-	while (c = *pOptions++ ) {
-		if ( c == 'a' )	{
-			getUnameOption ( 's' );
-			printf (" " );
-			getUnameOption ( 'n' );
-			printf (" " );
-			getUnameOption ( 'r' );
-			printf (" " );
-			getUnameOption ( 'v' );
-			printf (" " );
-			getUnameOption ( 'm' );
-			printf (" " );
-			getUnameOption ( 'p' );
-		} else
-			getUnameOption ( c );
-	}
-	return 0;
-}
-
-static char **
-getlistOfOptions (char **pArgv, char * pOptions)
-{
-	char *pArg;
-	while ( *pArgv && (**pArgv == '-') ) {
-		pArg = *pArgv;
-		pArg++;		/* skip over '-' */
-		while ( *pArg )
-			*pOptions++ = *pArg++;
-		pArgv++;
-	}
-	*pOptions = '\0';
-	return pArgv;
-}
-void getUnameOption ( char option ) 
-{
-	char computerName[128];
-	SYSTEM_INFO systemInfo;
-	OSVERSIONINFO versionInfo;
-	DWORD computerNameLength = sizeof(computerName); 
-
-	GetSystemInfo( &systemInfo);
-	GetComputerName( (LPTSTR)&computerName, &computerNameLength );
-	versionInfo.dwOSVersionInfoSize = sizeof(OSVERSIONINFO);
-	GetVersionEx( &versionInfo );
-
-	switch ( option ) {
-	case 'a':
-		printf ( getenv	("OS") );
-		break;
-	case 'm':
-		printf ( "xx" );
-		break;
-	case 'n':
-		printf ( computerName );
-		break;
-	case 'p':
-		switch ( systemInfo.wProcessorArchitecture ) {
-		case PROCESSOR_ARCHITECTURE_INTEL:
-			printf("I386");
-			break;
-		case PROCESSOR_ARCHITECTURE_MIPS:
-			printf("MIPS");
-			break;
-		case PROCESSOR_ARCHITECTURE_ALPHA:
-			printf("ALPHA");
-			break;
-		case PROCESSOR_ARCHITECTURE_PPC:
-			printf("PPC");
-			break;
-		default:
-			printf("UNKNOWN_PROCESSOR");
-			break;
-		}
-		break;
-	case 'r':
-		printf ("%d.%d", versionInfo.dwMajorVersion, versionInfo.dwMinorVersion );
-		break;
-	case 's':
-		switch ( versionInfo.dwPlatformId ) {
-		case VER_PLATFORM_WIN32s:
-			printf("WIN32S");
-			break;
-		case VER_PLATFORM_WIN32_WINDOWS:
-			printf("WIN95");
-			break;
-		case VER_PLATFORM_WIN32_NT:
-			printf("WINNT");
-			break;
-		default:
-			printf("UNKNOWN_OS");
-			break;
-		} 
-		break;
-	case 'v':
-		printf ("%d", versionInfo.dwBuildNumber );
-		break;
-	default:
-		printf ( "uname -%c is unimplemented", option );
-		break;
-	}
-}

buildtools/windows/source/uname/uname.mak

@@ -1,141 +0,0 @@
-# NMAKE file for building uname.exe.
-#
-# This file is edited from an NMAKE file generated by
-# Microsoft Developer Studio, Format Version 4.20
-#
-# To build, say
-#     nmake /f uname.mak CFG=Release
-# or
-#     nmake /f uname.mak CFG=Debug
-# If CFG is omitted, a release build is assumed.
-
-!IF "$(CFG)" == ""
-CFG=Release
-!MESSAGE No configuration specified.  Defaulting Release.
-!ENDIF 
-
-!IF "$(CFG)" != "Release" && "$(CFG)" != "Debug"
-!MESSAGE Invalid configuration "$(CFG)" specified.
-!MESSAGE You can specify a configuration when running NMAKE on this makefile
-!MESSAGE by defining the macro CFG on the command line.  For example:
-!MESSAGE 
-!MESSAGE NMAKE /f "uname.mak" CFG="Debug"
-!MESSAGE 
-!MESSAGE Possible choices for configuration are:
-!MESSAGE 
-!MESSAGE "Release" (based on "Win32 Console Application")
-!MESSAGE "Debug" (based on "Win32 Console Application")
-!MESSAGE 
-!ERROR An invalid configuration is specified.
-!ENDIF 
-
-!IF "$(OS)" == "Windows_NT"
-NULL=
-!ELSE 
-NULL=nul
-!ENDIF 
-################################################################################
-# Begin Project
-CPP=cl.exe
-RSC=rc.exe
-
-!IF  "$(CFG)" == "Release"
-
-OUTDIR=.\Release
-INTDIR=.\Release
-
-ALL : "$(OUTDIR)\uname.exe"
-
-CLEAN : 
-	-@erase "$(INTDIR)\uname.obj"
-	-@erase "$(OUTDIR)\uname.exe"
-
-"$(OUTDIR)" :
-    if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"
-
-CPP_PROJ=/nologo /ML /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE"\
- /Fp"$(INTDIR)/uname.pch" /YX /Fo"$(INTDIR)/" /c 
-CPP_OBJS=.\Release/
-CPP_SBRS=.\.
-BSC32=bscmake.exe
-BSC32_FLAGS=/nologo /o"$(OUTDIR)/uname.bsc" 
-BSC32_SBRS= \
-	
-LINK32=link.exe
-LINK32_FLAGS=/nologo\
- /subsystem:console /incremental:no /pdb:"$(OUTDIR)/uname.pdb"\
- /out:"$(OUTDIR)/uname.exe" 
-LINK32_OBJS= \
-	"$(INTDIR)\uname.obj"
-
-"$(OUTDIR)\uname.exe" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
-    $(LINK32) @<<
-  $(LINK32_FLAGS) $(LINK32_OBJS)
-<<
-
-!ELSEIF  "$(CFG)" == "Debug"
-
-OUTDIR=.\Debug
-INTDIR=.\Debug
-
-ALL : "$(OUTDIR)\uname.exe"
-
-CLEAN : 
-	-@erase "$(INTDIR)\uname.obj"
-	-@erase "$(INTDIR)\vc40.idb"
-	-@erase "$(INTDIR)\vc40.pdb"
-	-@erase "$(OUTDIR)\uname.exe"
-	-@erase "$(OUTDIR)\uname.ilk"
-	-@erase "$(OUTDIR)\uname.pdb"
-
-"$(OUTDIR)" :
-    if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"
-
-CPP_PROJ=/nologo /MD /W3 /Gm /GX /Zi /Od /D "WIN32" /D "_DEBUG" /D "DEBUG"\
- /D "_CONSOLE" /Fp"$(INTDIR)/uname.pch" /YX /Fo"$(INTDIR)/"\
- /Fd"$(INTDIR)/" /c 
-CPP_OBJS=.\Debug/
-CPP_SBRS=.\.
-BSC32=bscmake.exe
-BSC32_FLAGS=/nologo /o"$(OUTDIR)/uname.bsc" 
-BSC32_SBRS= \
-	
-LINK32=link.exe
-LINK32_FLAGS=/nologo\
- /subsystem:console /incremental:yes /pdb:"$(OUTDIR)/uname.pdb" /debug\
- /out:"$(OUTDIR)/uname.exe" 
-LINK32_OBJS= \
-	"$(INTDIR)\uname.obj"
-
-"$(OUTDIR)\uname.exe" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
-    $(LINK32) @<<
-  $(LINK32_FLAGS) $(LINK32_OBJS)
-<<
-
-!ENDIF 
-
-.c{$(CPP_OBJS)}.obj:
-   $(CPP) $(CPP_PROJ) $<  
-
-.c{$(CPP_SBRS)}.sbr:
-   $(CPP) $(CPP_PROJ) $<  
-
-################################################################################
-# Begin Target
-
-################################################################################
-# Begin Source File
-
-SOURCE=.\uname.c
-DEP_CPP_SHMSD=\
-	{$(INCLUDE)}"\sys\stat.h"\
-	{$(INCLUDE)}"\sys\types.h"\
-	
-
-"$(INTDIR)\uname.obj" : $(SOURCE) $(DEP_CPP_SHMSD) "$(INTDIR)"
-
-
-# End Source File
-# End Target
-# End Project
-################################################################################

l10nkits/client/windows/docs/installer/branding.html

@@ -1,40 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Product Branding Issues</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-Product Branding Instructions</H3>
-Under the terms of the Unlimited Localization Program, you must remove
-or replace all trademarked Netscape terms, brand names, icons, images,
-etc.&nbsp; These trademarks are listed on the page found at the following
-URL:
-
-<P><A HREF="http://home.netscape.com/misc/trademarks.html#trademarks">http://home.netscape.com/misc/trademarks.html#trademarks</A>
-
-<P>Please refer to that page for details.&nbsp; You may not release a localized
-version of the Netscape Communicator with these trademarks left in the
-product.
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="usingKit.html#branding">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER><BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/gettingStarted.html

@@ -1,100 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Getting Started</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-<A NAME="getting started"></A>2. Getting Started</H2>
-Before you can begin using the Windows Installer Localization Kit, you
-must install it and setup your working directories. This is a simple matter
-of unzipping the compressed kit file(s) into the proper directories. Your
-system must also meet certain requirements to run the tools needed to perform
-the localization steps described below.
-
-<P>
-<HR WIDTH="50%">
-<H3>
-<A NAME="sysreqs"></A>System Requirements</H3>
-There few system requirements for the kit in the strictest sense; however,
-your choice of tools will have their own set of requirements.&nbsp; The
-most likely minimum configuration will be as follows:
-<UL>
-<LI>
-100% IBM compatible PC</LI>
-
-<LI>
-Pentium<SUP><FONT SIZE=-1>&reg;</FONT></SUP> processor</LI>
-
-<LI>
-Microsoft<SUP><FONT SIZE=-1>&reg;</FONT></SUP> Windows NT 3.51 or 4.0 (localized
-versions will help testing but aren't required)</LI>
-
-<LI>
-16 MB RAM</LI>
-
-<LI>
-30 MB available hard disk space</LI>
-
-<LI>
-InstallShield International version 3.0 or other install builder software</LI>
-
-<LI>
-A visual resource editor, such as those provided with Microsoft<SUP><FONT SIZE=-1>&reg;</FONT></SUP>
-Visual C++, Borland<SUP><FONT SIZE=-1>&reg;</FONT></SUP> C++, etc.</LI>
-
-<LI>
-An active Internet connection and the ability to ftp (send and receive)
-large files</LI>
-
-<LI>
-A Web browser (say, for example, Netscape Communicator ;-)</LI>
-</UL>
-
-<H3>
-
-<HR WIDTH="50%"></H3>
-
-<H3>
-<A NAME="install"></A>Installing the Kit</H3>
-It is recommended that you install the Windows Installer Localization Kit
-into the same directory as your other Netscape/Mozilla localization kits:
-in other words, install this kit into your <B>kitRoot </B>directory.&nbsp;
-Place this localization kit's .ZIP file in that directory and UNZIP it
-with the -d parameter:
-
-<P>PKUNZIP -d <I>filename</I>
-<UL><B>Example:&nbsp; <TT>PKUNZIP -d instkit</TT></B></UL>
-
-<HR WIDTH="50%">
-<H3>
-<A NAME="configtool"></A>Configuring Your Tools</H3>
-Please refer to your Installshield or other install builder tool's documentation
-for set up and usage instructions.
-<BR>&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="nomenclature.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="usingKit.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS]</A></CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER></CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/isocodes.htm

@@ -1,203 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>ISO Locale codes</TITLE>
-</HEAD>
-<BODY>
-
-<CENTER>
-<H1>
-ISO Language and Country Codes</H1></CENTER>
-2 letter language codes are derived from the ISO 639 standard; country
-codes are from ISO 3166. Here are the codes for the locales currently supported
-by the L10n kits. If an entry also includes the country code then you must
-use that as well when creating the locale directory or naming a file.
-<H3>
-ISO Language and Country Codes table</H3>
-
-<TABLE BORDER=5 >
-<TR>
-<TD><U>Language Name</U></TD>
-
-<TD><U>Language Code</U></TD>
-
-<TD><U>Country Code</U></TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Chinese (Traditional)</CENTER>
-</TD>
-
-<TD>
-<CENTER>zh</CENTER>
-</TD>
-
-<TD>
-<CENTER>CN</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Chinese (Simplified)</CENTER>
-</TD>
-
-<TD>
-<CENTER>zh</CENTER>
-</TD>
-
-<TD>
-<CENTER>TW</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Danish</CENTER>
-</TD>
-
-<TD>
-<CENTER>da</CENTER>
-</TD>
-
-<TD>
-<CENTER>DK</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Dutch</CENTER>
-</TD>
-
-<TD>
-<CENTER>nl</CENTER>
-</TD>
-
-<TD>
-<CENTER>NL</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>French</CENTER>
-</TD>
-
-<TD>
-<CENTER>fr</CENTER>
-</TD>
-
-<TD>
-<CENTER>FR</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>German</CENTER>
-</TD>
-
-<TD>
-<CENTER>de</CENTER>
-</TD>
-
-<TD>
-<CENTER>DE</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Italian</CENTER>
-</TD>
-
-<TD>
-<CENTER>it</CENTER>
-</TD>
-
-<TD>
-<CENTER>IT</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Japanese</CENTER>
-</TD>
-
-<TD>
-<CENTER>ja</CENTER>
-</TD>
-
-<TD>
-<CENTER>JP</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Korean</CENTER>
-</TD>
-
-<TD>
-<CENTER>ko</CENTER>
-</TD>
-
-<TD>
-<CENTER>KR</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Portuguese</CENTER>
-</TD>
-
-<TD>
-<CENTER>pt</CENTER>
-</TD>
-
-<TD>
-<CENTER>BR</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Spanish</CENTER>
-</TD>
-
-<TD>
-<CENTER>es</CENTER>
-</TD>
-
-<TD>
-<CENTER>ES</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Swedish</CENTER>
-</TD>
-
-<TD>
-<CENTER>sv</CENTER>
-</TD>
-
-<TD>
-<CENTER>SE</CENTER>
-</TD>
-</TR>
-</TABLE>
-
-<CENTER><BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1997, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/kitOverview.html

@@ -1,99 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Kit Overview</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="kitoverview"></A>Kit Overview</H3>
-This kit is primarily intended for knowledgeable developers who are familiar
-with the localization process, with InstallShield or other installation
-programs, and with Windows resource editors.&nbsp; There are two basic
-approaches you can take to create an installer for your localized Communicator,
-Navigator or Mozilla derivative product:
-<OL>
-<LI>
-Use an existing Communicator or Navigator Export product installer as a
-base and add your localized files, or</LI>
-
-<LI>
-Create your own install program and use the registry setting information
-provided by the kit.</LI>
-</OL>
-
-<UL>
-<H4>
-<A NAME="method1"></A>Overview of Method 1.</H4>
-For this method you will need the following components:
-<BR>&nbsp;
-<UL>
-<LI>
-Your own copy of InstallShield version 3 International</LI>
-
-<LI>
-The appropriate version of a Netscape Communicator or Navigator installer.</LI>
-
-<LI>
-This localization kit.</LI>
-
-<LI>
-A text editor.</LI>
-
-<LI>
-A resource editor (e.g., MSDEV)</LI>
-</UL>
-
-
-<P>You will start with an Export version of a Netscape Communicator or
-Navigator installer.&nbsp; Then, you will extract the localizable components
-and modify them as desired.&nbsp; You will localize a number of strings
-contained in .INI files using a text editor. You will use a resource editor
-or the Netscape Translation Tools to localize STRINGTABLE and DIALOG resource
-types contained in two .DLLs. Once the localizable components of the installer
-are finished, you will reassemble the installer using the InstallShield
-EXE BUILDER tool, including your localized Communicator, Navigator or Mozilla
-derivative product.&nbsp; This process is detailed in the next section.</UL>
-
-<UL>
-<H4>
-<A NAME="method2"></A>Overview of Method 2.</H4>
-For this method you will need the following components:
-<BR>&nbsp;
-<UL>
-<LI>
-Your own copy of any install builder software</LI>
-
-<LI>
-This localization kit</LI>
-</UL>
-
-
-<P>You will create your own installation program in whatever fashion you
-wish.&nbsp; In order for your localized product to function properly, your
-installer will need to implement certain <A HREF="registrySettings.html">Windows
-registry settings</A>.</UL>
-&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="projectOverview.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="kitStruct.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-&nbsp;
-<CENTER><FONT SIZE=-1>&nbsp;1998, Copyright Netscape Communications Corp.
-All Rights Reserved</FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/kitStruct.html

@@ -1,63 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Kit Structure</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="kitstruct"></A>Kit Structure and Organization</H3>
-When you install this localization kit you will find a number of new directories
-on your hard disk. Each directory is named so as to be fairly self-explanatory,
-but the following diagram and description may help avoid any confusion
-you may have about what's what.
-<H4>
-<IMG SRC="l10ntree.jpg" BORDER=0 HEIGHT=98 WIDTH=177></H4>
-
-<H4>
-Description of Kit Directories</H4>
-
-<UL>
-<LI>
-The <B><TT>kitRoot</TT> </B>directory is wherever you install the Netscape
-Localization Kits.</LI>
-
-<LI>
-The <B><TT>l10nkits</TT> </B>directory contains the tools (if any) and
-documentation you need to complete your work.</LI>
-
-<LI>
-Since this kit concerns the Windows client product (as opposed to our server
-products) all the relevant documentation and tools are found under the
-<B><TT>client\windows </TT></B>directory.</LI>
-
-<LI>
-The <B><TT>docs</TT> </B>directory contains documentation on the kit, including
-the file you are reading now.</LI>
-</UL>
-&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="kitOverview.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="nomenclature.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeAim.html

@@ -1,51 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>Localize AIM.INI</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-Localization notes for AIM.INI</H4>
-
-<B>General Notes:</B>
-<UL>
-<LI>
-Only translate the strings which are shown in <B>bold</B> type face below.</LI>
-
-<LI>
-Change Netscape trademarks to your own product name(s).</LI>
-</UL>
-
-<B>Specific Notes:</B>
-<P>
-File Copy String=<B>Copying Netscape AOL Instant Messenger Service files...</B>
-
-<P>
-Installation String=<B>Installing Netscape AOL Instant Messenger Service files...</B>
-
-<P>
-Configuration String=<B>Configuring Netscape AOL Instant Messenger Service...</B>
-
-<P>
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table2">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<P>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeCD.html

@@ -1,65 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>Localize CD.INI</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-Localization notes for CD.INI</H4>
-<B>General Notes:</B>
-<UL>
-<LI>
-Only translate the strings which are shown in <B>bold</B> type face below.</LI>
-
-<LI>
-Update the product version number as appropriate.</LI>
-
-<LI>
-Modify the locale code according to the ISO 639 and ISO 3166 standards.
-(See the <A HREF="reference.html">Reference section</A> for details).</LI>
-
-<LI>
-You may need to move the placement of "%s" variables in your translation.</LI>
-
-<LI>
-Do not exceed the length of US string for Deinstall Dialog Wait Message.</LI>
-
-<LI>
-Change Netscape trademarks to your own product name(s).</LI>
-</UL>
-<B>Specific Notes:</B>
-
-<P>Product Setup Title1= <B>Deinstaller</B>
-
-<P>Product Version=<B>4.03 </B>(<B>en</B>)
-
-<P>Deinstall Dialog Message=<B>Are you sure you want to deinstall</B> <B>Netscape
-Communicator 4.03</B> ?
-
-<P>Deinstall Dialog Wait Message=<B>Parsing</B> <B>Netscape Communicator
-4.03&nbsp; deinstall log file</B> %s (<B>this will take several minutes)...</B>
-
-<P>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table2">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-<BR>&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeCosmo.html

@@ -1,62 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>Localize COSMO.INI</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-Localization notes for COSMO.INI</H4>
-<B>General Notes:</B>
-<UL>
-<LI>
-Only translate the strings which are shown in <B>bold</B> type face below.</LI>
-
-<LI>
-Update the product version number as appropriate.</LI>
-
-<LI>
-Modify the locale code according to the ISO 639 and ISO 3166 standards.
-(See the <A HREF="reference.html">Reference section</A> for details).</LI>
-</UL>
-<B>Specific Notes:</B>
-<BR>&nbsp;
-<BR>Installation String=<B>Installing Cosmo Player files...</B>
-
-<P>Configuration String=<B>Configuring Cosmo Player...</B>
-
-<P>File Copy String=<B>Copying Cosmo Player files...&nbsp;</B>
-
-<P>Description=<B>VRML 2.0 support&nbsp;</B>
-
-<P>[Registry Entries-Reg2]
-<BR>HKEY Value=<B>4.03 </B>(<B>en</B>)
-
-<P>[Registry Entries-Reg3]
-<BR>HKEY Key Path=Software\Netscape\Cosmo\<B>4.03</B> (<B>en</B>)
-
-<P>[Registry Entries-Reg4]
-<BR>HKEY Key Path=Software\Netscape\Cosmo\<B>4.03 </B>(<B>en</B>)\Main
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table2">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-<BR>&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeIsuser.html

@@ -1,32 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>Localize _ISUSER.DLL</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-Localization notes for _ISUSER.DLL</H4>
-All dialogs in this .DLL can be localized.
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table1">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeMmedia.html

@@ -1,45 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>Localize MMEDIA.INI</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-Localization notes for MMEDIA.INI</H4>
-<B>General Notes:</B>
-<UL>
-<LI>
-Only translate the strings which are shown in <B>bold</B> type face below.</LI>
-
-</UL>
-<B>Specific Notes:</B>
-
-<P>Installation String=<B>Installing Audio/Video Playback files...</B>
-
-<P>Configuration String=<B>Configuring Audio/Video Playback...</B>
-
-<P>File Copy String=<B>Copying Audio/Video Playback files...</B>
-
-<P>Description=<B>Support for multi-media web pages</B>
-<P>
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table2">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<P>
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeMplay.html

@@ -1,68 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Localizing MPLAY32.INI</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-Localization notes for MPLAY32.INI</H4>
-<B>General Notes:</B>
-<UL>
-<LI>
-Only translate the strings which are shown in <B>bold</B> type face below.</LI>
-
-<LI>
-Update the product version number as appropriate.</LI>
-
-<LI>
-Modify the locale code according to the ISO 639 and ISO 3166 standards.
-(See the <A HREF="reference.html">Reference section</A> for details).</LI>
-
-<LI>
-Change Netscape trademarks to your own product name(s).</LI>
-</UL>
-<B>Specific Notes:</B>
-
-<P>Installation String=<B>Installing Netscape Media Player files...</B>
-
-<P>Configuration String=<B>Configuring Netscape Media Player...</B>
-
-<P>File Copy String=<B>Copying Netscape Media Player files...</B>
-
-<P>Description=<B>Streaming audio support</B>
-
-<P>[Default Folder-Icon2]
-<BR>ProgramFolder=[Default Folder]\<B>Utilities</B>
-
-<P>[Registry Entries-Reg2]
-<BR>HKEY Value=<B>4.03 </B>(<B>en</B>)
-
-<P>[Registry Entries-Reg3]
-<BR>HKEY Key Path=Software\Netscape\Media Player\<B>4.03 </B>(<B>en</B>)
-
-<P>[Registry Entries-Reg4]
-<BR>HKEY Key Path=Software\Netscape\Media Player\<B>4.03 </B>(<B>en</B>)\Main
-
-<P>[Registry Entries-Reg5]
-<BR>HKEY Key Path=Software\Netscape\Media Player\<B>4.03</B> (<B>en</B>)\Main
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table2">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;<BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeNav40.html

@@ -1,154 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>Localize NAV40.INI</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-Localization notes for NAV40.INI</H4>
-<B>General Notes:</B>
-<UL>
-<LI>
-Do not exceed the length of English string if possible.</LI>
-
-<LI>
-Modify the locale code according to the ISO 639 and ISO 3166 standards.
-(See the <A HREF="reference.html">Reference section</A> for details).</LI>
-
-<LI>
-The "Utilities" folder name may be localized.</LI>
-
-<LI>
-"Item name" is the name that will appear under the associated icon; these
-may be localized.</LI>
-
-<LI>
-You may need to move the placement of "%s" variables in your translation.</LI>
-
-<LI>
-Change Netscape trademarks to your own product name(s).</LI>
-</UL>
-<B>Specific Notes:</B>
-
-<P>Installation String=<B>Installing Netscape Communicator 4.03 files...</B>
-
-<P>Configuration String=<B>Configuring Netscape Communicator 4.03...</B>
-
-<P>File Copy String=<B>Copying Netscape Communicator 4.03 files...</B>
-
-<P>Description=<B>Contains Collabra, Composer, Messenger, and Navigator</B>.
-
-<P>Warn Previous Version Message=<B>Setup has detected a previous installation
-of</B> %s. <B>If you installed plugins or helper applications with a previous
-installation, you will need to reinstall them to this version of</B> <B>Communicator.</B>
-
-<P>[Navigator 1]
-<BR>Message=<B>Setup has detected that an instance of Navigator is currently
-running. Please quit Navigator before running Setup.</B>
-
-<P>[Navigator 2]
-<BR>Message=<B>Setup has detected that an instance of Navigator is currently
-running. Please quit</B> <B>Navigator before running Setup.</B>
-
-<P>[Navigator 3]
-<BR>Message=<B>Setup has detected that an instance of Navigator is currently
-running. Please quit</B> <B>Navigator before running Setup.</B>
-
-<P>[NSMail Notifier]
-<BR>Message=<B>Installation cannot continue because the Mail Notification
-program is currently running. Use your right mouse button to click the
-Mail icon next to the task bar clock and select 'Exit' to disable Mail
-Notification, then run the installer again.</B>
-
-<P>[Navigator 4.05 32]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.05 (<B>en</B>)\Main
-
-<P>[Navigator 4.04 32]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.04 (<B>en</B>)\Main
-
-<P>[Navigator 4.03 32]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.03 (<B>en</B>)\Main
-
-<P>[Navigator 4.02 32]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.02 (<B>en</B>)\Main
-
-<P>[Navigator 4.01 32]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.01 (<B>en</B>)\Main
-
-<P>[Navigator 4.0 32]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.0 (<B>en</B>)\Main
-
-<P>[Navigator 4.0b6 32]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.0b6 (<B>en</B>)\Main
-
-<P>[Navigator 4.0b5 32]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.0b5 (<B>en</B>)\Main
-
-<P>[Navigator 4.0b4 32]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.0b4 (<B>en</B>)\Main
-
-<P>[Navigator 4.0b3 32]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.0b3 [<B>en</B>]\Main
-
-<P>[Default Folder-Icon11]
-<BR>ItemName=<B>User Profile Manager</B>
-
-<P>[Default Folder-Icon12]
-<BR>ProgramFolder=[Default Folder]\<B>Utilities</B>
-<BR>ItemName=<B>User Profile Manager</B>
-
-<P>[Default Folder-Icon13]
-<BR>ItemName=<B>Netscape Mail Notification</B>
-
-<P>[Default Folder-Icon14]
-<BR>ProgramFolder=[Default Folder]\<B>Utilities</B>
-<BR>ItemName=<B>Netscape Mail Notification</B>
-
-<P>[Registry Entries-R14]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.03 (<B>en</B>)
-
-<P>[Registry Entries-R15]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.03 (<B>en</B>)\Main
-
-<P>[Registry Entries-R16]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.03 (<B>en</B>)\Main
-
-<P>[Registry Entries-R17]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.03 (<B>en</B>)\Main
-
-<P>[Registry Entries-R18]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.03 (<B>en</B>)\Main
-
-<P>[Registry Entries-R19]
-<BR>HKEY Key Path=Software\Netscape\Netscape Navigator\4.03 (<B>en</B>)\Main
-
-<P>[Registry Entries-R37]
-<BR>HKEY Value=4.03 (<B>en</B>)
-
-<P>[Registry Entries-R38]
-<BR>HKEY Key Path=Software\Netscape\Netcaster\4.03 (<B>en</B>)\Main
-
-<P>[Registry Entries-R39]
-<BR>HKEY Key Path=Software\Netscape\Netcaster\4.03 (<B>en</B>)\Main
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table2">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER></CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeNetcast.html

@@ -1,49 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>Localize NETCAST.INI</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-Localization notes for NETCAST.INI</H4>
-
-<B>General Notes:</B>
-<UL>
-<LI>
-Only translate the strings which are shown in <B>bold</B> type face below.</LI>
-
-<LI>
-Change Netscape trademarks to your own product name(s).</LI>
-</UL>
-
-<B>Specific Notes:</B>
-<P>
-Installation String=<B>Installing Netscape Netcaster files...</B>
-<P>
-Configuration String=<B>Configuring Netscape Netcaster...</B>
-<P>
-File Copy String=<B>Copying Netscape Netcaster files...</B>
-
-<P>
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table2">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<P>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeNsconf.html

@@ -1,67 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>Localizing NSCONF.INI</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-Localization notes for NSCONF.INI</H4>
-<B>General Notes:</B>
-<UL>
-<LI>
-Only translate the strings which are shown in <B>bold</B> type face below.</LI>
-
-<LI>
-Update the product version number as appropriate.</LI>
-
-<LI>
-Modify the locale code according to the ISO 639 and ISO 3166 standards.
-(See the <A HREF="reference.html">Reference section</A> for details).</LI>
-
-<LI>
-Change Netscape trademarks to your own product name(s).</LI>
-</UL>
-<B>Specific Notes:</B>
-
-<P>Installation String=<B>Installing Netscape Conference files...</B>
-
-<P>Configuration String=<B>Configuring Netscape Conference...</B>
-
-<P>File Copy String=<B>Copying Netscape Conference files...</B>
-
-<P>Description=<B>Real-time collaboration and audio conferencing</B>
-
-<P>[Registry Entries-Reg17]
-<BR>HKEY Value=<B>4.03</B> (<B>en</B>)
-
-<P>[Registry Entries-Reg18]
-<BR>HKEY Key Path=Software\Netscape\Conference\<B>4.03 </B>(<B>en</B>)
-
-<P>[Registry Entries-Reg19]
-<BR>HKEY Key Path=Software\Netscape\Conference\<B>4.03</B> (<B>en</B>)\Main
-
-<P>[Registry Entries-Reg20]
-<BR>HKEY Key Path=Software\Netscape\Conference\<B>4.03</B> (<B>en</B>)\Main<BR>
-<BR>
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table2">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER></CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeRsutil.html

@@ -1,71 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>Localize RSUTIL.DLL</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-Localization notes for RSUTIL.DLL</H4>
-<B>STRINGTABLES</B><B></B>
-
-<P><B><FONT COLOR="#FF0000">Do not translate the following strings:</FONT></B>
-
-<P>STRING ID:
-<BR><I>1&nbsp;</I>
-<BR><I>17 18 19&nbsp;</I>
-<BR><I>20 21 22 23 24 25 26 27 28 29&nbsp;</I>
-<BR><I>30 31 32 33 34 35 36 37 38 39&nbsp;</I>
-<BR><I>40 41 42 43 44 45 46 47 48 49&nbsp;</I>
-<BR><I>50 51 52 53 54 55 56 57 58 59&nbsp;</I>
-<BR><I>60 61 62 63 64 65 66 67 68 69&nbsp;</I>
-<BR><I>70 71 72 73 74 75 76 77 78 79&nbsp;</I>
-<BR><I>80 81 82 83 85 86 88&nbsp;</I>
-<BR><I>90 91 92 95 97 98 99</I>
-<BR><I>100 101 102 103 104 105 106 107 108 109</I>
-<BR><I>110 111 112 113 114</I>
-<BR><I>122 123 126 127 129</I>
-<BR><I>132 133 134 135 136 137 138 139</I>
-<BR><I>140 145 149</I>
-<BR><I>151 153 154 155 156 157 158 159</I>
-<BR><I>162 163 164 165 166 167 169&nbsp;</I>
-<BR><I>170 171 172 173 174 175 176 177 178 179</I>
-<BR><I>180 181 182 183 184 185 187 188</I>
-<BR><I>190 192 193 194 195 196 197 198 199</I>
-<BR><I>200 201 202 203 204 205 206 207 208 209</I>
-<BR><I>210 211 212 213 214 215 216 217 218 219</I>
-<BR><I>220 221 222 226 227 228 229&nbsp;</I>
-<BR><I>230 232 233 234 235 236 237 238 239</I>
-<BR><I>240 241 242 243 244 245 246 247 248 249</I>
-<BR><I>250 251 252 253 254 255 256 257&nbsp;</I>
-<BR><I>260 261 263 264 265 266 267 269</I>
-<BR><I>270 271 272 273 274 275 276 277 278 279</I>
-<BR><I>280 281 282 283</I>
-<BR>&nbsp;
-<BR>
-<HR WIDTH="50%">
-<BR><B>ICONS</B>
-<BR>Replace any trademarked icons, as described in the universal localization
-program license agreement, with your own icons.
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table1">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeSetup.html

@@ -1,138 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>Localize SETUP.INI</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-Localization notes for SETUP.INI</H4>
-<B>General Notes:</B>
-<UL>
-<LI>
-Only translate the strings which are shown in bold type face below.</LI>
-
-<LI>
-The "StartCopy Dialog Message" should be less than 256 bytes long.</LI>
-
-<LI>
-For the "Multiple Components" section, both the key and the value may be
-localized (optional).</LI>
-
-<LI>
-If the key "Multimedia Support" is localized then next section name should
-be identical to the localized key.</LI>
-
-<LI>
-Change Netscape trademarks to your own product name(s).</LI>
-
-<LI>
-Update the version number as appropriate.</LI>
-
-<LI>
-Modify the locale code according to the ISO 639 and ISO 3166 standards.
-(See the <A HREF="reference.html">Reference section</A> for details).</LI>
-</UL>
-<B>Specific Notes:</B>
-
-<P>Product Setup Title1= <B>Setup</B>
-
-<P>Product Version=<B>4.03 </B>(<B>en</B>)
-
-<P>Deinstall Version=<B>4.03 </B>(<B>en</B>)
-
-<P>License Dialog Title=<B>Software License Agreement</B>
-
-<P>License Dialog Message=<B>Please read the following license agreement.
-Use the scroll bar to view the rest of this agreement.</B>
-
-<P>License Dialog Question=<B>Do you accept all the terms of the preceding
-license agreement? If so, click on the Yes button. If you select No, Setup
-will close.</B>
-
-<P>License Icon Description=<B>License Agreement</B>
-
-<P>Welcome Dialog Title=<B>Netscape Communicator 4.03 Setup</B>
-
-<P>Welcome Dialog Message=<B>Welcome to Netscape Communicator 4.03 Setup</B>.
-
-<P>SetupType Dialog Title=<B>Setup Type</B>
-
-<P>SetupType Dialog Message=<B>Select the type of setup you prefer.</B>
-
-<P>Insufficient Space Dialog Title=<B>Insufficient Space</B>
-
-<P>Insufficient Space Dialog Message=<B>The path below contains insufficient
-space.</B>
-
-<P>Path Dialog Title=<B>Choose Destination Location</B>
-
-<P>Path Dialog Message=<B>Please enter the location where you would like
-to install </B>Netscape Communicator 4.03
-<BR><B>components. You may type a new directory name or click the Browse
-button to find a new location.</B>
-
-<P>Options Dialog Title=<B>Netscape Communicator 4.03 Options</B>
-
-<P>Options Dialog Message=<B>Check the components you would like to install.</B>
-
-<P>Associations Dialog Title=<B>Setup Associations</B>
-
-<P>Associations Dialog Message=<B>Check the extensions you would like Communicator
-to set up. These extensions will be associated with Communicator components.</B>
-
-<P>Select Folder Dialog Title=<B>Select Program Folder</B>
-
-<P>StartCopy Dialog Title=<B>Start Copying Files</B>
-
-<P>StartCopy Dialog Message=<B>Setup has enough information to start copying
-the program files. If you want to review or change settings, click Back.
-If you are satisfied with the current settings, click Install to begin
-copying files.</B>
-
-<P>Readme Dialog Prompt=<B>Would you like to view the README file now?</B>
-
-<P>Finish Dialog Prompt=<B>Setup is complete. You may run Netscape Communicator
-4.03 by double-clicking on one of the icons in the folder.</B>
-
-<P>Reboot Dialog Title=<B>Restarting Windows</B>
-
-<P>Reboot Dialog Message=<B>Setup has finished copying files to your computer.
-Before you can use the program, you must restart Windows or your computer.</B>
-
-<P>Exit Dialog Message=<B>Are you sure you want to exit setup?</B>
-
-<P>Error Resource Message1=<B>Could not load Resource: </B>%s
-<BR>Error Resource Message2=<B>Attempted to fix the problem. Please restart
-the setup application.</B>
-<BR>Error Resource Message3=<B>Could not get module handle of rsutil.dll.
-System memory could be corrupted. Please reboot and try again.</B>
-
-<P>[Multiple Components]
-<BR><B>Multimedia Support</B>=<B>Extension modules for Netscape Communicator
-4.03</B>
-
-<P>[<B>Multimedia Support</B>]
-<BR>Default Path=
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table1">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localizeURL.html

@@ -1,55 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Localizing URLs</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="localizeURLs"></A>Localizing URLs</H3>
-Many resources of all types in the Communicator contain Internet addresses
-in the form of URLs (Universal Resource Locators). Most of these point
-to locations within the Netscape domain; as part of the Unlimited Localization
-Program, you can leave these as they are, or you may change them as you
-desire.
-<H3>
-Internal URLs</H3>
-There are a number of internal URLs that <FONT COLOR="#FF0000">should not
-be changed</FONT>.&nbsp; These are the strings that look like <B>about:[some
-value]</B>.&nbsp; These point to internally contained resources, such as
-the main About Communicator page.&nbsp; If you localize these strings you
-will not be able to load these pages.&nbsp; The main examples you might
-find are:
-<UL>
-<LI>
-about:</LI>
-
-<LI>
-about:plugins</LI>
-
-<LI>
-about:fonts</LI>
-</UL>
-For more examples and information on these internal URLs go <A HREF="http://help.netscape.com/kb/client/970513-4.html">here</A>.
-<BR>&nbsp;
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="usingKit.html#localizeURLs">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;<BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/localize_these_files.html

@@ -1,125 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Localize these Files</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="localize_these_files"></A>Localize These Files</H3>
-This section tells you exactly what files need to be localized. The following
-tables contain two columns:
-<UL>
-<LI>
-The file to be localized column gives the specific file name. The path
-name <I>temp</I> refers to wherever you have copied the uncompressed installer
-files in Step 2 of the <A HREF="usingKit.html#l10nchecklist">Localization
-Checklist</A>. If the file or resource name is a hypertext link, further
-information can be found by following that link.</LI>
-
-<LI>
-The purpose column describes the basic purpose of this file.</LI>
-</UL>
-<A NAME="table1"></A><FONT SIZE=-1>Table 1. Binary files to be localized</FONT>
-<TABLE BORDER >
-<TR>
-<TD><B>File to be localized&nbsp;</B></TD>
-
-<TD><B>Purpose</B></TD>
-</TR>
-
-<TR>
-<TD><TT><A HREF="localizeRsutil.html">rsutil.dll</A></TT></TD>
-
-<TD>Installer STRINGTABLE and ICON resources.&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><TT><A HREF="localizeIsuser.html">_isuser.dll</A></TT></TD>
-
-<TD>Installer DIALOG resources.</TD>
-</TR>
-</TABLE>
-
-<P>
-<A NAME="table2"></A><FONT SIZE=-1>Table 2. .INI files to be localized</FONT>
-<TABLE BORDER >
-<TR>
-<TD><B>File to be localized</B></TD>
-
-<TD><B>Purpose</B></TD>
-</TR>
-
-<TR>
-<TD><A HREF="localizeAim.html">aim.ini</A></TD>
-
-<TD>AOL Instant Messgenger initialization file.*</TD>
-</TR>
-
-<TR>
-<TD><A HREF="localizeCD.html">cd.ini</A></TD>
-
-<TD>Deinstaller initialization file.</TD>
-</TR>
-
-<TR>
-<TD><A HREF="localizeCosmo.html">cosmo.ini</A></TD>
-
-<TD>Cosmo player initialization file.*</TD>
-</TR>
-
-<TR>
-<TD><A HREF="localizeMmedia.html">mmedia.ini</A></TD>
-
-<TD>Multimedia initialization file.*</TD>
-</TR>
-
-<TR>
-<TD><A HREF="localizeMplay.html">mplay32.ini</A></TD>
-
-<TD>Media Player initialization file.*</TD>
-</TR>
-
-<TR>
-<TD><A HREF="localizeNav40.html">nav40.ini</A></TD>
-
-<TD>Main product initialization file.</TD>
-</TR>
-
-<TR>
-<TD><A HREF="localizeNetcast.html">netcast.ini</A></TD>
-
-<TD>Netcaster initialization file.</TD>
-</TR>
-
-<TR>
-<TD><A HREF="localizeNsconf.html">nsconf.ini</A></TD>
-
-<TD>Netscape Conference initialization file.*</TD>
-</TR>
-
-<TR>
-<TD><A HREF="localizeSetup.html">setup.ini</A></TD>
-
-<TD>Main setup initialization file.</TD>
-</TR>
-</TABLE>
-<P>
-* These files come with the Complete installer version.
-<P>
-<CENTER><TABLE COLS=1 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<P>
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/nomenclature.html

@@ -1,109 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Conventions</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="nomenclature"></A>Nomenclature and Typographical Conventions</H3>
-<B>Typographical Conventions</B>
-<BR>Words in <I>italics</I> typeface represent a variable term or phrase,
-meant to be replaced by another value at "runtime."&nbsp; Example:
-<UL><I>locale</I> -- replaced by a 2- or 4 letter locale code; e.g. zhtw</UL>
-Words in <B>bold</B> typeface, using a proportional font, represent a literal
-value in a string that might also contain a variable word or phrase. Example:
-<UL><B>4.03 [</B><I>locale</I><B>]</B> -- 4.03 [ ] are literal values,
-while <I>locale</I> is a variable.
-<UL>&nbsp;</UL>
-</UL>
-Words in a <TT>fixed width font</TT> represent file or directory names,
-or DOS or Windows commands to be typed as they appear.&nbsp; Sometimes,
-part or all of the path will be in <B><TT>bold</TT></B>, for emphasis.
-Examples:
-<UL>Change to the <B><TT><I>kitRoot</I>\l10nkits\client\windows\tools</TT></B><TT>
-</TT>directory
-<BR>Execute <B><TT>RTRNKIT</TT></B></UL>
-<B>Nomenclature</B>
-<BR>Throughout this document, certain terms and phrases will be used repeatedly:
-
-<P><FONT SIZE=-1>Table 1. Nomenclature and Typographical Conventions</FONT>
-<TABLE BORDER >
-<TR>
-<TD><B><TT>kitRoot</TT> </B>directory&nbsp;</TD>
-
-<TD>indicates the starting or topmost directory of the Windows Front End
-Localization Kit.</TD>
-</TR>
-
-<TR>
-<TD><I>platform</I></TD>
-
-<TD>either 16 or 32 bit, depending on the version you are working on.</TD>
-</TR>
-
-<TR>
-<TD><I>locale</I></TD>
-
-<TD>in general, this refers to the language into which you are localizing
-the product. The list of valid locale names is defined in the <A HREF="isocodes.htm">ISO
-Language and Country Codes Table</A>.</TD>
-</TR>
-
-<TR>
-<TD>localization database</TD>
-
-<TD>a database generated by a leveraging tool from a set of matched binary
-resource files.&nbsp;</TD>
-</TR>
-
-<TR>
-<TD>localization notes</TD>
-
-<TD>any special instructions, including the "translate/don't translate"
-flag, associated with a given resource.&nbsp; Localization notes are contained
-in the localization database for each resource module.</TD>
-</TR>
-
-<TR>
-<TD><I>leverage</I></TD>
-
-<TD>The process of merging previous localized versions of a file into a
-current version.&nbsp;</TD>
-</TR>
-
-<TR>
-<TD>forbidden resource</TD>
-
-<TD>A resource that cannot be changed from the original value without (negatively)
-impacting the functionality of the product. These are identified in the
-localization databases.</TD>
-</TR>
-</TABLE>
-&nbsp;
-<BR>&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="kitStruct.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="gettingStarted.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/projectOverview.html

@@ -1,57 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Project Overview</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-<A NAME="overviews"></A>1. Project Overview</H2>
-
-<CENTER><B><FONT COLOR="#009900">Welcome to the Communicator/Navigator
-Installer Localization Kit!</FONT></B></CENTER>
-
-
-<P>Under the universal localization program, you are free to create an
-installer for a localized Communicator, Navigator or Mozilla derivative
-product in any way you choose. This localization kit will assist you in
-creating a your installer for the 32-bit Windows platform. As long as you
-follow the terms of the universal localization program license agreement,
-you are free to do what you want with the resulting localized product and
-installer.
-
-<P>The Netscape Communicator and Netscape Navigator 4.x installation programs
-were created with InstallShield<SUP><FONT SIZE=-1>&reg;</FONT></SUP> version
-3.&nbsp; Because this is the proprietary product of InstallShield Corporation,
-Netscape cannot redistribute the complete source for these installers.&nbsp;
-You may, however, modify an existing Communicator or Navigator installer,
-or if you choose, you may build your own installer "from scratch".
-
-<P><B>Note</B>: because of the U.S. Government's restrictions on the export
-of strong cryptography, <B>you may only distribute the "export" version</B>
-of the Netscape binaries.&nbsp; Please keep this in mind as you work with
-the localization kit instructions.
-<BR>&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="splash.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="kitOverview.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-&nbsp;
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/reference.html

@@ -1,54 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Reference</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-<A NAME="reference"></A>Reference</H2>
-This section summarizes the references used throughout this document.&nbsp;
-In addition, other miscellaneous references may be found here.
-
-<P><FONT SIZE=-1>Table 5. Reference Links</FONT>
-<TABLE BORDER COLS=3 WIDTH="100%" >
-<TR>
-<TD><A HREF="isocodes.htm">Locale Table (local)</A></TD>
-
-<TD><A HREF="http://www.indigo.ie/egt/standards/iso639/iso639-en.html">Locale
-Table (remote)</A></TD>
-
-<TD><A HREF="registrySettings.html">Windows Registry Settings Reference</A></TD>
-</TR>
-
-<TR>
-<TD><A HREF="http://home.netscape.com/menu/intl/">Communicator International
-Features</A></TD>
-
-<TD><A HREF="http://help.netscape.com/kb/client/970513-4.html"></A></TD>
-
-<TD><FONT COLOR="#009900"><A HREF="charsets.htm"></A></FONT></TD>
-</TR>
-</TABLE>
-<A HREF="allxpstr.h"></A>
-
-<P>&nbsp;
-<CENTER><TABLE COLS=1 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER></CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/registrySettings.html

@@ -1,612 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Windows Registry Settings</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H1>
-Windows Registry Settings</H1>
-This document is provided as a reference to the Windows registry settings
-implemented by Communicator and Navigator.&nbsp; You may use this as a
-guide to the registry settings you must implement if you create your own
-installation program (as opposed to localizing an existing Netscape installer).
-
-<P>Note that in the Netscape installers, these settings are implemented
-only within .INI files.&nbsp; This simplifies modifying and localizing
-the installer. It is recommended that your installer do the same.
-
-<P>You may observe the registry changes made by any product with tools
-such as <A HREF="http://www.ntinternals.com/regmon.htm">Regmon.</A> This
-may be a useful addition to your toolset.
-
-<P>These notes are applicable to Netscape Communicator version 4.03.
-<BR>&nbsp;
-<TABLE BORDER COLS=1 WIDTH="100%" >
-<TR>
-<TD><B>MPLAY32.INI</B>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Media Player&nbsp;
-<BR>Name : CurrentVersion&nbsp;
-<BR>Value: 4.03 (en)&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Media Player\4.03 (en)&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Media Player\4.03 (en)\Main&nbsp;
-<BR>Name : Install Directory&nbsp;
-<BR>Value: [Default Path]\MPlayer&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : Program Folder&nbsp;
-<BR>Value: [Program Folder]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\.LAM&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: LAMDocument&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\LAMDocument\shell\open\command&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [WINSYSDIR]\mplay32.exe %1&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : (Default)&nbsp;
-<BR>Value: [WINDIR]\mplayer.exe %1&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\LAMDocument\DefaultIcon&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\MPlayer\npcfg32.exe ,0&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\MCI32&nbsp;
-<BR>Name : LiveAudioFile&nbsp;
-<BR>Value: mcilma32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\MCI&nbsp;
-<BR>Name : LiveAudioFile&nbsp;
-<BR>Value: mcilma.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\MCI32&nbsp;
-<BR>Name : LiveAudioMetafile&nbsp;
-<BR>Value: mcilau32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\drivers.desc&nbsp;
-<BR>Name : mcilau32.dll&nbsp;
-<BR>Value: (MCI) Netscape Media Player&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\MCI&nbsp;
-<BR>Name : LiveAudioMetafile&nbsp;
-<BR>Value: mcilau.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\MCI
-Extensions&nbsp;
-<BR>Name : LAM&nbsp;
-<BR>Value: LiveAudioMetafile&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : LMA&nbsp;
-<BR>Value: LiveAudioFile&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : LA&nbsp;
-<BR>Value: LiveAudioFile&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\drivers.desc&nbsp;
-<BR>Name : mcilma32.dll&nbsp;
-<BR>Value: (MCI) Netscape Packetized Audio&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Drivers32&nbsp;
-<BR>Name : MSACM.NSPAC&nbsp;
-<BR>Value: NSPAC32.ACM&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\drivers.desc&nbsp;
-<BR>Name : NSPAC32.ACM&nbsp;
-<BR>Value: elemedia(TM) AX24000P Music Codec&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Drivers32&nbsp;
-<BR>Name : MSACM.voxacm118&nbsp;
-<BR>Value: vdk32118.acm&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\drivers.desc&nbsp;
-<BR>Name : vdk32118.acm&nbsp;
-<BR>Value: Voxware 32bit Codec&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Drivers32&nbsp;
-<BR>Name : MSACM.NSX83&nbsp;
-<BR>Value: NSX83P32.ACM&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\drivers.desc&nbsp;
-<BR>Name : NSX83P32.ACM&nbsp;
-<BR>Value: elemedia(TM) SX8300 Speech Codec&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Drivers32&nbsp;
-<BR>Name : MSACM.NSMLAW&nbsp;
-<BR>Value: NSMLAW32.DLL&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\drivers.desc&nbsp;
-<BR>Name : NSMLAW32.DLL&nbsp;
-<BR>Value: Netscape G.711 Decoder&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>
-<HR WIDTH="100%">
-<BR><B>NAV40.INI</B>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App
-Paths\Netscape.exe&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\Netscape.exe&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : Path&nbsp;
-<BR>Value: [Default Path]\Program&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\CLSID\{7865A9A1-33A8-11d0-BED9-00A02468FAB6}\InprocServer32&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\brpref32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\CLSID\{543EC0D0-6AB7-11d0-BF56-00A02468FAB6}\InprocServer32&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\brpref32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\CLSID\{543EC0D1-6AB7-11d0-BF56-00A02468FAB6}\InprocServer32&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\brpref32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\CLSID\{2D0A7D70-748C-11d0-9705-00805F8AA8B8}\InprocServer32&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\edpref32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\CLSID\{E8D6B4F0-8B58-11d0-9B63-00805F8ADDDE}\InprocServer32&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\mnpref32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\CLSID\{DDF4AB60-8B84-11d0-9B63-00805F8ADDDE}\InprocServer32&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\mnpref32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\CLSID\{CC3E2871-43CA-11d0-B6D8-00805F8ADDDE}\InprocServer32&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\mnpref32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\CLSID\{CC3E2872-43CA-11d0-B6D8-00805F8ADDDE}\InprocServer32&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\mnpref32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Netscape Navigator&nbsp;
-<BR>Name : CurrentVersion&nbsp;
-<BR>Value: 4.03 (en)&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Netscape Navigator\Users&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Netscape Navigator\4.03
-(en)&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Netscape Navigator\4.03
-(en)\Main&nbsp;
-<BR>Name : Install Directory&nbsp;
-<BR>Value: [Default Path]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : Java Directory&nbsp;
-<BR>Value: [Default Path]\Program\Java&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : NetHelp Directory&nbsp;
-<BR>Value: [Default Path]\Program\NetHelp&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : Plugins Directory&nbsp;
-<BR>Value: [Default Path]\Program\Plugins&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : Program Folder&nbsp;
-<BR>Value: [Program Folder]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CURRENT_USER\Software\Netscape&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CURRENT_USER\Software\Netscape\Netscape Navigator&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CURRENT_USER\Software\Netscape\Netscape Navigator\Main&nbsp;
-<BR>Name : Install Directory&nbsp;
-<BR>Value: [Default Path]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\CLSID&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: {61D8DE20-CA9A-11CE-9EA5-0080C82BE3B6}&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\Insertable&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\protocol\StdFileEditing\server&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\Netscape.exe&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\protocol\StdFileEditing\verb\0&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: &amp;Edit&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\open\command&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\Netscape.exe "%1"&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\print\command&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\Netscape.exe /print("%1")&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\print\ddeexec&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [print("%1")]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\PrintTo\command&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\Netscape.exe /printto("%1","%2","%3","%4")&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\PrintTo\ddeexec&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [("%1","%2","%3","%4")]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\open\ddeexec&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: "%1"&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\open\ddeexec\Application&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: NSShell&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\open\ddeexec\Topic&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: WWW_OpenURL&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\Edit\command&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\Netscape.exe -edit "%1"&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\Edit\ddeexec&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [edit("%1")]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Netcaster&nbsp;
-<BR>Name : CurrentVersion&nbsp;
-<BR>Value: 4.03 (en)&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Netcaster\4.03 (en)\Main&nbsp;
-<BR>Name : Install Directory&nbsp;
-<BR>Value: [Shell Path]\Netcast&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : Program Folder&nbsp;
-<BR>Value: [Program Folder]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\CLSID\{C98D0190-7D81-11d0-BF8D-00A02468FAB6}\InprocServer32&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\brpref32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\CLSID\{37B601C0-8AC8-11d0-83AF-00805F8A274D}\InprocServer32&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\brpref32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\CLSID\{913A4A20-8EBF-11d0-BFAB-00A02468FAB6}\InprocServer32&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\Program\brpref32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\print\ddeexec\Application&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: NSShell&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\PrintTo\ddeexec\Application&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: NSShell&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup\shell\Edit\ddeexec\Application&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: NSShell&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\NetscapeMarkup&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: Hypertext Markup Language&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\telnet&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: URL:Telnet Protocol&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\telnet\shell\open\command&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: telnet %1&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>
-<HR WIDTH="100%">
-<BR><B>NETCAST.INI</B>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Netcaster&nbsp;
-<BR>Name : CurrentVersion&nbsp;
-<BR>Value: 1.0 (en)&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Netcaster\1.0 (en)&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Netcaster\1.0 (en)\Main&nbsp;
-<BR>Name : Install Directory&nbsp;
-<BR>Value: [Default Path]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : Program Folder&nbsp;
-<BR>Value: [Program Folder]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>
-<HR WIDTH="100%">
-<BR><B>NSCONF.INI</B>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Conference&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Conference\CurrentVersion&nbsp;
-<BR>Name : Description&nbsp;
-<BR>Value: Conference&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : InstallDate&nbsp;
-<BR>Value: [TIME]&nbsp;
-<BR>Type : REGDB_NUMBER&nbsp;
-
-<P>Name : Installed&nbsp;
-<BR>Value: 1&nbsp;
-<BR>Type : REGDB_NUMBER&nbsp;
-
-<P>Name : PathName&nbsp;
-<BR>Value: [Default Path]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : SoftwareType&nbsp;
-<BR>Value: application&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : VersionBuild&nbsp;
-<BR>Value: 1213&nbsp;
-<BR>Type : REGDB_NUMBER&nbsp;
-
-<P>Name : VersionMajor&nbsp;
-<BR>Value: 1&nbsp;
-<BR>Type : REGDB_NUMBER&nbsp;
-
-<P>Name : VersionMinor&nbsp;
-<BR>Value: 0&nbsp;
-<BR>Type : REGDB_NUMBER&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Drivers32&nbsp;
-<BR>Name : MSACM.VOXACM118&nbsp;
-<BR>Value: vdk32118.acm&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : MSACM.NSX83&nbsp;
-<BR>Value: nsx83p32.acm&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : MSACM.NSX723&nbsp;
-<BR>Value: sx5363s.acm&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : MSACM.NSMLAW&nbsp;
-<BR>Value: nsmlaw32.dll&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CURRENT_USER\Software\Netscape&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_CLASSES_ROOT\nscfile\shell\open\command&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value: [Default Path]\NSConf32.exe -f "%1"&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Conference&nbsp;
-<BR>Name : CurrentVersion&nbsp;
-<BR>Value: 4.03 (en)&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Conference\4.03 (en)&nbsp;
-<BR>Name : (Default)&nbsp;
-<BR>Value:&nbsp;
-<BR>Type :&nbsp;
-<BR>&nbsp;
-
-<P>Key&nbsp; : HKEY_LOCAL_MACHINE\Software\Netscape\Conference\4.03 (en)\Main&nbsp;
-<BR>Name : Install Directory&nbsp;
-<BR>Value: [Default Path]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-
-<P>Name : Program Folder&nbsp;
-<BR>Value: [Program Folder]&nbsp;
-<BR>Type : REGDB_STRING&nbsp;
-<BR>&nbsp;</TD>
-</TR>
-</TABLE>
-&nbsp;
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="kitOverview.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/reportingBugs.html

@@ -1,53 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Reporting Bugs</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="reporting_bugs"></A>Reporting Bugs</H3>
-Any bugs in the localization kits you find should be reported to <A HREF="http://www.mozilla.org">mozilla.org</A>
-as soon as possible. When you report a bug, try to be as specific as you
-can about the exact steps needed to reproduce the bug.&nbsp; Provide a
-complete description of the problem versus the expected results.&nbsp;
-You should let us know if the problem is 100% reproducible (it happens
-every time), or if it is intermittant.&nbsp; If you think that your operating
-environment may play some factor, let us know the details of that.&nbsp;
-Finally, before reporting any bug, you should make sure that the problem
-doesn't also happen in the US English product (if it does, we still want
-to know, but it may not be possible to fix it through the localization
-kits or tools as they are now).
-
-<P>To report a bug, post a message to the following mozilla.org newsgroup:
-<BR>&nbsp;
-<CENTER><A HREF="news://news.mozilla.org/netscape.public.mozilla.general">news://news.mozilla.org/netscape.public.mozilla.general</A></CENTER>
-
-
-<P>Be sure to include the information described above.
-<BR>&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="testKit.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="returnKit.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/returnKit.html

@@ -1,54 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Returning the Kit</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-<A NAME="returnkit"></A>5. Publishing the Finished Kit</H2>
-Once you are satisfied with the quality of your localization efforts, you
-are required by the terms of the universal localization program license
-agreement to make your localized product publicly available. The exact
-details of how you do this is up to you, the most commonly acceptable method
-is to post your localized product to a publicly accessible ftp site.
-
-<P>You should post just the localized versions of the files mentioned in
-the Localize These Files section of this document. For ease of transfer,
-you may create a compressed archive in the .ZIP file format that contains
-the localized files. Create one .ZIP file for each language/platform you
-do. If you are publishing more than one language or platform, you may combine
-multiple .ZIP files into one master .ZIP file if this makes your life easier.
-
-<P>If your localized product includes your own trademarks, you should identify
-these and any restrictions you are placing on their use. You must also
-include a copy of the End User License Agreement (EULA), as well as a notice
-stating that Netscape Communications is not required to support your product,
-and that you are the Licensor referred to in the EULA. Please refer to
-the Universal Localization Agreement for the exact legal requirements.
-
-<P>Once your localized product is publicly available, you may inform the
-world in any manner you choose, but we encourage you to also post the download
-location to the mozilla.org Announcements newsgroup (netscape.public.mozilla.announce).
-<CENTER>&nbsp;<BR>
-<FONT COLOR="#008000"><FONT SIZE=+2>Congratulations! You are done!</FONT></FONT></CENTER>
-&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="testKit.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/splash.html

@@ -1,47 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Title Page</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<CENTER>
-<H1>
-NETSCAPE COMMUNICATOR</H1></CENTER>
-
-<CENTER><IMG SRC="SPLASH.JPG" NOSAVE HEIGHT=261 WIDTH=390></CENTER>
-
-<CENTER>
-<H1>
-Localization Kit</H1></CENTER>
-
-<CENTER>
-<H3>
-for Microsoft<SUP><FONT SIZE=+0>&reg;</FONT></SUP> Windows (32-bit version)</H3></CENTER>
-
-<CENTER>
-<H3>
-Revision 1.1</H3></CENTER>
-
-<CENTER>Copyright &copy; 1994-1998 Netscape&reg; Communications Corporation,
-All rights reserved.</CENTER>
-&nbsp;
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="projectOverview.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/testKit.html

@@ -1,150 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Testing the Localized Resources</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-<A NAME="testkit"></A>4. Ensuring Quality</H2>
-The quality of your localized version will have a large impact on its acceptance
-in the marketplace.&nbsp; You can greatly enhance your chances of producing
-a quality product by using experienced and skilled localizers, and by performing
-post-translation testing.
-
-<P>When performing the actual translation, you should be sensitive to a
-number of issues:
-<UL>
-<LI>
-Completeness: you should aim for as thorough a translation as possible.&nbsp;
-Try not to leave portions of the product untranslated. However, be aware
-that some terms may best be left in English, depending on local conventions.</LI>
-
-<LI>
-Suitability: all translations should be suitable and appropriate for product,
-the language, the market and the customers you intend to reach.&nbsp; This
-includes using the proper technical terminology for a give platform or
-computer operation, as well as using language that is readily understood
-by the average user of the product in a given language.&nbsp; You should,
-where possible, try to use terminology which is similar to other products
-available on the same platform (without violating copyrights or trademarks,
-of course).</LI>
-
-<LI>
-Accuracy: you should be sure your translation conveys the same meaning
-and intention as the original English.</LI>
-
-<LI>
-Grammar and spelling: you should be sure your translation is grammatically
-accurate and free from spelling errors.</LI>
-</UL>
-Keep in mind that engineers do not necessarily make the best localizers!
-
-<P>Once localization is complete, there are two basic types of post-translation
-testing that should be done:
-<BR>&nbsp;
-<TABLE BORDER WIDTH="100%" >
-<TR>
-<TD>Linguistic Review</TD>
-
-<TD>Checking all translations for accuracy and appropriateness in the actual
-context in which they appear.</TD>
-</TR>
-
-<TR>
-<TD>Functional Testing</TD>
-
-<TD>Ensuring the product still functions as designed (or at least as well
-as the US English product).</TD>
-</TR>
-</TABLE>
-&nbsp;
-<BR>For the linguistic review, you should have an independent reviewer
-(i.e. not the person who implemented the translations) check every string
-for the items listed above.&nbsp; In some cases, it may be enough to review
-the running product itself; however, it is also valuable to print out your
-translations and review them externally from the product.
-
-<P>For the functional testing, your best resource are the directions contained
-in the localization notes and this document. You should review the completed
-product's localization notes with this document in hand, double checking
-that you have followed all the instructions contained here.
-
-<P>Consider the following general guidelines when testing:
-<UL>
-<LI>
-It is helpful to have a second copy of the product running with the English
-version so you can compare them side by side (a second computer might be
-helpful or required for this).</LI>
-
-<LI>
-Walk through every menu in each module you have localized looking for translation
-accuracy, pick letter conflicts and other problems.</LI>
-
-<LI>
-Bring up as many dialogs as you can, looking for translation accuracy,
-pick letter conflicts, truncated strings and functionality issues.</LI>
-
-<LI>
-Exercise the installer in as many ways as possible:</LI>
-
-<UL>
-<LI>
-Select every installer option</LI>
-
-<LI>
-Be sure to test the deinstaller</LI>
-
-<LI>
-Look at the icons and folder names created</LI>
-
-<LI>
-Use accented or multibyte file and directory names</LI>
-
-<LI>
-Install to non-existant and read-only directories</LI>
-
-<LI>
-Install to drives with insufficient disk space</LI>
-
-<LI>
-etc.</LI>
-</UL>
-
-<LI>
-If functional problems are found, you should compare the same steps you
-took in the localized product to the English product: if the two products
-fail in the same way, it is a "core" bug, which can only be fixed by changing
-the core product's executable. If the localized product fails while the
-English product does not, then it is probably a translation-related bug;
-these can be fixed by altering the way you localize the product (perhaps
-by not translating a particular item, or by translating it differently).</LI>
-</UL>
-The following section tells you how to report bugs in the localization
-kit itself, or in the core product.
-<BR>&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="usingKit.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="reportingBugs.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/toc.html

@@ -1,106 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Table of Contents</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-Table of Contents</H2>
-
-<TABLE>
-<TR>
-<TD><FONT SIZE=+1>i. <A HREF="splash.html">Title Page</A></FONT>&nbsp;
-<BR>&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>1. <A HREF="projectOverview.html">Project Overview</A></FONT>&nbsp;
-<UL>
-<LI>
-<A HREF="kitOverview.html">Kit Overview</A></LI>
-
-<LI>
-<A HREF="kitStruct.html">Structure and Organization</A></LI>
-
-<LI>
-<A HREF="nomenclature.html">Nomenclature and Typographical Conventions<BR>
-</A>&nbsp;&nbsp;</LI>
-</UL>
-</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>2. <A HREF="gettingStarted.html">Getting Started</A></FONT>&nbsp;
-<UL>
-<LI>
-<A HREF="gettingStarted.html#sysreqs">System Requirements</A></LI>
-
-<LI>
-<A HREF="gettingStarted.html#install">Installing the Kit</A></LI>
-
-<LI>
-<A HREF="gettingStarted.html#configtool">Configuring Your Tools</A></LI>
-</UL>
-&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>3. <A HREF="usingKit.html">Using the Kit</A></FONT>&nbsp;
-<UL>
-<LI>
-<A HREF="usingKit.html#locdbf">Understanding the Localization Notes</A></LI>
-
-<LI>
-<A HREF="usingKit.html#l10nchecklist">Localization Checklist</A></LI>
-
-<LI>
-<A HREF="localize_these_files.html">Localize These Files</A></LI>
-
-<LI>
-<A HREF="usingKit.html#branding">Product Branding Issues</A></LI>
-
-<LI>
-<A HREF="usingKit.html#howtol10n">How to Localize Different Resource Types</A></LI>
-
-<LI>
-<A HREF="localizeURL.html">Localizing URLs</A></LI>
-
-<LI>
-<A HREF="usingKit.html#localize_stringtable">Localizing STRING TABLES</A></LI>
-
-<LI>
-<A HREF="usingKit.html#localize_dialogs">Localizing DIALOGS</A></LI>
-
-<LI>
-<A HREF="usingKit.html#localize_text">Localizing .INI Files</A></LI>
-</UL>
-&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>4. <A HREF="testKit.html">Ensuring Quality</A></FONT>&nbsp;
-<UL>
-<LI>
-<A HREF="testKit.html#testkit">Test Considerations</A></LI>
-
-<LI>
-<A HREF="reportingBugs.html">Reporting Bugs</A></LI>
-</UL>
-&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>5. <A HREF="returnKit.html">Publishing the Finished Kit</A></FONT>&nbsp;
-<BR>&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>6. <A HREF="reference.html">References</A></FONT>&nbsp;</TD>
-</TR>
-</TABLE>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/installer/usingKit.html

@@ -1,323 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Using the Kit</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-&nbsp;
-<TABLE COLS=1 WIDTH="100%" >
-<TR>
-<TD>
-<CENTER><B><FONT COLOR="#FF0000">WARNING! Protect yourself from data loss
-by making regular backups of your work.</FONT></B></CENTER>
-</TD>
-</TR>
-</TABLE>
-
-<H2>
-<A NAME="usekit"></A>3. Using the Kit</H2>
-Once your copy of the Windows Installer Localization Kit is correctly installed,
-you may begin your localization work by following the instructions in the
-remainder of this document. The next section discusses the contents of
-the localization notes provided with this kit. It is important that you
-work properly with the instructions contained in these files or the localized
-product you create may not function.
-<H3>
-<A NAME="locdbf"></A>Understanding the Localization Notes</H3>
-Each localized module to be installed has an associated initialization
-(.INI) file. The localization notes for these files, and for the localizable
-dynamic link libraries used by the InstallShield installer, are provided
-as HTML documentation. (There are no localization databases in this kit).
-Additionally, a section detailing the required Windows registry settings
-is also provided in HTML format.
-
-<P>The next section presents the basic localization process as a checklist.
-<CENTER>
-<HR WIDTH="50%"></CENTER>
-
-<H3>
-<A NAME="l10nchecklist"></A>Localization Checklist</H3>
-This checklist applies to the "<A HREF="kitOverview.html#method1">modifying
-an existing Communicator installer</A>" method. If you are <A HREF="kitOverview.html#method2">creating
-your own installer</A>, you will need to adapt this checklist accordingly.
-A reference is provided to help you implement the correct <A HREF="registrySettings.html">Windows
-registry settings</A>.
-
-<P><B>1. Download an existing installer</B>
-<BR>You will need a matching installer for the product you are localizing.
-In other words, if you are localizing Netscape Communicator version 4.03,
-you need an installer for the Export version of Netscape Communicator 4.03.
-If you are localizing Mozilla Navigator version 5.0, you need an installer
-for the Export version (if any) of Mozilla Navigator version 5.0. Latest
-versions of Netscape products can be downloaded from the <A HREF="http://home.netscape.com/download/index.html">Netscape
-homepage</A>. Older versions of Netscape installers, matching the versions
-used to generate the localization kits, can be found on the <A HREF="ftp://ftp.mozilla.org/pub/l10n-kits/">mozilla.org
-ftp site</A>.
-
-<P>Current Netscape installers come in two forms: base and complete. Complete
-installers include plugins and other components besides the basic Communicator
-software. You may use either installer as the foundation for your work,
-but note that there may not be localization kits for the additional components.
-Even if you choose to distribute the English version of these components,
-however, you must modify the associated initialization files, listed in
-the <A HREF="localize_these_files.html#table1">Localize These Files</A>
-page in order for the additional components to be installed properly.
-
-<P><B>2. Uncompress the Installer files</B>
-<UL>
-<LI>
-Run the installer you downloaded in step 1. This will bring up the following
-dialog (or something very similar):</LI>
-
-<BR><IMG SRC="Is1.jpg" HEIGHT=101 WIDTH=364>
-<LI>
-Click yes. InstallShield will extract all the installation files to your
-temporary directory. (Usually, this will be C:\temp or something similar).
-Once this process is complete, the blue InstallShield background will display.</LI>
-
-<LI>
-Without exiting the installer, locate the unpacked installer files in your
-temp directory and copy them to a new directory. Call this directory "install"
-(or something similar).</LI>
-
-<LI>
-Exit the installer.</LI>
-</UL>
-<B>3. Uncompress the Deinstaller files</B>
-<UL>
-<LI>
-Change directories to your "install" directory. Locate the file cd32*.exe
-(where * equals the version number you are working on. For example, version
-4.03 would be represented as cd32403.exe).</LI>
-
-<LI>
-Execute cd32*.exe. This will bring up a dialog similar to the one shown
-is step 2. Click yes and wait until InstallShield has finished unpacking
-the deinstaller files (the blue InstallShield background will display).</LI>
-
-<LI>
-Without exiting the installer, locate the unpacked deinstaller files in
-your temp directory and copy them to a new directory. Call this directory
-"deinstall" (or something similar).</LI>
-
-<LI>
-Exit the installer.</LI>
-</UL>
-<B>4. Extract localizable installer .DLLs</B>
-<BR>Change directories to your "install" directory. Use the InstallShield
-tool ICOMP.EXE to extract RSUTIL.DLL and _ISUSER.DLL from _SETUP.LIB:
-<UL><TT>Example: icomp _setup.lib -d</TT></UL>
-<B>4. Localize files</B>
-<BR>Consult the <A HREF="localize_these_files.html#table1">Localize These
-Files</A> page to learn which files contain localizable resources.
-
-<P>For each file to be localized, locate the associated Localization Notes
-for that file and follow them carefully.
-
-<P><B>5. Replace original product files contained in nav40.z with localized
-product files</B>
-<BR>Use the ICOMP tool to replace the original (English language) Communicator
-or Navigator files with the ones you have localized using the Windows Front
-End Localization Kit.
-<UL>
-<LI>
-Make sure your localized product directory structure matches the structure
-inside the compressed file nav40.z. (If necessary, uncompress nav40.z (including
-subdirectories), and replace all the localizable files (as identified by
-the Windows Front End Localization Kit) with your localized versions).</LI>
-
-<LI>
-Update nav40.z with your localized files:</LI>
-
-<UL><TT>Example: icomp \<I>kitRoot</I>\products\client\windows\<I>platform</I>\<I>locale</I>\*.*
-nav40.z -i</TT></UL>
-</UL>
-<B>6. Rebuild the self-extracting deinstaller program</B>
-<BR>Use the InstallShield tool EXE Builder to reassemble the self-extracting
-deinstaller archive.
-<UL>
-<LI>
-Specify your "deinstall" directory as the source directory.</LI>
-
-<LI>
-Set compression on.</LI>
-
-<LI>
-Specify Setup.exe as the command line program to run when self-extraction
-is complete. (No optional parameters are required.)</LI>
-
-<LI>
-Specify your "install" directory as the target directory.</LI>
-
-<LI>
-Enter the name of your localized product as the application name.</LI>
-
-<LI>
-Do not specify a password.</LI>
-
-<LI>
-Once creation of your localized self-extracting deinstaller is complete,
-locate the file Setupex.exe in your "install" directory and rename it to
-match the original name of the deinstaller self-extracting program (e.g.,
-cd32403.exe).</LI>
-</UL>
-<B>7. Rebuild the self-extracting installer program</B>
-<BR>Use the InstallShield tool EXE Builder to reassemble the self-extracting
-installer archive.
-<UL>
-<LI>
-Specify your "install" directory as the source directory.</LI>
-
-<LI>
-Set compression on.</LI>
-
-<LI>
-Specify Setup.exe as the command line program to run when self-extraction
-is complete. (No optional parameters are required.)</LI>
-
-<LI>
-Specify any directory you want as the target directory.</LI>
-
-<LI>
-Enter the name of your localized product as the application name.</LI>
-
-<LI>
-Do not specify a password.</LI>
-
-<LI>
-Once creation of your localized self-extracting installer is complete,
-locate the file Setupex.exe in your target directory and rename it to something
-meaningful.</LI>
-</UL>
-<B>8. Complete post-translation processing</B>
-<BR>After translation is complete, you need to test your work and deal
-with any problems:
-<UL>
-<LI>
-Test the localized installer.</LI>
-
-<LI>
-Fix translation bugs using your localization tools or a resource editor.</LI>
-
-<LI>
-Fix dialog size bugs using your localization tools or a resource editor.</LI>
-
-<LI>
-Report core bugs to Netscape.</LI>
-</UL>
-<B>9. Publish your localized product to the Internet</B>
-<BR>As the terms of the universal localization program license agreement
-state, your localized product
-
-<P><TT>"must be made publicly available in executable code form,</TT>
-<BR><TT>free of charge, for electronic delivery via a mechanism</TT>
-<BR><TT>generally accepted in the software development</TT>
-<BR><TT>community."</TT>
-
-<P>In plain English, this means you should post your localized product
-on a publicly accessible http: or ftp: server. You may also want to send
-an announcement of your product's availability to mozilla.org (though you
-are not required to do so).
-
-<P>
-<HR WIDTH="50%">
-<H2>
-<A NAME="branding"></A>Product Branding Issues</H2>
-If you are using this kit under the auspices of the universal localization
-program, you must remove or replace Netscape trademarked strings, images
-and icons in your localized version. Click <A HREF="branding.html">here</A>
-for instructions.
-
-<P>
-<HR WIDTH="50%">
-<H2>
-<A NAME="howtol10n"></A>How to Localize Different Resource Types</H2>
-This section provides you with general information about localizing the
-various resource types and files found with this kit.
-<H3>
-<A NAME="localize_text"></A>Localizing .INI Files</H3>
-
-<UL>Most of the work for the Windows installers is localizing initialization
-(.INI) files. You may use the text editor of your choice to do this work.
-Be sure the localized files are saved as plain text only.
-<H4>
-<A NAME="locnote_ini"></A>Localization Notes</H4>
-Individual localization notes for the installer .INI files are contained
-in the individual HTML documents linked from the <A HREF="localize_these_files.html#table1">Localize
-These Files</A> page.</UL>
-
-<H3>
-<A NAME="localizeURLs"></A>Localizing URLs</H3>
-
-<UL>You will not likely encounter any URLs (Universal Resource Locators)
-in the installers, but if you do, how they are localized depends on whether
-you are creating a branded Netscape version or not. The rules for how to
-handle URLs are found <A HREF="localizeURL.html">here</A>.</UL>
-
-<H3>
-<A NAME="localize_stringtable"></A>Localizing String Tables</H3>
-
-<UL>Use the resource editor of your choice to localize STRINGTABLE resources.
-These are the most sensitive, potentially problematic resource type you
-will be working with. Therefore, you must pay close attention to the instructions
-provided in the localization notes.
-<H4>
-<A NAME="locnote_stringtable"></A>Localization Notes</H4>
-Individual localization notes for the installer resource .DLLs are contained
-in the individual HTML documents linked from the <A HREF="localize_these_files.html#table1">Localize
-These Files</A> page. This section gives you some additional general guidelines
-to follow when localizing the installer binary files.
-<UL>
-<LI>
-Some strings may contain C++ print format strings, such as %s, %ld, %lu,
-etc. Do not modify these while translating the rest of the string.</LI>
-
-<LI>
-Some strings may contain new line characters: \n. In general, you should
-try leave these as you find them.</LI>
-</UL>
-</UL>
-
-<H3>
-<A NAME="localize_menus"></A>Localizing Menus</H3>
-
-<UL>There are no menu resources in the Windows installer</UL>
-
-<H3>
-<A NAME="localize_dialogs"></A>Localizing Dialogs</H3>
-
-<UL>Use the resource editor of your choice to localize and resize DIALOG
-resources. Dialog translation is usually not as tricky as localizing string
-tables; however, you should take care to assign unique pickletters to dialog
-controls.
-<H4>
-<A NAME="locnote_menus"></A>Localization Notes</H4>
-</UL>
-
-<UL>Individual localization notes for the installer resource .DLLs are
-contained in the individual HTML documents linked from the <A HREF="localize_these_files.html#table1">Localize
-These Files</A> page.</UL>
-&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="gettingStarted.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="testKit.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/branding.html

@@ -1,40 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Product Branding Issues</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-Product Branding Instructions</H3>
-Under the terms of the Unlimited Localization Program, you must remove
-or replace all trademarked Netscape terms, brand names, icons, images,
-etc.&nbsp; These trademarks are listed on the page found at the following
-URL:
-
-<P><A HREF="http://home.netscape.com/misc/trademarks.html#trademarks">http://home.netscape.com/misc/trademarks.html#trademarks</A>
-
-<P>Please refer to that page for details.&nbsp; You may not release a localized
-version of the Netscape Communicator with these trademarks left in the
-product.
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="usingKit.html#branding">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER><BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/charsets.htm

@@ -1,383 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>HTML Output of: C:\TEMP\CHARSET.DBF</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H1>
-CSID REFERENCE TABLE</H1>
-Use this table to determine the Character Set ID (CSID) for the character
-set you wish to use, for example, for setting the value of&nbsp; pref("intl.character_set")
-in ALL_PREFS.
-<BR>&nbsp;
-<TABLE BORDER >
-<TR>
-<TH>CSID</TH>
-
-<TH>CHARSET</TH>
-</TR>
-
-<TR>
-<TD>0</TD>
-
-<TD>CS_DEFAULT</TD>
-</TR>
-
-<TR>
-<TD>1</TD>
-
-<TD>CS_ASCII</TD>
-</TR>
-
-<TR>
-<TD>2</TD>
-
-<TD>CS_LATIN1</TD>
-</TR>
-
-<TR>
-<TD>6</TD>
-
-<TD>CS_MAC_ROMAN</TD>
-</TR>
-
-<TR>
-<TD>10</TD>
-
-<TD>CS_LATIN2</TD>
-</TR>
-
-<TR>
-<TD>11</TD>
-
-<TD>CS_MAC_CE</TD>
-</TR>
-
-<TR>
-<TD>14</TD>
-
-<TD>CS_8859_3</TD>
-</TR>
-
-<TR>
-<TD>15</TD>
-
-<TD>CS_8859_4</TD>
-</TR>
-
-<TR>
-<TD>16</TD>
-
-<TD>CS_8859_5</TD>
-</TR>
-
-<TR>
-<TD>17</TD>
-
-<TD>CS_8859_6</TD>
-</TR>
-
-<TR>
-<TD>18</TD>
-
-<TD>CS_8859_7</TD>
-</TR>
-
-<TR>
-<TD>19</TD>
-
-<TD>CS_8859_8</TD>
-</TR>
-
-<TR>
-<TD>20</TD>
-
-<TD>CS_8859_9</TD>
-</TR>
-
-<TR>
-<TD>21</TD>
-
-<TD>CS_SYMBOL</TD>
-</TR>
-
-<TR>
-<TD>22</TD>
-
-<TD>CS_DINGBATS</TD>
-</TR>
-
-<TR>
-<TD>23</TD>
-
-<TD>CS_DECTECH</TD>
-</TR>
-
-<TR>
-<TD>27</TD>
-
-<TD>CS_JISX0201</TD>
-</TR>
-
-<TR>
-<TD>29</TD>
-
-<TD>CS_TIS620</TD>
-</TR>
-
-<TR>
-<TD>35</TD>
-
-<TD>CS_UTF7</TD>
-</TR>
-
-<TR>
-<TD>38</TD>
-
-<TD>CS_USRDEF2</TD>
-</TR>
-
-<TR>
-<TD>39</TD>
-
-<TD>CS_KOI8_R</TD>
-</TR>
-
-<TR>
-<TD>40</TD>
-
-<TD>CS_MAC_CYRILLIC</TD>
-</TR>
-
-<TR>
-<TD>41</TD>
-
-<TD>CS_CP_1251</TD>
-</TR>
-
-<TR>
-<TD>42</TD>
-
-<TD>CS_MAC_GREEK</TD>
-</TR>
-
-<TR>
-<TD>43</TD>
-
-<TD>CS_CP_1253</TD>
-</TR>
-
-<TR>
-<TD>44</TD>
-
-<TD>CS_CP_1250</TD>
-</TR>
-
-<TR>
-<TD>45</TD>
-
-<TD>CS_CP_1254</TD>
-</TR>
-
-<TR>
-<TD>46</TD>
-
-<TD>CS_MAC_TURKISH</TD>
-</TR>
-
-<TR>
-<TD>53</TD>
-
-<TD>INTL_CHAR_SET_MAX</TD>
-</TR>
-
-<TR>
-<TD>254</TD>
-
-<TD>CS_USER_DEFINED_ENCODING</TD>
-</TR>
-
-<TR>
-<TD>255</TD>
-
-<TD>CS_UNKNOWN</TD>
-</TR>
-
-<TR>
-<TD>260</TD>
-
-<TD>CS_SJIS</TD>
-</TR>
-
-<TR>
-<TD>261</TD>
-
-<TD>CS_EUCJP</TD>
-</TR>
-
-<TR>
-<TD>263</TD>
-
-<TD>CS_BIG5</TD>
-</TR>
-
-<TR>
-<TD>264</TD>
-
-<TD>CS_GB_8BIT</TD>
-</TR>
-
-<TR>
-<TD>265</TD>
-
-<TD>CS_CNS_8BIT</TD>
-</TR>
-
-<TR>
-<TD>280</TD>
-
-<TD>CS_CNS11643_1</TD>
-</TR>
-
-<TR>
-<TD>281</TD>
-
-<TD>CS_CNS11643_2</TD>
-</TR>
-
-<TR>
-<TD>282</TD>
-
-<TD>CS_JISX0208</TD>
-</TR>
-
-<TR>
-<TD>284</TD>
-
-<TD>CS_KSC5601</TD>
-</TR>
-
-<TR>
-<TD>286</TD>
-
-<TD>CS_JISX0212</TD>
-</TR>
-
-<TR>
-<TD>287</TD>
-
-<TD>CS_GB2312</TD>
-</TR>
-
-<TR>
-<TD>290</TD>
-
-<TD>CS_UTF8</TD>
-</TR>
-
-<TR>
-<TD>292</TD>
-
-<TD>CS_NPC</TD>
-</TR>
-
-<TR>
-<TD>293</TD>
-
-<TD>CS_X_BIG5</TD>
-</TR>
-
-<TR>
-<TD>303</TD>
-
-<TD>CS_GB2312_11</TD>
-</TR>
-
-<TR>
-<TD>304</TD>
-
-<TD>CS_JISX0208_11</TD>
-</TR>
-
-<TR>
-<TD>305</TD>
-
-<TD>CS_KSC5601_11</TD>
-</TR>
-
-<TR>
-<TD>306</TD>
-
-<TD>CS_CNS11643_1110</TD>
-</TR>
-
-<TR>
-<TD>515</TD>
-
-<TD>CS_JIS</TD>
-</TR>
-
-<TR>
-<TD>525</TD>
-
-<TD>CS_2022_KR</TD>
-</TR>
-
-<TR>
-<TD>564</TD>
-
-<TD>CS_IMAP4_UTF7</TD>
-</TR>
-
-<TR>
-<TD>810</TD>
-
-<TD>CS_UCS2</TD>
-</TR>
-
-<TR>
-<TD>811</TD>
-
-<TD>CS_UCS4</TD>
-</TR>
-
-<TR>
-<TD>819</TD>
-
-<TD>CS_UCS2_SWAP</TD>
-</TR>
-
-<TR>
-<TD>1292</TD>
-
-<TD>CS_KSC_8BIT</TD>
-</TR>
-
-<TR>
-<TD>2308</TD>
-
-<TD>CS_SJIS_AUTO</TD>
-</TR>
-
-<TR>
-<TD>2309</TD>
-
-<TD>CS_EUCJP_AUTO</TD>
-</TR>
-
-<TR>
-<TD>2563</TD>
-
-<TD>CS_JIS_AUTO</TD>
-</TR>
-</TABLE>
-@author: relliott
-<BR>@source: ftang
-<BR>@last updated: Mar. 19, 1998
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1997, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/gettingStarted.html

@@ -1,100 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Getting Started</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-<A NAME="getting started"></A>2. Getting Started</H2>
-Before you can begin using the Windows Front End Localization Kit, you
-must install it and setup your working directories. This is a simple matter
-of unzipping the compressed kit file(s) into the proper directories. Your
-system must also meet certain requirements to run the tools needed to perform
-the localization steps described below.
-
-<P>
-<HR WIDTH="50%">
-<H3>
-<A NAME="sysreqs"></A>System Requirements</H3>
-There a few system requirements for the kit in the strictest sense; however,
-your choice of tools will have their own set of requirements.&nbsp; The
-most likely minimum configuration will be as follows:
-<UL>
-<LI>
-100% IBM compatible PC</LI>
-
-<LI>
-Pentium<SUP><FONT SIZE=-1>&reg;</FONT></SUP> processor</LI>
-
-<LI>
-Microsoft<SUP><FONT SIZE=-1>&reg;</FONT></SUP> Windows NT 3.51 or 4.0 (localized
-versions will help testing but aren't required)</LI>
-
-<LI>
-16 MB RAM</LI>
-
-<LI>
-30 MB available hard disk space</LI>
-
-<LI>
-A visual resource editor, such as those provided with Microsoft<SUP><FONT SIZE=-1>&reg;</FONT></SUP>
-Visual C++, Borland<SUP><FONT SIZE=-1>&reg;</FONT></SUP> C++, etc.</LI>
-
-<LI>
-An active Internet connection and the ability to ftp (send and receive)
-large files</LI>
-
-<LI>
-A Web browser (say, for example, Netscape Communicator ;-)</LI>
-</UL>
-
-<H3>
-
-<HR WIDTH="50%"></H3>
-
-<H3>
-<A NAME="install"></A>Installing the Kit</H3>
-It is recommended that you install the Windows Front End Localization Kit
-in a brand new directory on your development machine. For example, you
-can create a \Netscape_L10N_Kits directory on your hard drive. This becomes
-your <B>kitRoot </B>directory.&nbsp; Place the L10n Kit's .ZIP file in
-that directory and UNZIP it with the -d parameter:
-
-<P>PKUNZIP -d <I>filename</I>
-<UL><B>Example:&nbsp; <TT>PKUNZIP -d winfekit</TT></B></UL>
-
-<HR WIDTH="50%">
-<H3>
-<A NAME="configtool"></A>Configuring Your Tools</H3>
-If you intend to use the Netscape Translation Tools, please refer to the
-<A HREF="../dogTool/dogToolUG.html">Translation Tools User Guide</A> for
-instructions on setting up and using those tools.&nbsp; If you intend to
-use a different localization tool, please refer to that tool's documentation
-for set up and usage instructions.
-<BR>&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="nomenclature.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="usingKit.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS]</A></CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER></CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/isocodes.htm

@@ -1,203 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <TITLE>ISO Locale codes</TITLE>
-</HEAD>
-<BODY>
-
-<CENTER>
-<H1>
-ISO Language and Country Codes</H1></CENTER>
-2 letter language codes are derived from the ISO 639 standard; country
-codes are from ISO 3166. Here are the codes for the locales currently supported
-by the L10n kits. If an entry also includes the country code then you must
-use that as well when creating the locale directory or naming a file.
-<H3>
-ISO Language and Country Codes table</H3>
-
-<TABLE BORDER=5 >
-<TR>
-<TD><U>Language Name</U></TD>
-
-<TD><U>Language Code</U></TD>
-
-<TD><U>Country Code</U></TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Chinese (Traditional)</CENTER>
-</TD>
-
-<TD>
-<CENTER>zh</CENTER>
-</TD>
-
-<TD>
-<CENTER>CN</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Chinese (Simplified)</CENTER>
-</TD>
-
-<TD>
-<CENTER>zh</CENTER>
-</TD>
-
-<TD>
-<CENTER>TW</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Danish</CENTER>
-</TD>
-
-<TD>
-<CENTER>da</CENTER>
-</TD>
-
-<TD>
-<CENTER>DK</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Dutch</CENTER>
-</TD>
-
-<TD>
-<CENTER>nl</CENTER>
-</TD>
-
-<TD>
-<CENTER>NL</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>French</CENTER>
-</TD>
-
-<TD>
-<CENTER>fr</CENTER>
-</TD>
-
-<TD>
-<CENTER>FR</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>German</CENTER>
-</TD>
-
-<TD>
-<CENTER>de</CENTER>
-</TD>
-
-<TD>
-<CENTER>DE</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Italian</CENTER>
-</TD>
-
-<TD>
-<CENTER>it</CENTER>
-</TD>
-
-<TD>
-<CENTER>IT</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Japanese</CENTER>
-</TD>
-
-<TD>
-<CENTER>ja</CENTER>
-</TD>
-
-<TD>
-<CENTER>JP</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Korean</CENTER>
-</TD>
-
-<TD>
-<CENTER>ko</CENTER>
-</TD>
-
-<TD>
-<CENTER>KR</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Portuguese</CENTER>
-</TD>
-
-<TD>
-<CENTER>pt</CENTER>
-</TD>
-
-<TD>
-<CENTER>BR</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Spanish</CENTER>
-</TD>
-
-<TD>
-<CENTER>es</CENTER>
-</TD>
-
-<TD>
-<CENTER>ES</CENTER>
-</TD>
-</TR>
-
-<TR>
-<TD>
-<CENTER>Swedish</CENTER>
-</TD>
-
-<TD>
-<CENTER>sv</CENTER>
-</TD>
-
-<TD>
-<CENTER>SE</CENTER>
-</TD>
-</TR>
-</TABLE>
-
-<CENTER><BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1997, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/kitOverview.html

@@ -1,44 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Kit Overview</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="kitoverview"></A>Kit Overview</H3>
-This kit is primarily intended for knowledgeable 3rd parties, familiar
-with the localization process and with commonly available localization
-and resource editing tools.&nbsp; Using this kit, you will localize the
-components that make up the Windows <I>front end</I> (the Windows-specific,
-user visible portions) of the Netscape Communicator or Navigator. You may
-use the Netscape-developed translation tools (DogLev and ToolCool) or another
-tool set of your choice to leverage and localize STRING TABLE, MENU, DIALOG
-and certain DATA resource types. You will need to use a Windows compatible
-resource editor to localize the remaining DATA resources and to resize
-DIALOGs.
-<BR>&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="projectOverview.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="kitStruct.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;<BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/kitStruct.html

@@ -1,75 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Kit Structure</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="kitstruct"></A>Kit Structure and Organization</H3>
-When you install this Localization Kit you will find a number of new directories
-on your hard disk. Each directory is named so as to be fairly self-explanatory,
-but the following diagram and description may help avoid any confusion
-you may have about what's what.
-<H4>
-<IMG SRC="winfekit.jpg" HEIGHT=114 WIDTH=149></H4>
-
-<H4>
-Description of Kit Directories</H4>
-
-<UL>
-<LI>
-The <B><TT>kitRoot</TT> </B>directory is wherever you install the Netscape
-Localization Kits.</LI>
-
-<LI>
-The <B><TT>l10nkits</TT> </B>directory contains the tools and documentation
-you need to complete your work (see below)</LI>
-
-<LI>
-The <B><TT>products</TT> </B>directory contains the English language version
-of the files you will be translating. This kit concerns the files contained
-in the 32 bit Windows client product.</LI>
-</UL>
-The <B><TT>l10nkit</TT> </B>directory tree has the following structure:
-
-<P><IMG SRC="l10ntree.jpg" HEIGHT=133 WIDTH=173>
-<UL>
-<LI>
-Since this kit concerns the Windows client Communicator product (as opposed
-to our server products) all the relevant documentation and tools are found
-under the <B><TT>client\windows </TT></B>directory.</LI>
-
-<LI>
-The <B><TT>docs</TT> </B>directory contains documentation on the Kit, including
-the file you are reading now.</LI>
-
-<LI>
-The <B><TT>tools</TT> </B>directory contains any tools provided with the
-Kit, such as the Netscape Translation Tool.</LI>
-</UL>
-&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="kitOverview.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="nomenclature.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;<BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/localizeAboutplg.html

@@ -1,81 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Localizing ABOUTPLG</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-<A NAME="locnote_aboutplg"></A>Localization Notes for ABOUTPLG</H4>
-This resource contains the HTML and JavaScript source of the about:plugins
-page. You only need to translate the user-visible portions of this file,
-as indicated below. DO NOT translate tags or JavaScript language elements.
-Unless you plan to create and support your own plugins, you probably should
-not localize the URL contained in this page.
-
-<P>Note: this is a cross platform resource; you may be able to reuse this
-localization work for Macintosh and/or Unix versions.
-
-<P>Just translate the items in <FONT COLOR="#FF00FF">magenta</FONT>:
-<UL>
-<LI>
-<TT>&lt;TITLE><FONT COLOR="#FF00FF">About Plug-ins</FONT>&lt;/TITLE></TT></LI>
-
-<LI>
-<TT>document.writeln("&lt;b>&lt;font size=+3><FONT COLOR="#FF00FF">Installed
-plug-ins</FONT>&lt;/font>&lt;/b>&lt;br>");</TT></LI>
-
-<LI>
-<TT>document.writeln("&lt;b>&lt;font size=+2><FONT COLOR="#FF00FF">No plug-ins
-are installed.</FONT>&lt;/font>&lt;/b>&lt;br>");</TT></LI>
-
-<LI>
-<TT>document.writeln("<FONT COLOR="#FF00FF">For more information on Netscape
-plug-ins,</FONT></TT></LI>
-
-<BR><TT>&lt;A REF=<FONT COLOR="#FF00FF">http://home.netscape.com/comprod/products/navigator/version_2.0/plugins/index.html</FONT>></TT>
-<BR><TT><FONT COLOR="#FF00FF">click here</FONT>&lt;/A>.&lt;p>&lt;hr>");</TT>
-<LI>
-<TT>document.writeln("&lt;dl>&lt;dd><FONT COLOR="#FF00FF">File name:</FONT>");</TT></LI>
-
-<LI>
-<TT>document.writeln("&lt;tr>&lt;th width=20%>&lt;font size=-1><FONT COLOR="#FF00FF">Mime
-Type</FONT>&lt;/font>&lt;/th>");</TT></LI>
-
-<LI>
-<TT>document.writeln("&lt;th width=50%>&lt;font size=-1><FONT COLOR="#FF00FF">Description</FONT>&lt;/font>&lt;/th>");</TT></LI>
-
-<LI>
-<TT>document.writeln("&lt;th width=20%>&lt;font size=-1><FONT COLOR="#FF00FF">Suffixes</FONT>&lt;/font>&lt;/th>");</TT></LI>
-
-<LI>
-<TT>document.writeln("&lt;th>&lt;font size=-1><FONT COLOR="#FF00FF">Enabled</FONT>&lt;/th>&lt;/tr>");</TT></LI>
-
-<LI>
-<TT>enabled = "<FONT COLOR="#FF00FF">No</FONT>";</TT></LI>
-
-<LI>
-<TT>enabled = "<FONT COLOR="#FF00FF">Yes</FONT>";</TT></LI>
-</UL>
-&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table3">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/localizeAllPref.html

@@ -1,154 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Localizing ALL_PREFS</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-<A NAME="locnote_allprefs"></A>Localization Notes for ALL_PREFS</H4>
-These preferences are identified in the localization notes as "ALL_PREFSRCDATA"
-followed by the Javascript function name for that preference.&nbsp; For
-example:
-<UL><TT>ALL_PREFSRCDATAnetwork.search.url</TT></UL>
-The localizable portion of this preference will appear in the XL_STR field.&nbsp;
-If this value is a string, it will be surrounded with quotes.&nbsp; If
-it is a number, it will not.&nbsp; Do not delete quotes if they are present
-and do not add them if they are absent!&nbsp; Many entries also begin with
-tab characters or initial spaces; it is best not to alter these, as well.
-
-<P><FONT COLOR="#FF0000">NOTE: the following section is for reference,
-showing the way the complete Javascript syntax looks.&nbsp; The entries
-contained in the translation databases separate the Javascript function
-from the data that function returns. Comments are reproduced in the COMMENT
-field of the translation database where appropriate.</FONT>
-
-<P>You only need to localize the following entries. The parts you need
-to change are highlighted in <FONT COLOR="#FF00FF">majenta</FONT>. Comments
-are in <FONT COLOR="#009900">green</FONT>. Localize URLs according to the
-<A HREF="localizeURL.html">rules</A>.
-<UL>
-<LI>
-pref("network.<FONT COLOR="#000000">search</FONT>.url", "<FONT COLOR="#FF00FF">http://cgi.netscape.com/cgi-bin/url_search.cgi?search=</FONT>");</LI>
-
-<UL><FONT COLOR="#009900">This URL is connected to the Navigator's Search
-button.</FONT>
-<BR>&nbsp;</UL>
-
-<LI>
-pref("browser.startup.homepage", "<FONT COLOR="#FF00FF">http://home.netscape.com/</FONT>");</LI>
-
-<UL><FONT COLOR="#009900">This is the default home page value that is attached
-to the Home button and the Home menu item.</FONT></UL>
-</UL>
-
-<UL>
-<LI>
-pref("browser.personal_toolbar_button.max_chars", <FONT COLOR="#FF00FF">15</FONT>);</LI>
-
-<UL><FONT COLOR="#009900">This determines the maximum number of characters
-a personal toolbar button title can contain.&nbsp; You may not need to
-change this, but it's there if you do.</FONT>
-<BR>&nbsp;</UL>
-
-<LI>
-pref("intl.accept_languages",&nbsp;&nbsp;&nbsp; "<FONT COLOR="#FF00FF">en</FONT>");</LI>
-
-<UL><FONT COLOR="#009900">This determines the default value of the ACCEPT_LANG
-property of the META tag. You can see this value by choosing Edit | Preferences,
-select Navigator | Language; the default value will be the 2 letter ISO
-Language code value you supply here.</FONT>
-<BR>&nbsp;</UL>
-
-<LI>
-pref("intl.accept_charsets",&nbsp; "<FONT COLOR="#FF00FF">iso-8859-1</FONT>,*,utf-8");</LI>
-
-<UL><FONT COLOR="#009900">Replace iso-8859-1 with sjis for Japanese, euc-kr
-for Korean, gb for Simplified Chinese, Big5 for Traditional Chinese, iso8859-2
-for Latin 2 languages.</FONT>
-<BR>&nbsp;</UL>
-
-<LI>
-pref("intl.character_set",&nbsp; <FONT COLOR="#FF00FF">2</FONT>);</LI>
-
-<UL><FONT COLOR="#009900">You only need to change this for non-LATIN1 languages.&nbsp;
-Use the <A HREF="charsets.htm">CSID Reference table </A>to look up the
-appropriate value for other languages.</FONT>
-<BR>&nbsp;</UL>
-
-<LI>
-pref("intl.font_encoding", 6);</LI>
-
-<UL><FONT COLOR="#009900">maybe not used, 6 = CS_MAC_ROMAN, 1292 = ko,
-263 = trad. chinese, 264 = simp. chinese</FONT></UL>
-&nbsp;
-<LI>
-pref("editor.template_location", <FONT COLOR="#FF00FF">http://home.netscape.com/home/gold3.0_templates.html</FONT>");</LI>
-
-<LI>
-pref("editor.default_template_location", "<FONT COLOR="#FF00FF">http://home.netscape.com/home/gold3.0_templates.html</FONT>");</LI>
-
-<UL><FONT COLOR="#009900">Localize these URL according to the </FONT><A HREF="localizeURL.html">rules</A><FONT COLOR="#009900">.</FONT></UL>
-
-<LI>
-pref("editor.html_directory",&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "<FONT COLOR="#FF00FF">C:\\My
-Documents</FONT>");</LI>
-
-<LI>
-pref("editor.image_directory",&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "<FONT COLOR="#FF00FF">C:\\My
-Documents</FONT>");</LI>
-
-<UL><FONT COLOR="#009900">If the My Documents directory is translated on
-the localized version of Windows you working on, then match this preference
-with the localized value.</FONT>
-<BR>&nbsp;</UL>
-
-<LI>
-pref("editor.color_scheme",&nbsp;&nbsp;&nbsp;&nbsp; "<FONT COLOR="#FF00FF">Netscape
-Default Colors</FONT>");</LI>
-
-<UL><FONT COLOR="#009900">This string should match the value used to translate
-STRINGTABLE42169 (but it's not critical if it doesn't).</FONT>
-<BR>&nbsp;</UL>
-
-<LI>
-pref("ldap.directory1.description", "<FONT COLOR="#FF00FF">Personal Address
-Book</FONT>");</LI>
-
-<LI>
-pref("ldap_1.directory1.description", "<FONT COLOR="#FF00FF">Personal Address
-Book</FONT>");</LI>
-
-<UL><FONT COLOR="#009900">These entries appears as the description for
-searching the personal address book in a mail directory search.&nbsp; Translate
-them the way you do all the other instances of this string.</FONT>
-<BR>&nbsp;</UL>
-
-<LI>
-&nbsp;pref("netcaster.containers.container1", "-3;'Channel_Finder'; '<FONT COLOR="#FF00FF">http://netcaster.netscape.com/finder/container/index.html</FONT>';
-1440;0");</LI>
-
-<UL><FONT COLOR="#009900">Localize this URL according to the </FONT><A HREF="localizeURL.html">rules</A><FONT COLOR="#009900">.</FONT></UL>
-</UL>
-&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="usingKit.html#locnote_allprefs">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/localizeBookmarks.html

@@ -1,36 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Localizing Bookmarks</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-<A NAME="locnote_bookmark"></A>Localization Notes for&nbsp; BOOKMARKS.HTM</H4>
-As part of the Unlimited Localization Program, you may choose to include
-the default set of bookmarks that came with this kit, or you may create
-your own bookmarks file.&nbsp; Assuming you include a bookmarks file, you
-should save it to&nbsp; <B><TT>kitRoot\products\client\windows\<I>platform</I>\<I>locale</I>\nav40\program\defaults\bookmark.htm</TT>.</B>
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table2">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER></CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-<BR>&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/localizeConfigPref.html

@@ -1,108 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Localizing CONFIG_PREFS</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-<A NAME="locnote_configprefs"></A>Localization Notes for CONFIG_PREFS</H4>
-These entries make up the configurable Guide Toolbar and Help menu items
-and their functions. As part of the Unlimited Localization Program, you
-may define your own set of Guide Toolbar and Help Menu items.&nbsp; You
-MUST remove or replace with your own links the following Help Menu items:
-<UL>
-<LI>
-Release Notes</LI>
-
-<LI>
-Product Information and Support</LI>
-
-<LI>
-Software Updates</LI>
-
-<LI>
-Register Now</LI>
-
-<LI>
-Member Services</LI>
-</UL>
-CONFIG_PREF items are identified in the localization notes as "CONFIG_PREFSRCDATA"
-followed by the Javascript function name.&nbsp; For example,
-<UL><TT>CONFIG_PREFSRCDATAtoolbar.places.default_url</TT></UL>
-Most items in this list of preferences consist of two related components:
-a label and a URL.&nbsp; To localize a label, only edit the portion of
-the preference that are within the second set of quotes.&nbsp; For example,
-<UL>
-<LI>
-config("toolbar.places.item_0.label","<FONT COLOR="#FF00FF">The Internet</FONT>");</LI>
-</UL>
-The words, "The Internet" are contained in the second set of quotes; that
-is the part you localize.&nbsp; Because these are button labels, you should
-try to keep them as short as possible.&nbsp; If you find that you must
-use a long word or phrase in your translation, you may discover that the
-buttons no longer display the entire text.&nbsp; You can increase the maximum
-number of characters the Toolbar buttons will display by increasing the
-value of the <TT>browser.personal_toolbar_button.max_chars </TT>preference.
-
-<P>You can use the "-" character in a label to create a separator.
-
-<P>You can specify a sub-folder in the Guide Toolbar by specifying the
-URL to be the word "FOLDER".&nbsp; For example:
-<UL>
-<LI>
-config("personal_toolbar.item_1.url","<FONT COLOR="#FF0000">FOLDER</FONT>");</LI>
-</UL>
-This lets the code that lays out the toolbar know that the current item
-is a folder with sub-folders.&nbsp; <FONT COLOR="#FF0000">DO NOT </FONT>localize
-the word "FOLDER".
-<H4>
-Forbidden CONFIG_PREFS Resources</H4>
-There are some URLs in CONFIG_PREFS which must not be changed in any way.&nbsp;
-The first kind is the about: page URLs:
-<UL>
-<LI>
-config("menu.help.item_12.url","about:plugins");</LI>
-
-<LI>
-config("menu.help.item_13.url","about:fonts");</LI>
-</UL>
-You may translate the associated labels but not these URLs. (You can, of
-course, delete them entirely, but then you won't have access to these "about"
-pages via the menus.)&nbsp; Refer to the <A HREF="#localizeURLs">Localizing
-URLs</A> section for more information.
-<BR>Finally, some items in CONFIG_PREFS are non-localizable Javascript
-preference values.&nbsp; For example,
-<UL>
-<LI>
-config("toolbar.logo.frames",<FONT COLOR="#FF0000">-1</FONT>);</LI>
-
-<LI>
-config("personal_toolbar.CreateNewToolbar", <FONT COLOR="#FF0000">false</FONT>);</LI>
-
-<LI>
-config("personal_toolbar.NewToolbarFolderName", <FONT COLOR="#FF0000">""</FONT>);</LI>
-</UL>
-Don't alter these.
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="usingKit.html#locnote_configprefs">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;<BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-<BR>&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/localizeLicense.html

@@ -1,67 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Localizing the License</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H4>
-<A NAME="locnote_license"></A>Localization notes for LICENSE</H4>
-You must include the Netscape End User License Agreement included with
-this kit in your localized product.&nbsp; The license file may be found
-at: <TT>products\client\windows\<I>platform</I>\<B>en</B>\license\export\eula\<B>license.txt</B></TT>.
-The Localization Kit gives no information on the nature of this license
-agreement; it only tells you how to put a localized license into the software.
-Whether or not you localize this license (this may depend on your desires
-or upon the laws of your country), you must include this in your localized
-binaries by following this procedure. (This example uses Microsoft<SUP><FONT SIZE=-1>&reg;</FONT></SUP>
-MSDEV; if you prefer a different resource editor you may need to execute
-slightly different steps):
-<UL>
-<LI>
-Open license.txt in a text editor window.</LI>
-
-<LI>
-Choose <B><TT>Edit | Select All.</TT></B></LI>
-
-<LI>
-Choose <B><TT>Edit | Copy</TT></B>.</LI>
-
-<LI>
-Open resdll.dll (make sure you have the right one!).</LI>
-
-<LI>
-Expand the DATA section, open the LICENSE entry.</LI>
-
-<LI>
-Choose <B><TT>Edit | Select All</TT></B>.</LI>
-
-<LI>
-Choose <B><TT>Edit | Paste</TT></B> to paste the new text over the old:</LI>
-
-<LI>
-Terminate the entry with a null character: type "0"</LI>
-
-<BR>Save and exit.</UL>
-&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table3">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/localizeNpnul.html

@@ -1,42 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Localizing NPNUL</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="localize_npnul"></A>Localizing the NULL Plugin</H3>
-The so-called "NULL" plugin is the default plugin that ships with all versions
-of the Communicator.&nbsp; It's job is to list the plugins that you have
-installed, and if you don't have a requested plugin, to help you get it.
-
-<P>The NULL plugin consists of a single file, npnul32.dll, located in the
-<B><TT>kitRoot\products\client\windows\<I>platform</I>\<I>locale</I>\nav40\program\plugins\</TT></B>
-directory.&nbsp; Localization notes have been provided for you to use when
-localizing the resources for this file.&nbsp; Instructions for individual
-resources can be found in the COMMENT field of the matching DOG file, npnul32.dog
-(or npnul16.dog for Windows 3.1)
-<CENTER>&nbsp;</CENTER>
-&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="localize_these_files.html#table1">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/localizeURL.html

@@ -1,55 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Localizing URLs</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="localizeURLs"></A>Localizing URLs</H3>
-Many resources of all types in the Communicator contain Internet addresses
-in the form of URLs (Universal Resource Locators). Most of these point
-to locations within the Netscape domain; as part of the Unlimited Localization
-Program, you can leave these as they are, or you may change them as you
-desire.
-<H3>
-Internal URLs</H3>
-There are a number of internal URLs that <FONT COLOR="#FF0000">should not
-be changed</FONT>.&nbsp; These are the strings that look like <B>about:[some
-value]</B>.&nbsp; These point to internally contained resources, such as
-the main About Communicator page.&nbsp; If you localize these strings you
-will not be able to load these pages.&nbsp; The main examples you might
-find are:
-<UL>
-<LI>
-about:</LI>
-
-<LI>
-about:plugins</LI>
-
-<LI>
-about:fonts</LI>
-</UL>
-For more examples and information on these internal URLs go <A HREF="http://help.netscape.com/kb/client/970513-4.html">here</A>.
-<BR>&nbsp;
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="usingKit.html#localizeURLs">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;<BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/localize_these_files.html

@@ -1,141 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Localize these Files</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="localize_these_files"></A>Localize These Files</H3>
-This section tells you exactly what files need to be localized. The following
-tables contain two columns:
-<UL>
-<LI>
-The file to be localized column gives the specific file name. The path
-name given for each file is relative to the Windows Front End Localization
-Kit's starting point; e.g. <B><TT>\kitRoot\products\client\windows\<I>platform</I>\de</TT></B>
-(German in this example).&nbsp; If the file or resource name is a hypertext
-link, further information can be found by following that link.</LI>
-
-<LI>
-The purpose column describes the basic purpose of this file.</LI>
-</UL>
-<A NAME="table1"></A><FONT SIZE=-1>Table 1. Binary files to be localized</FONT>
-<TABLE BORDER >
-<TR>
-<TD><B>File to be localized&nbsp;</B></TD>
-
-<TD><B>Purpose</B></TD>
-</TR>
-
-<TR>
-<TD><TT>nav40\program\<B>brpref32.dll</B></TT></TD>
-
-<TD>Browser preferences</TD>
-</TR>
-
-<TR>
-<TD><TT>nav40\program\<B>editor32.dll</B></TT></TD>
-
-<TD>Composer User Interface</TD>
-</TR>
-
-<TR>
-<TD><TT>nav40\program\<B>edpref32.dll</B></TT></TD>
-
-<TD>Composer preferences</TD>
-</TR>
-
-<TR>
-<TD><TT>nav40\program\<B>mnpref32.dll</B></TT></TD>
-
-<TD>Mail and News preferences</TD>
-</TR>
-
-<TR>
-<TD><TT>nav40\program\<B>nsmailui.dll</B></TT></TD>
-
-<TD>Mail User Interface</TD>
-</TR>
-
-<TR>
-<TD><TT>nav40\program\<B>nsnotify.exe</B></TT></TD>
-
-<TD>Mail notification User Interface</TD>
-</TR>
-
-<TR>
-<TD><TT>nav40\program\<B>prefui32.dll</B></TT></TD>
-
-<TD>Preference User Interface&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><TT>nav40\program\<B>resdll.dll</B></TT></TD>
-
-<TD>Main Browser User Interface</TD>
-</TR>
-
-<TR>
-<TD><TT><A HREF="localizeNpnul.html">nav40\program\plugins\<B>npnul32.dll</B></A></TT></TD>
-
-<TD>NULL plugin</TD>
-</TR>
-</TABLE>
-
-
-<P><A NAME="table2"></A><FONT SIZE=-1>Table 2. External files to be localized</FONT>
-<TABLE BORDER WIDTH="100%" >
-<TR>
-<TD><B>File to be localized</B></TD>
-
-<TD><B>Purpose</B></TD>
-</TR>
-
-<TR>
-<TD><TT><A HREF="localizeBookmarks.html">nav40\program\defaults\<B>bookmark.htm</B></A></TT></TD>
-
-<TD>Default bookmarks file.</TD>
-</TR>
-</TABLE>
-<BR>
-<A NAME="table3"></A><FONT SIZE=-1>Table 3. DATA resources requiring localization</FONT>
-<TABLE BORDER >
-<TR>
-<TD>Resource Name&nbsp;</TD>
-
-<TD>Purpose</TD>
-</TR>
-
-<TR>
-<TD><A HREF="localizeAboutplg.html">ABOUTPLG</A></TD>
-
-<TD>HTML source of about:plugins page</TD>
-</TR>
-
-<TR>
-<TD><A HREF="localizeLicense.html">LICENSE</A></TD>
-
-<TD>Internal software license agreement</TD>
-</TR>
-</TABLE>
-
-<CENTER>&nbsp;</CENTER>
-&nbsp;
-<CENTER><TABLE COLS=1 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER></CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/nomenclature.html

@@ -1,108 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Conventions</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="nomenclature"></A>Nomenclature and Typographical Conventions</H3>
-<B>Typographical Conventions</B>
-<BR>Words in <I>italics</I> typeface represent a variable term or phrase,
-meant to be replaced by another value at "runtime."&nbsp; Example:
-<UL><I>locale</I> -- replaced by a 2- or 4 letter locale code; e.g. zhtw</UL>
-Words in <B>bold</B> typeface, using a proportional font, represent a literal
-value in a string that might also contain a variable word or phrase. Example:
-<UL><B>4.03 [</B><I>locale</I><B>]</B> -- 4.03 [ ] are literal values,
-while <I>locale</I> is a variable.
-<UL>&nbsp;</UL>
-</UL>
-Words in a <TT>fixed width font</TT> represent file or directory names,
-or DOS or Windows commands to be typed as they appear.&nbsp; Sometimes,
-part or all of the path will be in <B><TT>bold</TT></B>, for emphasis.
-Examples:
-<UL>Change to the <B><TT><I>kitRoot</I>\l10nkits\client\windows\tools</TT></B><TT>
-</TT>directory
-<BR>Execute <B><TT>RTRNKIT</TT></B></UL>
-<B>Nomenclature</B>
-<BR>Throughout this document, certain terms and phrases will be used repeatedly:
-
-<P><FONT SIZE=-1>Table 1. Nomenclature and Typographical Conventions</FONT>
-<TABLE BORDER >
-<TR>
-<TD><B><TT>kitRoot</TT> </B>directory&nbsp;</TD>
-
-<TD>indicates the starting or topmost directory of the Windows Front End
-Localization Kit.</TD>
-</TR>
-
-<TR>
-<TD><I>platform</I></TD>
-
-<TD>either 16 or 32 bit, depending on the version you are working on.</TD>
-</TR>
-
-<TR>
-<TD><I>locale</I></TD>
-
-<TD>in general, this refers to the language into which you are localizing
-the product. The list of valid locale names is defined in the <A HREF="isocodes.htm">ISO
-Language and Country Codes Table</A>.</TD>
-</TR>
-
-<TR>
-<TD>localization database</TD>
-
-<TD>a database generated by a leveraging tool from a set of matched binary
-resource files.&nbsp;</TD>
-</TR>
-
-<TR>
-<TD>localization notes</TD>
-
-<TD>any special instructions, including the "translate/don't translate"
-flag, associated with a given resource.&nbsp; Localization notes are contained
-in the localization database for each resource module.</TD>
-</TR>
-
-<TR>
-<TD><I>leverage</I></TD>
-
-<TD>The process of merging previous localized versions of a file into a
-current version.&nbsp;</TD>
-</TR>
-
-<TR>
-<TD>forbidden resource</TD>
-
-<TD>A resource that cannot be changed from the original value without (negatively)
-impacting the functionality of the product. These are identified in the
-localization databases.</TD>
-</TR>
-</TABLE>
-&nbsp;
-<BR>&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="kitStruct.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="gettingStarted.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;<BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/projectOverview.html

@@ -1,73 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Project Overview</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-<A NAME="overviews"></A>1. Project Overview</H2>
-
-<CENTER><B><FONT COLOR="#009900">Welcome to the Netscape Communicator/Navigator
-Localization Kit!</FONT></B></CENTER>
-
-
-<P>This localization kit will assist you in creating a localized version
-of Netscape Communicator or Navigator for the 32-bit Windows platform.
-Using the instructions and optionally, the tools provided in this kit,
-you can translate the product's menus, dialogs and error messages to the
-language of your choice. As long as you follow the terms of the license
-agreement under which this kit is distributed, you are free to do what
-you want with the resulting localized product.
-
-<P>Localizing the Netscape client is based on "binary" or "no-compile"localization
-model. Instead of localizing resource script (.RC) files, which must be
-recompiled to produce a working localized version, you work directly on
-the binary resource module (.DLL or .EXE) files. You have access to <I>localization
-notes</I> to assist and guide you through some of the trickier areas of
-the product.&nbsp; Finally, this kit contains several tools developed by
-Netscape to expedited the localization process; however, you may, if you
-prefer, work with the localization tools of your choice.
-
-<P>The no-compile localization model offers a number of key benefits over
-source file translation:
-<UL>
-<LI>
-A simpler kit environment - no make files or bulky source trees are required.</LI>
-
-<LI>
-Leveraging previous translations is simpler when resources can be stored
-in a database, decreasing translation time.</LI>
-
-<LI>
-"Forbidden" resources can be locked from over-translation, improving the
-quality of translated products.</LI>
-
-<BR>Localization notes and instructions can be displayed along side the
-actual resource being localized, allowing the translator immediate access
-to this information.</UL>
-&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="splash.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="kitOverview.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;<BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/reference.html

@@ -1,77 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Reference</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-<A NAME="reference"></A>Reference</H2>
-This section summarizes the references used throughout this document.&nbsp;
-In addition, other miscellaneous references may be found here.
-
-<P><FONT SIZE=-1>Table 5. Reference Links</FONT>
-<TABLE BORDER COLS=3 WIDTH="100%" >
-<TR>
-<TD><A HREF="isocodes.htm">Locale Table (local)</A></TD>
-
-<TD><A HREF="http://www.indigo.ie/egt/standards/iso639/iso639-en.html">Locale
-Table (remote)</A></TD>
-
-<TD><A HREF="http://home.netscape.com/comprod/products/communicator/datasheet.html">Communicator
-Data Sheet</A></TD>
-</TR>
-
-<TR>
-<TD><A HREF="http://home.netscape.com/menu/intl/">Communicator International
-Features</A></TD>
-
-<TD><A HREF="http://help.netscape.com/kb/client/970513-4.html">"about:"
-URLs and easter eggs</A></TD>
-
-<TD><FONT COLOR="#009900"><A HREF="charsets.htm">CSID Reference table&nbsp;</A></FONT></TD>
-</TR>
-
-<TR>
-<TD><TT><FONT COLOR="#009900"><A HREF="xpencui.htm">Cross-Product Encoding
-UI Names</A></FONT></TT></TD>
-
-<TD></TD>
-
-<TD></TD>
-</TR>
-</TABLE>
-<BR>
-Following are links to the two main header files used in the Communicator
-project, resource.h and allxpstr.h. Resource.h contains the resource IDs
-for the Windows Front End resources, while allxpstr.h contains both the
-ID and the actual strings of the cross platform messages. These are provided
-for <FONT COLOR="#FF0000">reference only</FONT>, as the resource name is
-sometimes more descriptive than the numeric ID used in the translation
-databases. <FONT COLOR="#FF0000">You do not need to localize these files!</FONT>
-<UL>
-<LI>
-Look at <A HREF="resource.h">resource.h</A></LI>
-
-<LI>
-Look at <A HREF="allxpstr.h">allxpstr.h</A></LI>
-</UL>
-&nbsp;
-<CENTER><TABLE COLS=1 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/reportingBugs.html

@@ -1,54 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Reporting Bugs</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H3>
-<A NAME="reporting_bugs"></A>Reporting Bugs</H3>
-Any bugs in the localization kits you find should be reported to <A HREF="http://www.mozilla.org">mozilla.org</A>
-as soon as possible. When you report a bug, try to be as specific as you
-can about the exact steps needed to reproduce the bug.&nbsp; Provide a
-complete description of the problem versus the expected results.&nbsp;
-You should let us know if the problem is 100% reproducible (it happens
-every time), or if it is intermittant.&nbsp; If you think that your operating
-environment may play some factor, let us know the details of that.&nbsp;
-Finally, before reporting any bug, you should make sure that the problem
-doesn't also happen in the US English product (if it does, we still want
-to know, but it may not be possible to fix it through the localization
-kits or tools as they are now).
-
-<P>To report a bug, post a message to the following mozilla.org newsgroup:
-<CENTER></CENTER>
-
-<CENTER><A HREF="news://secnews.netscape.com/netscape.mozilla.public.general">news://secnews.netscape.com/netscape.mozilla.public.general</A></CENTER>
-
-
-<P>Be sure to include the information described above.
-<BR>&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="testKit.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="troubleshooting.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/returnKit.html

@@ -1,58 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Returning the Kit</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-<A NAME="returnkit"></A>6. Returning the Finished Kit</H2>
-
-<P>Once you are satisfied with the quality of your localization efforts,
-you are required by the terms of the Unlimited Localization Program
-license to make your localized product publicly available.  The exact details of 
-how you do this is up to you, the most commonly acceptable method is to post
-your localized product to a publicly accessible ftp site.
-<P>
-You should post just the localized versions of the files mentioned in the Localize These 
-Files section of this document.  For ease of transfer, you may create a compressed archive 
-in the .ZIP file format that contains the localized files.  Create one .ZIP file for each 
-language/platform you do. If you are publishing more than one language or platform, you 
-may combine multiple .ZIP files into one master .ZIP file if this makes your life easier. 
-<P>
-If your localized product includes your own trademarks, you should identify these and any
-restrictions you are placing on their use.  You must also include a copy of the End User 
-License Agreement (EULA), as well as a notice stating that Netscape Communications 
-is not required to support your product, and that you are the Licensor referred to in the EULA.
-Please refer to the Universal Localization Agreement for the exact legal requirements.
-<P>
-Once your localized product is publicly available, you may inform the world in any manner you 
-choose, but we encourage you to also post the download location to the mozilla.org 
-Announcements newsgroup (netscape.public.mozilla.announce). 
-<P>
-
-<CENTER><FONT COLOR="#008000"><FONT SIZE=+2>Congratulations! You are done!</FONT></FONT></CENTER>
-
-<BR>
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="troubleshooting.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<P>
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-
-<CENTER></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/splash.html

@@ -1,47 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; I) [Netscape]">
-   <TITLE>Title Page</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<CENTER>
-<H1>
-NETSCAPE COMMUNICATOR</H1></CENTER>
-
-<CENTER><IMG SRC="SPLASH.JPG" NOSAVE HEIGHT=261 WIDTH=390></CENTER>
-
-<CENTER>
-<H1>
-Localization Kit</H1></CENTER>
-
-<CENTER>
-<H3>
-for Microsoft<SUP><FONT SIZE=+0>&reg;</FONT></SUP> Windows (32-bit version)</H3></CENTER>
-
-<CENTER>
-<H3>
-Revision 1.2</H3></CENTER>
-
-<CENTER>Copyright &copy; 1994-1998 Netscape&reg; Communications Corporation,
-All rights reserved.</CENTER>
-&nbsp;
-<BR>&nbsp;
-<CENTER><TABLE COLS=2 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="projectOverview.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/testKit.html

@@ -1,130 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Testing the Localized Resources</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-<A NAME="testkit"></A>4. Ensuring Quality</H2>
-The quality of your localized version will have a large impact on its acceptance
-in the marketplace.&nbsp; You can greatly enhance your chances of producing
-a quality product by using experienced and skilled localizers, and by performing
-post-translation testing.
-
-<P>When performing the actual translation, you should be sensitive to a
-number of issues:
-<UL>
-<LI>
-Completeness: you should aim for as thorough a translation as possible.&nbsp;
-Try not to leave portions of the product untranslated. However, be aware
-that some terms may best be left in English, depending on local conventions.</LI>
-
-<LI>
-Suitability: all translations should be suitable and appropriate for product,
-the language, the market and the customers you intend to reach.&nbsp; This
-includes using the proper technical terminology for a give platform or
-computer operation, as well as using language that is readily understood
-by the average user of the product in a given language.&nbsp; You should,
-where possible, try to use terminology which is similar to other products
-available on the same platform (without violating copyrights or trademarks,
-of course).</LI>
-
-<LI>
-Accuracy: you should be sure your translation conveys the same meaning
-and intention as the original English.</LI>
-
-<LI>
-Grammar and spelling: you should be sure your translation is grammatically
-accurate and free from spelling errors.</LI>
-</UL>
-Keep in mind that engineers do not necessarily make the best localizers!
-
-<P>Once localization is complete, there are two basic types of post-translation
-testing that should be done:
-<BR>&nbsp;
-<TABLE BORDER WIDTH="100%" >
-<TR>
-<TD>Linguistic Review</TD>
-
-<TD>Checking all translations for accuracy and appropriateness in the actual
-context in which they appear.</TD>
-</TR>
-
-<TR>
-<TD>Functional Testing</TD>
-
-<TD>Ensuring the product still functions as designed (or at least as well
-as the US English product).</TD>
-</TR>
-</TABLE>
-
-
-<P>For the linguistic review, you should have an independent reviewer (i.e.
-not the person who implemented the translations) check every string for
-the items listed above.&nbsp; In some cases, it may be enough to review
-the running product itself; however, it is also valuable to print out your
-translations (using ToolCool or your own translation tools) and review
-them externally from the product.
-
-<P>For the functional testing, your best resource are the directions contained
-in the localization notes and this document. You should review the completed
-product's localization notes with this document in hand, double checking
-that you have followed all the instructions contained here and in the appropriate
-.DOG file's COMMENT field.
-
-<P>Consider the following general guidelines when testing:
-<UL>
-<LI>
-It is helpful to have a second copy of the product running with the English
-version so you can compare them side by side (a second computer might be
-helpful or required for this).</LI>
-
-<LI>
-Walk through every menu in each module you have localized looking for translation
-accuracy, pick letter conflicts and other problems.</LI>
-
-<LI>
-Bring up as many dialogs as you can, looking for translation accuracy,
-pick letter conflicts, truncated strings and functionality issues.</LI>
-
-<LI>
-Use as many of the features of the product as possible: read web pages,
-read and send mail and discussion group messages, set mail filters, search
-mail and discussion groups, create web pages using the Composer, etc. If
-functional problems are found, you should compare the same steps you took
-in the localized product to the English product: if the two products fail
-in the same way, it is a "core" bug, which can only be fixed by changing
-the core product's executable. If the localized product fails while the
-English product does not, then it is probably a translation-related bug;
-these can be fixed by altering the way you localize the product (perhaps
-by not translating a particular item, or by translating it differently).</LI>
-</UL>
-The following section tells you how to report bugs in the localization
-kit itself, or in the core product.
-<BR>&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="usingKit.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="reportingBugs.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/toc.html

@@ -1,132 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <TITLE>Table of Contents</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-Table of Contents</H2>
-
-<TABLE>
-<TR>
-<TD><FONT SIZE=+1>i. <A HREF="splash.html">Title Page</A></FONT><BR>
-<BR></TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>1. <A HREF="projectOverview.html">Project Overview</A></FONT>&nbsp;
-<UL>
-<LI>
-<A HREF="kitOverview.html">Kit Overview</A></LI>
-
-<LI>
-<A HREF="kitStruct.html">Structure and Organization</A></LI>
-
-<LI>
-<A HREF="nomenclature.html">Nomenclature and Typographical Conventions</A></LI>
-
-<BR>&nbsp;</UL>
-</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>2. <A HREF="gettingStarted.html">Getting Started</A></FONT>&nbsp;
-<UL>
-<LI>
-<A HREF="gettingStarted.html#sysreqs">System Requirements</A></LI>
-
-<LI>
-<A HREF="gettingStarted.html#install">Installing the Kit</A></LI>
-
-<LI>
-<A HREF="gettingStarted.html#configtool">Configuring Your Tools</A></LI>
-</UL>
-&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>3. <A HREF="usingKit.html">Using the Kit</A></FONT>&nbsp;
-<UL>
-<LI>
-<A HREF="usingKit.html#locdbf">Understanding the Localization Notes</A></LI>
-
-<LI>
-<A HREF="usingKit.html#l10nchecklist">Localization Checklist</A></LI>
-
-<LI>
-<A HREF="localize_these_files.html">Localize These Files</A></LI>
-
-<LI>
-<A HREF="usingKit.html#branding">Product Branding Issues</A></LI>
-
-<LI>
-<A HREF="usingKit.html#howtol10n">How to Localize Different Resource Types</A></LI>
-
-<LI>
-<A HREF="localizeURL.html">Localizing URLs</A></LI>
-
-<LI>
-<A HREF="usingKit.html#localize_stringtable">Localizing STRING TABLES</A></LI>
-
-<LI>
-<A HREF="usingKit.html#localize_menus">Localizing MENUS</A></LI>
-
-<LI>
-<A HREF="usingKit.html#localize_dialogs">Localizing DIALOGS</A></LI>
-
-<LI>
-<A HREF="usingKit.html#localize_prefs">Localizing Javascript Preferences</A></LI>
-
-<LI>
-<A HREF="usingKit.html#localize_rcdata">Localizing DATA</A></LI>
-
-<LI>
-<A HREF="usingKit.html#localize_text">Localizing External Files</A></LI>
-
-<LI>
-<A HREF="usingKit.html#localize_npnul">Localizing the NULL plugin</A></LI>
-</UL>
-&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>4. <A HREF="testKit.html">Ensuring Quality</A></FONT>
-<UL>
-<LI>
-<A HREF="testKit.html#testkit">Test Considerations</A></LI>
-
-<LI>
-<A HREF="reportingBugs.html">Reporting Bugs</A></LI>
-</UL>
-&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>5. <A HREF="troubleshooting.html">Troubleshooting</A></FONT>&nbsp;
-<UL>
-<LI>
-<A HREF="troubleshooting.html#idbuild">Using the idBuild</A></LI>
-</UL>
-&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>6. <A HREF="returnKit.html">Returning the Finished Kit</A></FONT>&nbsp;
-<BR>&nbsp;</TD>
-</TR>
-
-<TR>
-<TD><FONT SIZE=+1>7. <A HREF="reference.html">References</A></FONT>&nbsp;</TD>
-</TR>
-</TABLE>
-
-<CENTER>&nbsp;</CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/troubleshooting.html

@@ -1,125 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Troubleshooting</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<H2>
-<A NAME="troubleshooting"></A>5. Troubleshooting</H2>
-This section discusses tools and tips for diagnosing, correcting or avoiding
-problems encountered using this localization kit.
-<H3>
-<A NAME="idbuild"></A>Using the idBuild</H3>
-A special build of the US English product is provided with this kit, called
-the idBuild.&nbsp; This version of the product is designed to help you
-locate where specific strings are coming from within the resources.&nbsp;
-It does this by prepending to the resource string (putting in front) a
-token representing the resource ID.&nbsp; The token will be in the following
-form:
-<UL>
-<LI>
-an initial letter, either M, D or S, which stands for MENU, DIALOG or STRINGTABLE.&nbsp;
-(RCDATA is ignored.)</LI>
-
-<LI>
-the resource's numeric id</LI>
-
-<LI>
-for Menus and Dialogs, a dash followed by the Item number</LI>
-
-
-<P>Example: D2298-3 = DIALOG2298Item3</UL>
-This knowledge can help expand upon the information provided in the localization
-notes by giving you the actual context in which a specific string appears.&nbsp;
-It can also help you locate problematic issues, such as STRINGTABLE resources
-being used in menus, concatenated strings, etc.
-
-<P>NOTE: the idBuild is provided "AS IS" with no guarantees as to functionality,
-stability or fitness for any purpose.&nbsp; It may crash, or some features
-may not work due to the unexpected way in which the resources have been
-modified.&nbsp; Use it at your own risk.
-
-<P><B>To use the idBuild:</B>
-<BR>&nbsp;
-<UL>
-<LI>
-Install the current version of Communicator (4.03 as of this writing)</LI>
-
-<LI>
-Make backup copies of the 8 resource binaries listed in the<A HREF="#localize_these_files">
-table above</A>.&nbsp; Store these copies somewhere safe.</LI>
-
-<LI>
-Copy the 8 resource binaries provided in the <B><TT><I>kitRoot\</I>products\client\windows\32bit\en\nav40\program\idBuild
-</TT></B>directory to the installed version's <B><TT>Program</TT></B> directory
-(replacing the originals).</LI>
-
-<LI>
-Start the program as usual.</LI>
-</UL>
-What you will see will be the modified Communicator, with resource IDs
-visible next to the actual English strings.&nbsp; In some cases, you might
-not be able to see the entire string because of the increased string length.&nbsp;
-If absolutely necessary, you can modify the idBuild's binaries using MSDEV
-to produce a more useful version, or you may simply inspect the strings
-you can't fully see at runtime.
-
-<P><FONT SIZE=-1>idBuild Main Menu</FONT>
-<BR><IMG SRC="idBuild.jpg" BORDER=1 HEIGHT=366 WIDTH=673>
-
-<P>In the image above, you can see the Communicator's main menu and the
-toolbar buttons displayed with attached resource IDs. Note how most of
-the menu items begin with "M", telling you they are standard menu resources.&nbsp;
-However, a few begin "S", indicating they come from the STRINGTABLE resources.&nbsp;
-These require special attention when assigning pickletters.
-
-<P>If you see a string in the product itself (not a web page being displayed)
-that does not have a resource ID attached, there are 4 possibilities as
-it's origin:
-
-<P>1. It is part of a multipart string.&nbsp; For example, the toolbar
-buttons are made up of strings with 3 components, each separated by newline
-characters (<TT>\n</TT> ).&nbsp; The first part is the status bar message;
-this will have the resource ID.&nbsp; The second and third components are
-the ToolTip (pop-up help message) and the button label itself.&nbsp; These
-won't show the resource ID because it is prepended to the first part.
-
-<P>2. The string comes from an RCDATA resource.&nbsp; For example, the
-Help menu contains a number of entries that come from CONFIG_PREFS.&nbsp;
-These are not touched by the idBuild generation process.
-
-<P>3. The string comes from an external source.&nbsp; For example, the
-idBuild doesn't contain the MFC resources, so any strings coming from MFC42.dll
-will be in there original form.
-
-<P>4. The string is hard coded in the Netscape binary.&nbsp; There are
-still several strings that have not been resourced (for example, the Java
-Console is entirely hard coded).&nbsp; You will not be able to localize
-these for this version.
-<BR>&nbsp;
-<BR>&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="testKit.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="returnKit.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER>&nbsp;<BR>
-<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape Communications
-Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/usingKit.html

@@ -1,432 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="Rick Elliott">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Using the Kit</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<DIV ALIGN=right>&nbsp;</DIV>
-&nbsp;
-<TABLE COLS=1 WIDTH="100%" >
-<TR>
-<TD>
-<CENTER><B><FONT COLOR="#FF0000">WARNING! Protect yourself from data loss
-by making regular backups of your work.</FONT></B></CENTER>
-</TD>
-</TR>
-</TABLE>
-
-<H2>
-<A NAME="usekit"></A>3. Using the Kit</H2>
-Once your copy of the Windows Front End Localization Kit is correctly installed,
-you may begin your localization work by following the instructions in the
-remainder of this document. The next section discusses the contents of
-the localization notes provided with this kit.&nbsp; It is important that
-you work properly with the instructions contained in these files or the
-localized product you create may not function.
-<H3>
-<A NAME="locdbf"></A>Understanding the Localization Notes</H3>
-Each binary file to be localized has an associated localization notes file,
-called a "DOG" file.&nbsp; These files are created by the Netscape translation
-tool, ToolCool. For a complete description of the process used to create
-these files, please consult the <B>Netscape Translation Tool User's Guide
-</B>that comes with those tools. It is very important that you work properly
-with these localization notes, as they contain the bulk of the instructions
-for this project. Most importantly, the .DOG files identify the "forbidden"
-resources - those resources that you must not change.
-
-<P>Each DOG file associated with a. dll or .exe has the same name as the
-binary file, but will have the extension .DOG.
-<UL>E.g. <B><TT>RESDLL.DLL</TT></B> has an associated <B><TT>RESDLL.DOG</TT></B></UL>
-The .DOG file lists certain information about each resource contained in
-the associated binary file; :
-<PRE>Field Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Purpose
-FILENAME&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Not used.
-IDENTIFIER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Resource ID.
-US_STR&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Original English string.
-XL_STR&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Target translated string.
-COMMENT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Localization notes for translator.
-REASON&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Explanation of leveraging results.
-TRANSLATE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Resource is forbidden from translation if this is "FALSE"</PRE>
-Resource IDs are made up of a combination of the resource type and a unique
-identifier, depending on the type of resource.&nbsp; See the individual
-sections dealing with each resource type for a description of how resources
-are identified. You must not change the contents of this field.
-
-<P>The original English string is what you need to translate; however,
-your translation must go in the XL_STR field. It is not useful to change
-the contents of the US_STR field.
-
-<P>Your translation will be done in the XL_STR field. If there is no leveraged
-translation from a prior version, this string will originally match the
-US_STR value.
-
-<P>If a resource requires some extra explanation, this can be found in
-the COMMENT field.
-
-<P>The REASON field indicates the results of the leveraging process which
-created the database, which in turn was used to generate the .DOG file.
-Unless you are using the Netscape translation tools, this field is not
-useful to you.
-
-<P>The TRANSLATE field dictates whether or not you can change the value
-of the XL_STR field. If this field is blank, the resource is OK to translate;
-if the value is "FALSE", you must not translate it. (When viewed through
-ToolCool, this field appears as a check box. When checked, you may translate
-this resource; when unchecked, you may not.)
-
-<P>The next section presents the basic localization process as a checklist.
-<CENTER>
-<HR WIDTH="50%"></CENTER>
-
-<H3>
-<A NAME="l10nchecklist"></A>Localization Checklist</H3>
-The basic localization process is this:
-
-<P><B>1. Create your working directories</B>
-<BR>Copy the English directory (<B><TT>kitRoot\products\client\windows\<I>platform</I>\en</TT></B>)
-to a new directory at the same level.&nbsp; Be sure to use the appropriate
-naming convention for your new directory.&nbsp; This is the ISO 639:1988
-standard (<I>Code for the representation of names of languages</I>).&nbsp;
-A sub-set of these codes can be found in the accompanying <A HREF="isocodes.htm">table</A>.&nbsp;
-You can go <A HREF="http://www.indigo.ie/egt/standards/iso639/iso639-1-en.html">here</A>
-for a complete listing of the standard.
-
-<P><B>2. Identify files to localize</B>
-<BR>Consult the <A HREF="localize_these_files.html#table1">Localize These
-Files</A> page to learn which binary files contain localizable resources.
-
-<P>For each file to be localized, follow these steps using the tool of
-your choice, being careful to follow all instructions contained in the
-Localization Notes for that resource.:
-<UL>
-<LI>
-Localize the STRINGTABLE resources</LI>
-
-<LI>
-Localize the MENU resources</LI>
-
-<LI>
-Localize the DIALOG resources</LI>
-
-<LI>
-Localize the Javascript preferences stored in DATA resources (<TT>RESDLL.DLL</TT>
-only)</LI>
-
-<LI>
-Localize the remaining DATA resources (<TT>RESDLL.DLL</TT> only)</LI>
-</UL>
-<B>3. Localize external files</B>
-<BR>In addition to the binary resource modules requiring localization,
-there are a number of external files which <I>may </I>need to be localized<SUP><FONT SIZE=-1><A HREF="#fn1">1<A NAME="fn1_source"></A></A></FONT></SUP>:
-these are listed in the <A HREF="localize_these_files.html#table2">Localize
-These Files</A> page. Further instructions can be found there.
-
-<P><B>4. Complete post-translation processing</B>
-<BR>After translation is complete, you need to test your work and deal
-with any problems:
-<UL>
-<LI>
-Test the localized product.</LI>
-
-<LI>
-Fix translation bugs using your localization tools or a resource editor.</LI>
-
-<LI>
-Fix dialog size bugs using your localization tools or a resource editor.</LI>
-
-<LI>
-Report core bugs to Netscape.</LI>
-</UL>
-<B>5. Return kits (optional)</B>
-<BR>Finally, you may be required to deliver files back to Netscape:
-<UL>
-<LI>
-Return the necessary files to Netscape (if required).</LI>
-
-<LI>
-Inform us that the localized files have been returned (if required).</LI>
-</UL>
-
-<HR WIDTH="50%">
-<H2>
-<A NAME="branding"></A>Product Branding Issues</H2>
-If you are using this kit under the auspices of the Unlimited Localization
-Program, you must remove or replace Netscape trademarked strings, images
-and icons in your localized version. Click <A HREF="branding.html">here</A>
-for instructions.
-
-<P>
-<HR WIDTH="50%">
-<H2>
-<A NAME="howtol10n"></A>How to Localize Different Resource Types</H2>
-This section provides you with general information about localizing the
-various resource types and files found with this kit.&nbsp; (Remember,
-specific localization notes for binary resources is found in the associated
-.DOG file.)
-<H3>
-<A NAME="localizeURLs"></A>Localizing URLs</H3>
-
-<UL>Many resources of all types in the Communicator contain Internet addresses
-in the form of URLs (Universal Resource Locators). Because many of these
-URLs originally point to locations within the Netscape domain, how they
-are localized depends on whether you are creating a branded Netscape version
-or not.&nbsp; The rules for how to handle URLs are found <A HREF="localizeURL.html">here</A>.</UL>
-
-<H3>
-<A NAME="localize_stringtable"></A>Localizing String Tables</H3>
-
-<UL>STRINGTABLE resources are the most sensitive, potentially problematic
-resource type you will be working with. Therefore, you must pay close attention
-to the instructions provided in the localization notes.
-<H4>
-<A NAME="locnote_stringtable"></A>Localization Notes</H4>
-String table resources are identified by the word STRINGTABLE, followed
-by the numeric resource ID generated from the project's header files.&nbsp;
-For example, in the file BRPREF32.DLL, STRINGTABLE109 contains the label
-and explanatory text for the Languages pane of the preference dialog.&nbsp;
-Localization notes for string table resources are provided in the comments
-field for each resource contained in the associated .DOG file. Please pay
-special attention to these notes and to the TRANSLATE field. In general,
-be aware of the following:
-<BR>&nbsp;
-<UL>
-<LI>
-Many strings contain C++ print format strings, such as %s, %ld, %lu, etc.&nbsp;
-Do not modify these while translating the rest of the string.</LI>
-
-<LI>
-Many strings contain new line characters: \n.&nbsp; In general, you should
-try leave these as you find them.&nbsp; In some cases, the new line is
-used to delimit a matched set of strings used to build a button label,
-a ToolTip and a status bar message all relating to single control. In these
-cases, you must preserve the new line characters.</LI>
-
-<LI>
-Many strings actually show up as part of an HTML or Javascript document
-or dialog.&nbsp; Be careful not to break format tags, like &lt;TITLE>,
-&lt;FONT>, etc. by translating these.</LI>
-</UL>
-</UL>
-
-<H3>
-<A NAME="localize_menus"></A>Localizing Menus</H3>
-
-<UL>Menu translation is usually not as tricky as localizing string tables;
-however, you should take care to assign unique pickletters to menu choices.&nbsp;
-This process can be made difficult by the fact that some strings that appear
-in menus at runtime actually come from string tables.&nbsp; The special
-ID Build provided in this kit can help you find these.
-<H4>
-<A NAME="locnote_menus"></A>Localization Notes</H4>
-Menu resources are identified first by the word MENU, then by a resource
-number, then by a sequential Item number. For example, in RESDLL.DLL, MENU2ITEM0
-contains the word "&amp;File". This resource is the first item in menu
-structure structure #2 (the File menu).&nbsp; The ampersand character (&amp;)
-denotes the pickletter is the letter "F".&nbsp; Localization notes for
-individual MENU resource items are provided in the comments field for that
-item in the localization databases. Not all MENU resource items need to
-be translated so again, please pay special attention to these notes and
-to the TRANSLATE field!</UL>
-
-<H3>
-<A NAME="localize_dialogs"></A>Localizing Dialogs</H3>
-
-<UL>Dialog translation is usually not as tricky as localizing string tables;
-however, you should take care to assign unique pickletters to dialog controls.&nbsp;
-This process can be made difficult by the fact that some strings that appear
-in menus and dialogs at runtime actually come from string tables.&nbsp;
-The special ID Build provided in this kit can help you find these. Once
-a DIALOG resource has been translated, the dialog may need to be resized
-using a visual resource editor, such as MSDEV (Microsoft<SUP><FONT SIZE=-1>&reg;</FONT></SUP>
-Visual C++ 4.0 or greater) or Borland<SUP><FONT SIZE=-1>&reg;</FONT></SUP>
-Resource Workshop.
-<H4>
-<A NAME="locnote_menus"></A>Localization Notes</H4>
-Dialog resources are identified first by the word DIALOG , then by a resource
-number, then by a sequential Item number. For example, in NSMAILUI.DLL,
-DIALOG129Item0 contains the word "Password". This resource is the first
-item (the dialog title) in DIALOG129. Localization notes for individual
-DIALOG resource items are provided in the comments field for that item
-in the localization databases. Not all DIALOG resource items need to be
-translated so again, please pay special attention to these notes and to
-the TRANSLATE field!</UL>
-
-<UL><B>A special note on Dialog fonts</B>:
-<BR>The second item in each dialog definition (e.g. DIALOGnnnITEM1) is
-the font information for that dialog.&nbsp; If you find it necessary to
-change the font name or size, be aware of the following fact: the font
-size is represented in the translation database by the ASCII character
-corresponding to that size.&nbsp; In the US product the default font size
-is 9, which appears as a Horizontal Tab (Font size = 9 = ASCII character
-9 = tab).&nbsp; In the database, this will appear as an unprintable character,
-such as a black box.&nbsp; There are two concerns here: first, if you change
-the font name, be careful not to accidentally delete the tab character.&nbsp;
-Second, if you decide to change the font size, you can do so by substituting
-the appropriate ASCII character which matches the new size you want.&nbsp;
-For example, to change the font size to 10, replace the tab with a Line
-Feed character (ASCII 10).&nbsp; This is rather confusing, so it is probably
-best to avoid changing the fonts if possible.</UL>
-
-<H3>
-<A NAME="localize_prefs"></A>Localizing Javascript Preferences</H3>
-
-<UL>Javascript is used to define default preference information for the
-Communicator and it's components.&nbsp; These preferences end up stored
-in the DATA section of RESDLL.DLL. You can use the ToolCool to edit these
-just as you would STRINGTABLE resources, or use your preferred localization
-tools.
-
-<P>There are two groups of localizable Javascript preferences: ALL_PREFS
-and CONFIG_PREFS.&nbsp; Most of these preference settings are not localizable;
-these are marked as forbidden in the localization notes.&nbsp; Those that
-are localizable should be treated very carefully, as Javascript is rather
-particular about the format of the data it receives.&nbsp; Pay special
-attention not to unbalance quotes, delete the preceding tab characters,
-etc.</UL>
-
-<UL>
-<H4>
-<A NAME="locnote_allprefs"></A>Localization Notes for ALL_PREFS</H4>
-The entries in the ALL_PREFS section contain the default values for certain
-cross-platform preferences, including some crucial for the correct operation
-of localized versions.&nbsp; The rules for how to handle this section are
-found <A HREF="localizeAllPref.html">here</A>.
-<H4>
-<A NAME="locnote_configprefs"></A>Localization Notes for CONFIG_PREFS</H4>
-The entries in the CONFIG_PREFS section make up the configurable Toolbar
-and Help menu items and their functions.&nbsp; How they are localized depends
-on whether you are creating a branded Netscape version or not.&nbsp; The
-rules for how to handle this section are found <A HREF="localizeConfigPref.html">here</A>.</UL>
-
-<H3>
-<A NAME="localize_rcdata"></A>Localizing DATA</H3>
-
-<UL>There are several additional resources stored as DATA that cannot be
-edited using ToolCool.&nbsp; Therefore, you must use a resource editor
-and a text editor to localize these by following this procedure.&nbsp;
-(This example uses Microsoft<SUP><FONT SIZE=-1>&reg;</FONT></SUP> MSDEV;
-if you prefer a different resource editor you may need to execute slightly
-different steps).</UL>
-
-<UL>
-<UL>
-<LI>
-Open the file containing the DATA resources (usually RESDLL.DLL)</LI>
-
-<LI>
-Expand the DATA resource type.</LI>
-
-<LI>
-Select the resource you want to localize</LI>
-
-<LI>
-Choose <B><TT>Edit | Select All.</TT></B></LI>
-
-<LI>
-Choose <B><TT>Edit | Copy</TT></B>.</LI>
-
-<LI>
-Open a text editor window by clicking on the new document icon (or if you
-prefer, you may use any other text editor).</LI>
-
-<LI>
-Choose <B><TT>Edit | Paste</TT></B>.</LI>
-
-<LI>
-You should now have the text representation of the DATA resource in your
-text editor window. You may localize it according to the instructions in
-the Localization Notes section for each DATA resource.</LI>
-
-<LI>
-When done, save your work, then select ALL the text (use Edit | Select
-All if your editor supports this).</LI>
-
-<LI>
-Choose <B><TT>Edit | Copy</TT></B>.</LI>
-
-<LI>
-Go back to the RESDLL.DLL in MSDEV and select the DATA resource you have
-translated.</LI>
-
-<LI>
-Choose <B><TT>Edit | Select All</TT></B>.</LI>
-
-<LI>
-Choose <B><TT>Edit | Paste</TT></B>.</LI>
-
-<LI>
-You should now see the original English DATA resource replaced by your
-translated version.</LI>
-
-<LI>
-<FONT COLOR="#FF0000"><BLINK>IMPORTANT</BLINK>:</FONT> Go to the end of
-the resource and insert a NULL value by typing the number zero (0) in the
-first empty byte position.</LI>
-
-<LI>
-Close the resource and save your work.</LI>
-</UL>
-</UL>
-
-<UL>Consult the <A HREF="localize_these_files.html#table3">Localize These
-Files</A> to see the list of DATA resources that require localization:</UL>
-
-<H3>
-<A NAME="localize_text"></A>Localizing External Files</H3>
-
-<UL>As mentioned above, you may choose (or be required) to translate several
-external files.&nbsp; If this is the case, the links contained in the text
-file section of <A HREF="localize_these_files.html#table2">Localize These
-Files</A> will tell you what to do. (Note: this may be nothing at all).</UL>
-
-<H3>
-<A NAME="localize_npnul"></A>Localizing the NULL Plugin</H3>
-
-<UL>The so-called "NULL" plugin is the default plugin that ships with all
-versions of the Communicator.&nbsp; It's job is to list the plugins that
-you have installed, and if you don't have a requested plugin, to help you
-get it.
-
-<P>The name and location of the NULL plugin is given in the <A HREF="localize_these_files.html#table2">Localize
-These Files</A> binary file section. Localization notes have been provided
-for you to use when localizing the resources for this file.&nbsp; Instructions
-for individual resources can be found in the COMMENT field of the matching
-.DOG file.
-
-<P>
-<HR WIDTH="50%"></UL>
-
-<H2>
-<A NAME="notes"></A>Notes</H2>
-
-<UL><A NAME="fn1"></A>1. Whether or not you have to incorporate or create
-localized version of these files depends on your agreement with Netscape,
-if any; or if localization is occurring as part of the Universal Localization
-Program, upon your desire to perform this work.[<A HREF="usingKit.html#fn1_source">BACK]</A></UL>
-&nbsp;
-<CENTER><TABLE COLS=3 WIDTH="50%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="gettingStarted.html">BACK</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="testKit.html">NEXT</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="toc.html">CONTENTS</A>]</CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER></CENTER>
-
-<CENTER><FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright Netscape
-Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/windows/docs/nav40/xpencui.htm

@@ -1,215 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="Author" CONTENT="test">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Cross-Product Encoding UI Names</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-
-<CENTER>
-<H3>
-<B>Cross-Product Encoding UI Names</B></H3></CENTER>
-
-<CENTER><B><FONT COLOR="#F8060C">Uppercase and lowercase are treated distinctly</FONT></B></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<TABLE BORDER=4 CELLSPACING=4 CELLPADDING=4 WIDTH="100%" >
-<TR>
-<TH NOWRAP WIDTH="33%"><FONT SIZE=+2>UNIX</FONT></TH>
-
-<TH NOWRAP WIDTH="33%"><FONT SIZE=+2>Windows</FONT></TH>
-
-<TH NOWRAP><FONT SIZE=+2>Macintosh</FONT></TH>
-</TR>
-
-<TR VALIGN=TOP>
-<TD>Western (ISO-8859-1)&nbsp;
-<BR>Western (Windows-1252)&nbsp;
-<HR WIDTH="100%">Central European (ISO-8859-2)&nbsp;
-<BR>Central European (Windows-1250)&nbsp;
-<HR WIDTH="100%">Japanese (Auto-Detect)&nbsp;
-<BR>Japanese (Shift_JIS)&nbsp;
-<BR>Japanese (EUC-JP)&nbsp;
-<BR>Japanese (ISO-2022-JP)&nbsp;
-<HR WIDTH="100%">Traditional Chinese (Big5)&nbsp;
-<BR>Traditional Chinese (EUC-TW)&nbsp;
-<HR WIDTH="100%">Simplified Chinese (GB2312)&nbsp;
-<BR>Simplified Chinese (HZ)&nbsp;
-<HR WIDTH="100%">Korean (Auto-Detect)&nbsp;
-<BR>Korean (EUC-KR)&nbsp;
-<BR>Korean (ISO-2022-KR)&nbsp;
-<HR WIDTH="100%">Cyrillic (KOI8-R)&nbsp;
-<BR>Cyrillic (ISO-8859-5)&nbsp;
-<BR>Cyrillic (Windows-1251)&nbsp;
-<HR WIDTH="100%">Greek (ISO-8859-7)&nbsp;
-<BR>Greek (Windows-1253)&nbsp;
-<HR WIDTH="100%">Turkish (ISO-8859-9)&nbsp;
-<HR WIDTH="100%">Unicode (UTF-8)&nbsp;
-<BR>Unicode (UCS-2)&nbsp;
-<BR>Unicode (UTF-7)&nbsp;
-<HR WIDTH="100%">User-Defined&nbsp;
-<HR WIDTH="100%"></TD>
-
-<TD>Western (ISO-8859-1)&nbsp;
-<BR>Western (Windows-1252)&nbsp;
-<HR WIDTH="100%">Central European (ISO-8859-2)&nbsp;
-<BR>Central European (Windows-1250)&nbsp;
-<HR WIDTH="100%">Japanese (Auto-Detect)&nbsp;
-<BR>Japanese (Shift_JIS)&nbsp;
-<BR>Japanese (EUC-JP)&nbsp;
-<BR>Japanese (ISO-2022-JP)&nbsp;
-<HR WIDTH="100%">Traditional Chinese (Big5)&nbsp;
-<BR>Traditional Chinese (EUC-TW)&nbsp;
-<HR WIDTH="100%">Simplified Chinese (GB2312)&nbsp;
-<BR>Simplified Chinese (HZ)&nbsp;
-<HR WIDTH="100%">Korean (Auto-Detect)&nbsp;
-<BR>Korean (EUC-KR)&nbsp;
-<BR>Korean (ISO-2022-KR)&nbsp;
-<HR WIDTH="100%">Cyrillic (KOI8-R)&nbsp;
-<BR>Cyrillic (ISO-8859-5)&nbsp;
-<BR>Cyrillic (Windows-1251)&nbsp;
-<HR WIDTH="100%">Greek (ISO-8859-7)&nbsp;
-<BR>Greek (Windows-1253)&nbsp;
-<HR WIDTH="100%">Turkish (ISO-8859-9)&nbsp;
-<HR WIDTH="100%">Unicode (UTF-8)&nbsp;
-<BR>Unicode (UCS-2)&nbsp;
-<BR>Unicode (UTF-7)&nbsp;
-<HR WIDTH="100%">User-Defined&nbsp;
-<HR WIDTH="100%"></TD>
-
-<TD>Western (ISO-8859-1)&nbsp;
-<BR>Western (MacRoman)&nbsp;
-<BR>Western (Windows-1252)&nbsp;
-<HR WIDTH="100%">Central European (ISO-8859-2)&nbsp;
-<BR>Central European (Windows -1250)&nbsp;
-<BR>Central European (MacCE)&nbsp;
-<HR WIDTH="100%">Japanese (Auto-Detect)&nbsp;
-<BR>Japanese (Shift_JIS)&nbsp;
-<BR>Japanese (EUC-JP)&nbsp;
-<BR>Japanese (ISO-2022-JP)&nbsp;
-<HR WIDTH="100%">Traditional Chinese (Big5)&nbsp;
-<BR>Traditional Chinese (EUC-TW)&nbsp;
-<HR WIDTH="100%">Simplified Chinese (GB2312)&nbsp;
-<BR>Simplified Chinese (HZ)&nbsp;
-<HR WIDTH="100%">Korean (Auto-Detect)&nbsp;
-<BR>Korean (EUC-KR)&nbsp;
-<BR>Korean (ISO-2022-KR)&nbsp;
-<HR WIDTH="100%">Cyrillic (KOI8-R)&nbsp;
-<BR>Cyrillic (ISO-8859-5)&nbsp;
-<BR>Cyrillic (Windows-1251)&nbsp;
-<BR>Cyrillic (MacCyrillic)&nbsp;
-<HR WIDTH="100%">Greek (ISO-8859-7)&nbsp;
-<BR>Greek (Windows-1253)&nbsp;
-<BR>Greek (MacGreek)&nbsp;
-<HR WIDTH="100%">Turkish (ISO-8859-9)&nbsp;
-<BR>Turkish (MacTurkish)&nbsp;
-<HR WIDTH="100%">Unicode (UTF-8)&nbsp;
-<BR>Unicode (UCS-2)&nbsp;
-<BR>Unicode (UTF-7)&nbsp;
-<HR WIDTH="100%">User-Defined&nbsp;
-<HR WIDTH="100%"></TD>
-</TR>
-</TABLE>
-
-<HR WIDTH="100%">
-<CENTER>
-<H3>
-<B>Cross-Product Encoding Names to be Transmitted</B></H3></CENTER>
-
-<CENTER><B><FONT COLOR="#F5090C">Uppercase and lowercase are not distinct</FONT></B></CENTER>
-
-<CENTER>&nbsp;</CENTER>
-
-<TABLE BORDER=4 CELLSPACING=4 CELLPADDING=4 WIDTH="100%" >
-<TR>
-<TH NOWRAP WIDTH="33%"><FONT SIZE=+2>UNIX</FONT></TH>
-
-<TH NOWRAP WIDTH="33%"><FONT SIZE=+2>Windows</FONT></TH>
-
-<TH NOWRAP><FONT SIZE=+2>Macintosh</FONT></TH>
-</TR>
-
-<TR VALIGN=TOP>
-<TD>Western (ISO-8859-1)&nbsp;
-<HR WIDTH="100%">Central European (ISO-8859-2)&nbsp;
-<BR>Central European (Windows-1250)&nbsp;
-<HR WIDTH="100%">Japanese (Shift_JIS)&nbsp;
-<BR>Japanese (EUC-JP)&nbsp;
-<BR>Japanese (ISO-2022-JP)&nbsp;
-<HR WIDTH="100%">Traditional Chinese (Big5)&nbsp;
-<BR>Traditional Chinese (x-EUC-TW)&nbsp;
-<HR WIDTH="100%">Simplified Chinese (GB2312)&nbsp;
-<BR>Simplified Chinese (HZ-GB-2312)&nbsp;
-<HR WIDTH="100%">Korean (EUC-KR)&nbsp;
-<BR>Korean (ISO-2022-KR)&nbsp;
-<HR WIDTH="100%">Cyrillic (KOI8-R)&nbsp;
-<BR>Cyrillic (ISO-8859-5)&nbsp;
-<BR>Cyrillic (Windows-1251)&nbsp;
-<HR WIDTH="100%">Greek (ISO-8859-7)&nbsp;
-<BR>Greek (Windows-1253)&nbsp;
-<HR WIDTH="100%">Turkish (ISO-8859-9)&nbsp;
-<HR WIDTH="100%">Unicode (UTF-8)&nbsp;
-<BR>Unicode (ISO-10646-UCS-2)&nbsp;
-<BR>Unicode (UNICODE-1-1-UTF-7)&nbsp;
-<HR WIDTH="100%"></TD>
-
-<TD>Western (ISO-8859-1)&nbsp;
-<HR WIDTH="100%">Central European (ISO-8859-2)&nbsp;
-<BR>Central European (Windows-1250)&nbsp;
-<HR WIDTH="100%">Japanese (Shift_JIS)&nbsp;
-<BR>Japanese (EUC-JP)&nbsp;
-<BR>Japanese (ISO-2022-JP)&nbsp;
-<HR WIDTH="100%">Traditional Chinese (Big5)&nbsp;
-<BR>Traditional Chinese (x-EUC-TW)&nbsp;
-<HR WIDTH="100%">Simplified Chinese (GB2312)&nbsp;
-<BR>Simplified Chinese (HZ-GB-2312)&nbsp;
-<HR WIDTH="100%">Korean (EUC-KR)&nbsp;
-<BR>Korean (ISO-2022-KR)&nbsp;
-<HR WIDTH="100%">Cyrillic (KOI8-R)&nbsp;
-<BR>Cyrillic (ISO-8859-5)&nbsp;
-<BR>Cyrillic (Windows-1251)&nbsp;
-<HR WIDTH="100%">Greek (ISO-8859-7)&nbsp;
-<BR>Greek (Windows-1253)&nbsp;
-<HR WIDTH="100%">Turkish (ISO-8859-9)&nbsp;
-<HR WIDTH="100%">Unicode (UTF-8)&nbsp;
-<BR>Unicode (ISO-10646-UCS-2)&nbsp;
-<BR>Unicode (UNICODE-1-1-UTF-7)&nbsp;
-<HR WIDTH="100%"></TD>
-
-<TD>Western (ISO-8859-1)&nbsp;
-<BR>Western (x-MacRoman)&nbsp;
-<HR WIDTH="100%">Central European (ISO-8859-2)&nbsp;
-<BR>Central European (Windows-1250)&nbsp;
-<BR>Central European (x-MacCE)&nbsp;
-<HR WIDTH="100%">Japanese (Shift_JIS)&nbsp;
-<BR>Japanese (EUC-JP)&nbsp;
-<BR>Japanese (ISO-2022-JP)&nbsp;
-<HR WIDTH="100%">Traditional Chinese (Big5)&nbsp;
-<BR>Traditional Chinese (x-EUC-TW)&nbsp;
-<HR WIDTH="100%">Simplified Chinese (GB2312)&nbsp;
-<BR>Simplified Chinese (HZ-GB-2312)&nbsp;
-<HR WIDTH="100%">Korean (EUC-KR)&nbsp;
-<BR>Korean (ISO-2022-KR)&nbsp;
-<HR WIDTH="100%">Cyrillic (KOI8-R)&nbsp;
-<BR>Cyrillic (ISO-8859-5)&nbsp;
-<BR>Cyrillic (Windows-1251)&nbsp;
-<BR>Cyrillic (x-MacCyrillic)&nbsp;
-<HR WIDTH="100%">Greek (ISO-8859-7)&nbsp;
-<BR>Greek (Windows-1253)&nbsp;
-<BR>Greek (x-MacGreek)&nbsp;
-<HR WIDTH="100%">Turkish (ISO-8859-9)&nbsp;
-<BR>Turkish (x-MacTurkish)&nbsp;
-<HR WIDTH="100%">Unicode (UTF-8)&nbsp;
-<BR>Unicode (ISO-10646-UCS-2)&nbsp;
-<BR>Unicode (UNICODE-1-1-UTF-7)&nbsp;
-<HR WIDTH="100%"></TD>
-</TR>
-</TABLE>
-&nbsp;
-<CENTER>&nbsp;<FONT FACE="Arial, Helvetica"><FONT SIZE=-2>1998, Copyright
-Netscape Communications Corp. All Rights Reserved</FONT></FONT></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/xp/docs/mozilla.org/kitDownload.html

@@ -1,118 +0,0 @@
-<HTML>
-<HEAD>
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (Win95; I) [Netscape]">
-   <TITLE>Download L10n Kits</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-<B><FONT COLOR="#008080">Download Your Localization Kit</FONT></B>
-
-<P>Make your selections from the links below. If the Localization kit for
-the product or operating system you need is not shown list, we aren't supporting
-freely downloadable localization kits for that product or platform (yet).
-Kits have been broken into separate components for faster downloads.
-
-<P><B>Before downloading any localization kit, please read the <A HREF="ulpLicense.html">License
-Agreement</A>! </B>By downloading and using any of the information,
-software or tools linked from this page, you affirm that you have read
-this Agreement and agree to abide by the terms and conditions contained
-therein.
-<P>
-
-<TABLE WIDTH="75%" >
-<TR BGCOLOR="#3366FF">
-<TD><B><FONT SIZE=+1>Windows (NT)</B></FONT></TD>
-
-<TD><CENTER>Description</CENTER></TD>
-</TR>
-
-<TR VALIGN=TOP>
-<TD VALIGN=TOP><A HREF="ftp://ftp.mozilla.org/pub/l10n-kits/win32kit.zip">win32Kit.zip</A></TD>
-
-<TD>32 bit Localization Notes - version 4.03. Contains translation databases
-in binary (.dbf) and text (.dog) format.</TD>
-</TR>
-
-<TR VALIGN=TOP>
-<TD><A HREF="ftp://ftp.mozilla.org/pub/l10n-kits/winDocs.zip">winDocs.zip</A></TD>
-
-<TD>Windows Localization Kit Documentation. Contains .HTML documentation
-(identical to the <A HREF="http://www.mozilla.org/docs/l10n/l10nkits/client/windows/docs/nav40/splash.html">on-line
-version</A>).</TD>
-</TR>
-
-<TR VALIGN=TOP>
-<TD><A HREF="ftp://ftp.mozilla.org/pub/l10n-kits/nstool.exe">nstools.exe</A></TD>
-
-<TD>Windows Translation Tools. A self-extracting installer for ToolCool
-and DogLev. Includes documentation.</TD>
-</TR>
-
-<TR VALIGN=TOP>
-<TD><A HREF="ftp://ftp.mozilla.org/pub/l10n-kits/win32bits.zip">win32Bits.zip</A></TD>
-
-<TD>32 bit English export binaries - version 4.03. Contains the localizable
-resources matching the most recent localization notes.</TD>
-</TR>
-
-<TR BGCOLOR="#33CCFF">
-<TD><B>Installer</B></TD>
-
-<TD><CENTER>Description</CENTER></TD>
-</TR>
-
-<TR>
-<TD><A HREF="ftp://ftp.mozilla.org/pub/l10n-kits/winInstDocs.zip">winInstDocs.zip</A></TD>
-
-<TD>Windows Installer Localization Kit Documentation. Contains .HTML documentation
-(identical to the <A HREF="http://www.mozilla.org/docs/l10n/l10nkits/client/windows/docs/installer/splash.html">on-line
-version</A>).</TD>
-</TR>
-
-<TR>
-<TD><A HREF="ftp://ftp.mozilla.org/pub/l10n-kits/C32E403.EXE">C32E403.EXE</A></TD>
-
-<TD>Windows 32 bit English export installer, complete version.</TD>
-</TR>
-</TABLE>
-
-<P>
-<CENTER>
-<HR width="612" NOSHADE SIZE=2></CENTER>
-
-<CENTER><TABLE CELLSPACING=0 CELLPADDING=3 >
-<TR>
-<TD></TD>
-
-<TD><B>A<FONT SIZE=-1>DDITIONAL</FONT> I<FONT SIZE=-1>NFORMATION</FONT></B></TD>
-</TR>
-
-<TR>
-<TD ALIGN=RIGHT><B><FONT SIZE=-1>Program Terms:</FONT></B></TD>
-
-<TD><FONT SIZE=-1><A HREF="ulpLicense.html" TARGET="_top">Universal Localization
-Program License</A></FONT></TD>
-</TR>
-
-<TR>
-<TD ALIGN=RIGHT><B><FONT SIZE=-1>Product Info:</FONT></B></TD>
-
-<TD><FONT SIZE=-1><A HREF="l10nkitintro.html" TARGET="_top">Overview of
-Localization Kits</A> | <A HREF="ulpFAQ.html" TARGET="_top">FAQ</A></FONT></TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER><TABLE CELLSPACING=0 CELLPADDING=3 WIDTH="612" >
-<TR>
-<TD WIDTH="612">
-<CENTER>
-<HR width="612" NOSHADE SIZE=2></CENTER>
-
-<CENTER><FONT SIZE=-1><A HREF="http://home.netscape.com/misc/trademarks.html" TARGET="_top">Copyright</A>
-&copy; 1998 <A HREF="http://home.netscape.com/misc/contact_info.html" TARGET="_top">Netscape
-Communications Corporation</A></FONT></CENTER>
-</TD>
-</TR>
-</TABLE></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/xp/docs/mozilla.org/l10nLibrary.html

@@ -1,58 +0,0 @@
-<HTML>
-<HEAD>
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliot">
-   <TITLE>L10n Library</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000" <CENTER>
-
-<H1>
-L10n Library</H1>
-This is where you will find localization kit documentation on-line.&nbsp;
-Documentation will also be provided within the localization kits themselves.&nbsp;
-Theoretically, the on-line docs and the in-kit docs should be the same;
-however, if there is a discrepancy, you should:
-<UL>a) believe the in-kit docs over the on-line docs, and
-<BR>b) inform us that there is a mismatch between the two versions.&nbsp;
-We'll fix it as soon as possible.</UL>
-
-<HR WIDTH="50%">
-
-<P>Documentation is grouped into "pods" of related HTML pages. Select the
-pod you wish to read from the links below.
-<BR>&nbsp;
-<CENTER><TABLE CELLSPACING=5 >
-<TR BGCOLOR="#3366FF">
-<TH WIDTH="20%">Documentation Pod</TH>
-
-<TH>Description</TH>
-</TR>
-
-<TR>
-<TD VALIGN=TOP><A HREF="l10nkits/client/windows/docs/nav40/splash.html">Windows
-32 bit Front End</A></TD>
-
-<TD>Instructions for localizing the client for Windows NT and Windows<NOBR>
-</NOBR>'95.</TD>
-</TR>
-
-<TR>
-<TD VALIGN=TOP><A HREF="l10nkits/client/windows/docs/dogTool/dogToolUG.html">Netscape
-Translation Tools</A></TD>
-
-<TD>Instructions for using the freely available Netscape Translation Tools:
-ToolCool and DogLev <FONT COLOR="#FF0000">(note: DogLev docs are under
-construction.)</FONT></TD>
-</TR>
-
-<TR>
-<TD VALIGN=TOP><A HREF="l10nkits/client/windows/docs/installer/splash.html">Windows
-Installer</A></TD>
-
-<TD>Instructions for localizing the Windows installer program.</TD>
-</TR>
-
-</TABLE></CENTER>
-&nbsp;
-</BODY>
-</HTML>

l10nkits/client/xp/docs/mozilla.org/l10nkitintro.html

@@ -1,148 +0,0 @@
-<HTML>
-<HEAD>
-   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
-   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (WinNT; U) [Netscape]">
-   <META NAME="Author" CONTENT="Rick Elliot">
-   <TITLE>universal localization kits</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000" <CENTER>
-
-<CENTER>
-<H1>
-<FONT COLOR="#FF0000">they're here!</FONT></H1></CENTER>
-
-<CENTER>
-<H1>
-localization kits</H1></CENTER>
-
-<H2>
-purpose</H2>
-This page details the localization kits that are being made publicly available
-as part of the universal localization program. As the program's <A HREF="ulpFAQ.html">FAQ</A>
-stated, there are two dimensions to this program: what is permitted versus
-what is facilitated. Localization kits are the primary way in which the
-universal localization program facilitates translation of the branded Netscape
-Communicator Standard Edition and Netscape Navigator products, as well
-as the Mozilla product and its derivatives.
-
-<P>A localization kit contains the tools, instructions and resources necessary
-to produce a localized version of the target software. Currently, these
-kits are derived from the Netscape Communicator Standard Edition and Netscape
-Navigator version 4.x products. By following the instructions in the kits,
-you will be able to produce a localized client product in any supported
-language. By extension, you may be able to apply the tools and information
-provided in the localization kits to localize the Mozilla client. Finally,
-following this model, we anticipate developers publishing their own localization
-kits based on their derivatives of the mozilla.org source code.
-
-<H2>
-kit contents</H2>
-While the exact contents of each localization kit differs according to
-the platform and product it is intended for, each kit is composed of the
-following general pieces:
-<UL>
-<LI>
-The English language resources (in exportable, binary form)</LI>
-
-<LI>
-Localization notes</LI>
-
-<LI>
-Kit documentation</LI>
-
-<LI>
-Tools</LI>
-</UL>
-
-<DT>
-<B>Resources</B></DT>
-
-<DD>
-The English language resources are provided as the base for your localization
-work. These resources will match the version used to generate the localization
-notes. For Microsoft Windows and Apple Macintosh platforms, the English
-language resources are provided as binaries. (You may also download a later
-version of the product by visiting Netscape's <A HREF="http://home.netscape.com/download/index.html">download
-pages</A>. Be sure you only localize the <B><I>export</I></B> version!
-Otherwise, you will not be able to legally distribute your localized product.)
-Netscape's experience with localization has convinced us that localizing
-resource binaries is more efficient than working on source files (at least
-on Windows and Macintosh).</DD>
-
-<P>
-<DT>
-<B>Localization notes</B></DT>
-
-<DD>
-Localization notes are the heart of the kits: this is where you will find
-detailed information on the exact way in which particularly sensitive resources
-must be handled. For example, the localization notes tell you which resources
-must not be changed from their original values; they will also identify
-resources that appear as HTML or Javascript, or that must match other resources
-in order for the product to function properly.</DD>
-
-<P>
-<DT>
-<B>Documentation</B></DT>
-
-<DD>
-The localization kit documentation is a series of HTML files which give
-you an overview of the localization process, as well as generic instructions
-on localizing the different data types found in the product.</DD>
-
-<P>
-<DT>
-<B>Tools</B></DT>
-
-<DD>
-We have attempted to make our Localization Kits "tools agnostic," meaning
-you are free to use whichever localization tools you desire to accomplish
-your aims. At the same time, we have chosen to release some of our internally
-developed localization tools; these are provided "as is", with no support
-(but we use them daily with great success).</DD>
-
-
-<P>
-<HR WIDTH="100%">
-<H2>
-next steps</H2>
-If you have questions about the universal localization program, try the
-<A HREF="ulpFAQ.html">FAQ</A>.
-
-<P>Read the <A HREF="http://home.netscape.com/newsref/pr/newsrelease585.html">Press
-Release</A> announcing the universal localization program.
-
-<P>To download any of the localization kits, proceed to the <A HREF="kitDownload.html">
-download pages.</A>
-
-<P>To read the localization kit documentation on-line, visit the <A HREF="l10nLibrary.html">L10n
-Library.</A>
-
-<P>If you're looking for more information about localization, internationalization
-or links to related subjects, visit the Links &amp; Resources page. [<FONT COLOR="#FF0000">coming
-soon!</FONT>]
-<BR>
-<HR WIDTH="100%">
-<CENTER><TABLE COLS=4 WIDTH="80%" >
-<TR>
-<TD>
-<CENTER>[<A HREF="kitDownload.html">Download</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="l10nLibrary.html">L10n Library</A>]</CENTER>
-</TD>
-
-<TD>
-<CENTER>[<A HREF="ulpFAQ.html">FAQ</A>]</CENTER>
-</TD>
-
-<TD>[Links &amp; Resources]</TD>
-</TR>
-</TABLE></CENTER>
-
-<CENTER><FONT SIZE=-2>Copyright 1998, Netscape Communications Corp., All
-Rights Reserved.</FONT></CENTER>
-
-</BODY>
-</HTML>

l10nkits/client/xp/docs/mozilla.org/ulpFAQ.html

@@ -1,375 +0,0 @@
-<HTML>
-<HEAD>
-   <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
-   <TITLE>universal localization program FAQ</TITLE>
-</HEAD>
-<BODY>
-
-<H2>
-<FONT SIZE=+3>universal localization program</FONT> <FONT SIZE=+3>FAQ</FONT></H2>
-
-Last Updated: 23 Mar. 1998 3:40 pm
-<BR>
-<HR SIZE=4>
-
-<H2>
-O<FONT SIZE=-1>VERVIEW</FONT></H2>
-
-<P>Netscape's universal localization program furthers the goals of mozilla.org by 
-publishing tools and documentation to aid developers who wish to localize Mozilla.  In addition,
-participants in the universal localization program may freely translate the Netscape Navigator 
-and Netscape Communicator Standard Edition version 4.x.  These localized products may be freely distributed under
-the participant's branding. 
-<P>
-This document answers some frequently asked questions about the universal localization program.
-<P>
-<OL>
-<H3>
-G<FONT SIZE=-1>ENERAL</FONT></H3>
-
-<LI>
-<A HREF="#1">What is localization?</A></LI>
-
-<LI>
-<A HREF="#2">How does the universal localization program relate to mozilla.org?</A></LI>
-
-<LI>
-<A HREF="#3">How does the universal localization program relate to the unlimited distribution program?</A></LI>
-
-<LI>
-<A HREF="#4">What are the terms of the universal localization program's License?</A></LI>
-
-<LI>
-<A HREF="#5">What products may I localize?</A></LI>
-
-<LI>
-<A HREF="#6">Who should participate in the universal localization program?</A></LI>
-
-<H3>
-D<FONT SIZE=-1>ISTRIBUTION</FONT></H3>
-
-<LI>
-<A HREF="#7">Where can I distribute the localized version?</A></LI>
-
-<LI>
-<A HREF="#8">How much does this cost?</A></LI>
-
-<LI>
-<A HREF="#9">Am I allowed to use the Netscape brand, trademarks and logo?</A></LI>
-
-<LI>
-<A HREF="#10">Will there be any end user support from Netscape for my finished
-product?</A></LI>
-
-<LI>
-<A HREF="#11">Am I required to give my localization back to the Net?</A></LI>
-
-<LI>
-<A HREF="#12">Can I download software from the general download page on
-the Netscape web site and localize it?</A></LI>
-
-<H3>
-T<FONT SIZE=-1>ECHNICAL INFORMATION</FONT></H3>
-
-<LI>
-<A HREF="#13">What is a localization kit?</A></LI>
-
-<LI>
-<A HREF="#14">Why do I need a localization kit?</A></LI>
-
-<LI>
-<A HREF="#15">What platforms does this Program support?</A></LI>
-
-<LI>
-<A HREF="#16">Into what languages can I translate the software?</A></LI>
-
-<LI>
-<A HREF="#17">How can I get technical assistance?</A></LI>
-
-<LI>
-<A HREF="#18">I understand that the source code distributed by mozilla.org will not
-include certain 3rd-party components, and cryptography. If I localize
-Netscape Navigator 4.x, will I lose the ability to use those components?</A></LI>
-
-<LI>
-<A HREF="#19">Will this work for Communicator Professional Edition components?</A></LI>
-
-<LI>
-<A HREF="#20">What about products in France?</A></LI>
-
-<LI>
-<A HREF="#21">What spell checkers can I use?</A></LI>
-
-<LI>
-<A HREF="#22">What about installers?</A></LI>
-</OL>
-
-<HR SIZE=4>
-
-<OL>
-
-<H3>
-G<FONT SIZE=-1>ENERAL</FONT></H3>
-
-<A NAME="1"></A>
-<LI>
-<B>What is Localization?</B></LI>
-
-<BR>Localization is the process of adapting software for a specific international market; 
-this process includes translating the user interface, resizing dialog boxes, replacing icons
-and other culturally sensitive graphics (if necessary), customizing features (if necessary), 
-and testing the localized product to ensure that the program still works.
-
-<P><A NAME="2"></A>
-<LI>
-<B>How does the universal localization program relate to mozilla.org?</B></LI>
-
-<BR>The universal localization program is an extension of the philosophy
-behind mozilla.org. The goal of the program is to enable developers on the
-Internet to freely localize and distribute products based on the Netscape
-client and on derivatives based on the mozilla.org source. mozilla.org
-will host the content for this program, and provide a forum for developers
-to correspond on their work.
-
-<P><A NAME="3"></A>
-<LI>
-<B>How does the universal localization program relate to the unlimited distribution program?</B></LI>
-
-<BR>Whereas the unlimited distribution program allows you to
-freely distribute Netscape Navigator and Netscape Communicator
-Standard Edition client binaries, and to make slight modifications to these products,
-the universal localization program allows you to create localized,
-independently branded versions of these products.  You may then distribute these localized
-products according to the terms of the License.
-<P>
-For more information on the <A HREF="http://home.netscape.com/comprod/netscape_partner_programs/browser_distrib/index.html">
-unlimited distribution program</A>, please visit
-http://home.netscape.com/comprod/netscape_partner_programs/browser_distrib/index.html.
-
-<P><A NAME="4"></A>
-<LI>
-<B>What are the terms of the universal localization program's License?</B></LI>
-
-<BR>We are still working out some of the details of the License Agreement
-under which this program will be administered.  References to the License Agreement in 
-this document are, therefore, regrettably vague.  We hope to have this ironed out soon.
-
-<P><A NAME="5"></A>
-<LI>
-<B>What products may I localize?</B></LI>
-
-<BR>You may localize the Netscape Navigator, Netscape Communicator Standard
-Edition, or any client based on the Mozilla source code available from mozilla.org (or its
-mirror sites).
-Note that localizing products not directly documented in the localization
-kits probably will be more difficult than localizing those that are directly documented.
-
-
-<P><A NAME="6"></A>
-<LI>
-<B>Who should participate in the universal localization program?</B></LI>
-
-<BR>This program is intended for professional software localizers, localization engineers, 
-or others who are knowledgeable in software localization concepts and techniques. 
-However, if you are familiar with common tools, such as resource editors, and if you 
-are fluent in a particular language, you could use the tools and information provided by 
-this program to localize Navigator or Communicator in your language.
-
-<H3>
-D<FONT SIZE=-1>ISTRIBUTION</FONT></H3>
-
-<P><A NAME="7"></A>
-<LI>
-<B>Where can I distribute the localized version?</B></LI>
-
-<BR>The terms of the License do not change due to translation of the software: 
-you may distribute localized versions of the Netscape branded binaries anywhere
-allowed by the export license. (A copy of this license comes with every Netscape product).
-For localized Mozilla product derivatives, you may distribute them anywhere allowable under 
-the final free source License (whatever that turns out to be).
-
-<P><A NAME="8"></A>
-<LI>
-<B>How much does this cost?</B></LI>
-
-<BR>There is no cost to participate in the universal localization program.
-
-<P><A NAME="9"></A>
-<LI>
-<B>Am I allowed to use the Netscape brand, trademarks and logo?</B></LI>
-
-<BR>You may not use the name "Netscape" nor the "N" logo
-in your localized product. However, you may use the trademarks "Navigator,"
-"Communicator," "Messenger," "Collabra", and the "Ship's Wheel icon".  The universal 
-localization program License will give you the exact legal details.
-
-<P><A NAME="10"></A>
-<LI>
-<B>Will there be any end user support from Netscape for my finished product?</B></LI>
-
-<BR>No. The products derived from the mozilla.org source and Netscape binaries
-are not entitled to Netscape end user support. The level of support you provide 
-your end users is up to you to decide.
-
-<P><A NAME="11"></A>
-<LI>
-<B>Am I required to give my localization back to the Net?</B></LI>
-
-<BR>The terms of the License are not yet set on this issue.
-
-<P><A NAME="12"></A>
-<LI>
-<B>Can I download software from the general download page on the Netscape
-web site and localize it?</B></LI>
-
-<BR>Yes. You may download, localize and distribute any Netscape Navigator
-and Netscape Communicator Standard Edition product. However, we may not produce a
-localization kit for all versions and platforms. You may try
-to use the instructions and tools in the kits we do release for these other versions
-and platforms, but successful localization could be quite difficult under these circumstances.
-
-<H3>
-T<FONT SIZE=-1>ECHNICAL INFORMATION</FONT></H3>
-
-<P><A NAME="13"></A>
-<LI>
-<B>What is a localization kit?</B></LI>
-
-<BR>A localization kit contains the tools, instructions and resources necessary
-to produce a localized version of a specific software product. The
-detailed instructions contained in a given localization kit are usually
-specific to a single platform and/or version of a product. These instructions
-may, however, be broadly applicable to more than one version or platform.
-Therefore, when we say a localization kit "supports" a given platform,
-version or language, what we mean is that kit contains detailed instructions
-that directly apply to that platform or version or language. It may
-be possible to use a localization kit for one platform to successfully
-localize another. On the other hand, it may be quite difficult.
-
-<P><A NAME="14"></A>
-<LI>
-<B>Why do I need a localization kit?</B></LI>
-
-<BR>The primary goal of a localization kit is to convey information about
-the product being localized so that the over-translation of restricted
-resources does not occur. Over-translation occurs when a resource changes
-that must not be changed. It can also occur when a resource must be changed
-in a particular way, but is not done so. In both cases, the product may
-not function properly or may cease to function at all (e.g. crash). The
-information contained in the localization kits is designed to help
-avoid these situations and to help you correctly localize the product.
-Attempting to translate the source files directly without such a kit could
-be a frustrating and error-prone operation.
-
-<P><A NAME="15"></A>
-<LI>
-<B>What platforms does this program support?</B></LI>
-
-<BR>This question has two dimensions: what platforms are permissible versus what platforms 
-are made easy for me to localize onto.  The first issue is addressed by the program, the second, 
-by the localization kits.
-<P>
-The universal localization program allows you to create and distribute localized 
-products for any platform, except Caldera Linux.  Netscape has an exclusive agreement 
-with Caldera, so this platform is off the list.
-<P>
-Localization kits are currently planned for Windows (32 bit) and Macintosh platforms. 
-Windows 16 bit and Unix localization kits are not available at this time.  You are welcome to 
-try to localize the software for any platform (except Caldera Linux), with or without the benefit of 
-a localization kit (but doing so without will be harder than with).
-
-<P><A NAME="16"></A>
-<LI>
-<B>Into what languages can I translate the software?</B></LI>
-
-<BR>This is the same issue as above: under the universal localization program, you are free 
-to localize the product into any language you desire.  On the other hand, not every language
-is fully supported by current (version 4.x) client software.  In general, if the target language you desire 
-is supported by one of the encodings listed in the Navigator's View | Encoding menu,
-localization into that language should be successful. This is because parts of the product's 
-user interface is HTML, which depends on the encoding support built into the HTML rendering 
-engine to display properly.
-<P>
-You will need an operating system that also supports that language. This is because the fonts 
-necessary to display the standard (non-HTML) localized resources, as well as the input methods, 
-keyboard mappings, etc., required to input your language's characters, are provided by the 
-OS.
-<P>
-Please note that at this time, Communicator does not support bidirectional languages, such 
-as Arabic and Hebrew, nor languages with complex scripts, such as Devanagari. Languages 
-with contextual line breaking algorithms, such as Thai, are also not supported (although 
-partial localization and display of web pages may still be possible through various means).
-<P>
-To provide support for additional languages, you will be able modify the 5.x source
-code which will be distributed by mozilla.org.
-
-<P><A NAME="17"></A>
-<LI>
-<B>How can I get technical assistance?</B></LI>
-
-<BR>There is no formal technical support; you are on your own. However,
-we expect that you will find the newsgroups and mailing lists hosted on
-mozilla.org to be a valuable resource. You can find the list of newsgroups
-by going to the mozilla.org <A HREF="http://www.mozilla.org/community.html">Community</A> pages:
- http://www.mozilla.org/community.html
-
-<P><A NAME="18"></A>
-<LI>
-<B>I understand that the source code distributed by mozilla.org will not
-include certain 3rd-party components or cryptography. If I localize
-Netscape Navigator 4.x, will I lose the ability to use those components?</B></LI>
-
-<BR>No. Since the localization process does not depend on having
-the source code to the program available (all you are doing, really, is
-changing strings in an existing executable) you will retain all of the
-functionality present in the executable you started with. It will
-just be in a different language.
-
-<P><A NAME="19"></A>
-<LI>
-<B>Will this work for Communicator Professional Edition components?</B></LI>
-
-<BR>No. The Professional Edition includes 3rd Party components that are
-not covered by the Unlimited Distribution or NPL programs. These
-components cannot be modified under this program.
-
-<P><A NAME="20"></A>
-<LI>
-<B>What about products in France?</B></LI>
-
-<BR>You are free to create French versions.  However, to comply with French law, 
-if you distribute a product which has cryptographic 
-capabilities, that product must use the special encryption level for France.
-Compliant versions of Communicator and Navigator are available from Netscape's 
-download page. The English Export version of Netscape Navigator
-and Netscape Communicator Standard Edition are not authorized for import
-into France. 
-<P>
-Netscape's download page can be found 
-<A HREF="http://home.netscape.com/download/client_download.html">here</A>: 
-http://home.netscape.com/<WBR>download/<WBR>client_download.html
-
-<P><A NAME="21"></A>
-<LI>
-<B>What Spell Checkers can I use?</B></LI>
-
-<BR>The spell checker module built into Composer is licensed from Inso
-Software. Inso permits you to bundle two spell checkers with
-your product. For additional spell check dictionaries, contact Inso Corporation.
-<P>
-Visit <A HREF="http://www.inso.com/">Inso Corp.'s web site</A> at: http://www.inso.com/
-
-<P><A NAME="22"></A>
-<LI>
-<B>What about Installers?</B></LI>
-
-<BR>Currently, Netscape's installer programs are built using 3rd party
-modules, for which we do not have redistribution rights. Therefore,
-we are not releasing a complete installer kit; however, guidelines for
-creating your own installer will be available. You may use any commercially
-available installer software to package your localized product and obtain
-authorization for distribution directly from the provider of the installer
-software.</OL>
-
-</BODY>
-</HTML>