From f8e2f3e08d779092cf7d3f26f369c0941edf9349 Mon Sep 17 00:00:00 2001 From: Martin Arver Date: Tue, 17 Oct 2006 12:18:51 +0000 Subject: Fix for more consistent and proper British English. (-ize/-ise etc) git-svn-id: svn://svn.rockbox.org/rockbox/trunk@11246 a1c6a512-1295-4272-9138-f99709370657 --- manual/getting_started/h10_install.tex | 6 ++--- manual/getting_started/installation.tex | 44 +++++++++++++++---------------- manual/getting_started/ipod_install.tex | 8 +++--- manual/getting_started/iriver_install.tex | 40 ++++++++++++++-------------- manual/getting_started/main.tex | 12 ++++----- 5 files changed, 55 insertions(+), 55 deletions(-) (limited to 'manual/getting_started') diff --git a/manual/getting_started/h10_install.tex b/manual/getting_started/h10_install.tex index cc804f008a..36a36d8ec4 100755 --- a/manual/getting_started/h10_install.tex +++ b/manual/getting_started/h10_install.tex @@ -4,7 +4,7 @@ The \playertype{} can be connected to a computer in two different modes: \item Universal Mass Storage (UMS): In this mode, it will appear on your computer as a regular disk. This mode works with all major operating systems, including Windows, Linux and Mac OS X. \item Media Transfer Protocol (MTP): In this mode, it will appear on your computer as a Media Device. MTP was created by Microsoft for use with DAPs and only works with Windows XP and Media Player 10. \end{itemize} -The \playerlongtype{} is \opt{h10}{only available as a MTP device, but}\opt{h10_5gb}{available as both a MTP and as a UMS device, depending on where and when you bought it. You can tell which you have by how it appears when you conect it to a computer. If it appears as a regular disk then it is UMS. If it appears as a Media Device on Windows XP, or if it doesn't appear at all on other operating systems, then it is MTP. Even if you have a MTP \dap{}, it} can be forced into UMS mode using the UMS trick. +The \playerlongtype{} is \opt{h10}{only available as a MTP device, but}\opt{h10_5gb}{available as both a MTP and as a UMS device, depending on where and when you bought it. You can tell which you have by how it appears when you connect it to a computer. If it appears as a regular disk then it is UMS. If it appears as a Media Device on Windows XP, or if it doesn't appear at all on other operating systems, then it is MTP. Even if you have a MTP \dap{}, it} can be forced into UMS mode using the UMS trick. \subsubsection{UMS mode and the UMS trick} It is possible to force a MTP \playertype{} to start up in UMS mode using the following procedure: @@ -28,9 +28,9 @@ It is possible to force a MTP \playertype{} to start up in UMS mode using the fo \end{itemize}} \item Connect your \playertype{} to the computer using UMS mode and the UMS trick\opt{h10_5gb}{ if necessary}. \item Make a backup of the \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}} file in the \fname{System} directory on your \playertype{}. - \opt{h10_5gb}{\note{If you have a Pure model \playertype{} (which doesn't have a FM radio) it is possible that this file will be called \fname{H10EMP.mi4} instead. If so, rename the \fname{H10.mi4} you downloade in step 1 to \fname{H10EMP.mi4}.}} + \opt{h10_5gb}{\note{If you have a Pure model \playertype{} (which doesn't have a FM radio) it is possible that this file will be called \fname{H10EMP.mi4} instead. If so, rename the \fname{H10.mi4} you downloaded in step 1 to \fname{H10EMP.mi4}.}} \note{You should keep a safe backup of this file for use if you ever wish to switch back to the \playerman{} firmware.} - \note{If you can't see the \fname{System} directory, you will need to make sure your operating system is configured to show hidden files and folers.} + \note{If you can't see the \fname{System} directory, you will need to make sure your operating system is configured to show hidden files and folders.} \item Copy the \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4} (or \fname{H10EMP.mi4} if you have a \playertype{} Pure)} file you downloaded to the System directory on your \dap{}. \end{enumerate} diff --git a/manual/getting_started/installation.tex b/manual/getting_started/installation.tex index 946635c559..5a22d0b606 100644 --- a/manual/getting_started/installation.tex +++ b/manual/getting_started/installation.tex @@ -14,11 +14,11 @@ software. Rockbox is distributed as an archive using the \fname{.zip} format. Thus you need a tool to handle that compressed format. Usually your computer should have a tool installed that can - handle the \fname{.zip} file format. Windows XP has builtin support for + handle the \fname{.zip} file format. Windows XP has built-in support for \fname{.zip} files and presents them to you as folders unless you have installed a third party program that handles compressed files. For other operating systems this may vary. If the \fname{.zip} file format - is not recognized on your computer you can find a program to handle them + is not recognised on your computer you can find a program to handle them at \url{http://www.info-zip.org/} or \url{http://sevenzip.sf.net/} which can be downloaded and used free of charge. @@ -30,7 +30,7 @@ software. \opt{ipod}{ \note{Your \dap{} should enter disk mode automatically when connected to a - computer via USB. If your computer does not recognize your \dap{}, you + computer via USB. If your computer does not recognise your \dap{}, you may need to enter the disk mode manually. Disconnect your \dap{} from the computer. Reset the \dap{} by pressing and holding the \ButtonMenu{} and \ButtonSelect{} buttons simultaneously. As soon as the \dap{} resets, @@ -42,7 +42,7 @@ software. \item[Text editor.] As you will see in the following chapters, Rockbox is highly configurable. In addition to saving configurations within Rockbox, - Rockbox also allows you to create customized configuration files. If you + Rockbox also allows you to create customised configuration files. If you would like to edit custom configuration files on your computer, you will need a text editor like Windows' ``Wordpad''. @@ -75,22 +75,22 @@ software. \begin{description} \opt{HAVE_RB_BL_ON_DISK}{ - \item[The \playerman{} bootloader.] - The \playerman{} bootloader is the program that tells your \dap{} how to boot + \item[The \playerman{} boot loader.] + The \playerman{} boot loader is the program that tells your \dap{} how to boot and load the remaining firmware from disk. It is also responsible for the disk mode on your \dap{}. - This bootloader is stored in special flash memory in your \playerman. It is + This boot loader is stored in special flash memory in your \playerman. It is already installed on your \dap{}, so it is never necessary to modify this in order to install Rockbox.} - \item[The Rockbox bootloader.] \index{Bootloader} - \opt{HAVE_RB_BL_ON_DISK}{The Rockbox bootloader is loaded from disk by - the \playerman{} bootloader. It is responsible for loading the Rockbox + \item[The Rockbox boot loader.] \index{Boot loader} + \opt{HAVE_RB_BL_ON_DISK}{The Rockbox boot loader is loaded from disk by + the \playerman{} boot loader. It is responsible for loading the Rockbox firmware and for providing the dual boot function. It directly replaces the \playerman{} firmware on the \daps{} disk.} \opt{HAVE_RB_BL_IN_FLASH}{ - The bootloader is the program that tells your + The boot loader is the program that tells your \dap{} how to boot and load other components of Rockbox. This is the component of Rockbox that is installed to the flash memory of your \playerman.} @@ -107,14 +107,14 @@ software. \end{description} - \subsection{Installing the bootloader} + \subsection{Installing the boot loader} \opt{h1xx,h300}{\input{getting_started/iriver_install.tex}} \opt{ipod}{\input{getting_started/ipod_install.tex}} \opt{x5}{\input{getting_started/iaudio_install.tex}} \opt{h10,h10_5gb}{\input{getting_started/h10_install.tex}} \subsection{Installing the firmware} - After installing the bootloader, the installation becomes fairly easy. + After installing the boot loader, the installation becomes fairly easy. } There are three different types of firmware binaries from Rockbox website: @@ -217,7 +217,7 @@ use. your player using Itunes, you will not be able to see your music because Itunes changes your files' names and hides them in directories in the \fname{Ipod\_Control} folder. You can view files placed on your \dap{} by - Itunes by initializing and using Rockbox's Tag Cache. See + Itunes by initialising and using Rockbox's Tag Cache. See \reference{ref:tagcache} for more information. } } @@ -252,7 +252,7 @@ connect the \playerman{} to your computer, and delete the \optv{ipod}{ Next, open a command window (Windows) or a terminal window (Mac or Linux). Navigate to the folder you created when you downloaded the - \fname{ipodpatcher} program you used to install the Rockbox bootloader. + \fname{ipodpatcher} program you used to install the Rockbox boot loader. Type the following command: \begin{code} @@ -272,24 +272,24 @@ Turn the \dap{} back on and the original \playerman{} software will load. \opt{h1xx}{ \note{ - There's no need to remove the installed bootloader. If you want to remove + There's no need to remove the installed boot loader. If you want to remove it, simply flash an unpatched \playerman{} firmware. Be aware that doing so - will also remove the bootloader USB mode. As that mode can come in quite + will also remove the boot loader USB mode. As that mode can come in quite handy (especially when having disk errors) it is recommended to keep the - bootloader. It also gives you the possibility of trying Rockbox anytime + boot loader. It also gives you the possibility of trying Rockbox anytime later by simply installing the distribution files. } } \opt{h300}{ \note{ - There's no need to remove the installed bootloader, although you if you - retain the Rockbox bootloader, you will need to hold the \ButtonRec{} + There's no need to remove the installed boot loader, although you if you + retain the Rockbox boot loader, you will need to hold the \ButtonRec{} button each time you want to start the original firmware. If you want to remove it simply flash an unpatched \playerman{} firmware. Be aware that - doing so will also remove the bootloader USB mode. As that mode can come in + doing so will also remove the boot loader USB mode. As that mode can come in quite handy (especially when having disk errors), you may wish to keep the - bootloader. It also gives you the possibility of trying Rockbox anytime + boot loader. It also gives you the possibility of trying Rockbox anytime later by simply installing a new build. } } diff --git a/manual/getting_started/ipod_install.tex b/manual/getting_started/ipod_install.tex index a50519db8e..040532b950 100755 --- a/manual/getting_started/ipod_install.tex +++ b/manual/getting_started/ipod_install.tex @@ -5,7 +5,7 @@ Please check the wiki for up-to-date and improved installation instructions! If you find errors you're of course welcomed to report them so we can fix it for the next daily builds.} - Installing the bootloader is the trickiest part of the installation. + Installing the boot loader is the trickiest part of the installation. \opt{ipodnano}{First, you need to find out which version of the Apple firmware you're running. To do this, start the Apple firmware and go to Settings screen. In the ``About'' screen you'll find the version number @@ -87,7 +87,7 @@ for the next daily builds.} ipodpatcher -r \emph{N} bootpartition.bin \end{code} \note{You should keep a safe backup of this \fname{bootpartition.bin} file - for use if you ever wish to either upgrade the Rockbox bootloader or + for use if you ever wish to either upgrade the Rockbox boot loader or uninstall Rockbox from your Ipod} \item Extract the Apple firmware from the partition image image just created: \begin{code} @@ -102,7 +102,7 @@ for the next daily builds.} ipod_fw -o apple_sw_5g_rcsc.bin -e 1 bootpartition.bin \end{code} } - \item Merge the Rockbox bootloader you downloaded previously with the Apple + \item Merge the Rockbox boot loader you downloaded previously with the Apple firm\-ware.% \optv{ipodnano}{ If your firmware version is lower than 1.2 this works you need @@ -265,7 +265,7 @@ Now, proceed with installing the firmware itself. \item \url{http://www.rockbox.org/viewcvs.cgi/*checkout*/tools/ipod_fw.c} \end{itemize} Now compile it to an executable by opening a command prompt and changing - to the folder created previously. Thn run the following command: + to the folder created previously. Then run the following command: \begin{code} gcc -o ipod_fw ipod_fw.c \end{code} diff --git a/manual/getting_started/iriver_install.tex b/manual/getting_started/iriver_install.tex index fb950a23dd..0cb59492e8 100644 --- a/manual/getting_started/iriver_install.tex +++ b/manual/getting_started/iriver_install.tex @@ -1,11 +1,11 @@ % $Id$ % - Installing the bootloader is the trickiest part of the installation. - The Rockbox bootloader allows users to boot into either the Rockbox - firmware or the iriver firmware. For legal reasons, we cannot distribute - the bootloader. Instead, we have developed a program that will patch the - Iriver firmware with the Rockbox bootloader. These instructions will explain - how to download and patch the Iriver firmware with the Rockbox bootloader + Installing the boot loader is the trickiest part of the installation. + The Rockbox boot loader allows users to boot into either the Rockbox + firmware or the \playerman{} firmware. For legal reasons, we cannot distribute + the boot loader. Instead, we have developed a program that will patch the + Iriver firmware with the Rockbox boot loader. These instructions will explain + how to download and patch the Iriver firmware with the Rockbox boot loader and install it on your jukebox. @@ -22,7 +22,7 @@ your player.} \opt{IRIVER_H300_PAD}{1.28K, 1.28EU, 1.28J, 1.29K, 1.29J and 1.30EU. \note{The US H3xx firmware is not currently supported and cannot be - patched to be used with the bootloader. If you wish to install Rockbox + patched to be used with the boot loader. If you wish to install Rockbox on a US \playername, you must use an international firmware, which will permanently remove DRM support from the player.} }% @@ -32,7 +32,7 @@ to your desktop. Likewise, if the file that you downloaded is an \fname{.exe} file, double-click on the \fname{.exe} file to extract the \fname{.hex} file to your desktop. - When running linux you should be able extracting \fname{.exe} + When running Linux you should be able extracting \fname{.exe} files using \fname{unzip}. % \item Download the firmware patcher \fname{fwpatcher.exe} from @@ -50,7 +50,7 @@ to the \fname{.hex} file that you previously downloaded to your desktop. % \item Click \setting{Patch}. The firmware patcher will patch the - original firmware to include the Rockbox bootloader. The \fname{.hex} + original firmware to include the Rockbox boot loader. The \fname{.hex} file on your desktop is now a modified version of the original \fname{.hex} file. % @@ -65,7 +65,7 @@ or that it is connected to the power adaptor. Interrupting the next step due to a power failure most likely will brick your \dap{}.} % - \item Update your \daps{} firmware with the patched bootloader. To do this, turn + \item Update your \daps{} firmware with the patched boot loader. To do this, turn the jukebox on. Press and hold the \opt{IRIVER_H100_PAD,IRIVER_H300_PAD}{\ButtonSelect{} button }% to enter the main menu, and navigate to \setting{General $\rightarrow$ Firmware @@ -76,24 +76,24 @@ firmware update is complete the player will turn itself off. (The update firmware process usually takes a minute or so.) - You have now installed the Rockbox bootloader. + You have now installed the Rockbox boot loader. \end{enumerate} -\note{If you install the Rockbox bootloader but do not install the - Rockbox firmware the Rockbox bootloader will load the iriver firmware when the +\note{If you install the Rockbox boot loader but do not install the + Rockbox firmware the Rockbox boot loader will load the Iriver firmware when the jukebox is turned on. To load the \playerman{} firmware press and hold \ButtonRec{} before powering up the \dap{} until the \playerman{} logo appears. } -\note{The bootloader has a builtin ``bootloader USB mode''. This function +\note{The boot loader has a built-in ``boot loader USB mode''. This function switches to USB mode when the \dap{} is connected to a computer upon - power-up. This way you can access the \daps{} harddisk without the need - to boot any firmware (which is also useful when your harddisk is - damaged). The screen will simply display the text ``bootloader USB mode''. - After you disconnect the \dap{} from USB the bootloader will - continue booting Rockbox. As in bootloader USB mode the firmware + power-up. This way you can access the \daps{} hard disk without the need + to boot any firmware (which is also useful when your hard disk is + damaged). The screen will simply display the text ``boot loader USB mode''. + After you disconnect the \dap{} from USB the boot loader will + continue booting Rockbox. As in boot loader USB mode the firmware itself hasn't been loaded this is also a simple way of updating Rockbox. - After the disconnect the bootloader will load the updated version of + After the disconnect the boot loader will load the updated version of Rockbox. } diff --git a/manual/getting_started/main.tex b/manual/getting_started/main.tex index 0e930ff1a6..d85f4c4894 100644 --- a/manual/getting_started/main.tex +++ b/manual/getting_started/main.tex @@ -4,14 +4,14 @@ This is the manual for Rockbox. Rockbox is an open source firmware replacement for a growing number of MP3 players. Rockbox aims to be considerably more functional and efficient than your device's stock firmware while remaining easy -to use and customizable. Rockbox is written by users, for users. Not only is it +to use and customisable. Rockbox is written by users, for users. Not only is it free to use, it's also released under the GNU public license, which means that it will always remain free both to use and to change. -Rockbox has been in development since 2001, and recieves new features, tweaks +Rockbox has been in development since 2001, and receives new features, tweaks and fixes each day to provide you with the best possible experience on your MP3 player. A major goal of Rockbox is to be simple and easy to use, yet remain very -customizable and configurable. We believe that you should never need to go +customisable and configurable. We believe that you should never need to go through a series of menus for an action you perform frequently. We also believe that you should be able to configure almost anything about Rockbox you could want, pertaining to functionality. Another top priority of Rockbox is audio @@ -32,14 +32,14 @@ firmware. There is, however, more help available. The Rockbox website at written by members of the Rockbox community and this should be your first port of call when looking for further help. -If you can't find the informations you're searching for on the Rockbox +If you can't find the information you're searching for on the Rockbox website there are a number of support channels you should have a look at. You can try the Rockbox forums located at \url{http://forums.rockbox.org/}. Another option are the mailing lists which can be found at \url{http://www.rockbox.org/mail/}. From that page you can subscribe to the lists and browse the archives. For searching the list archives simply use the search field that is located on the left side of the web site. -Also you can ask on IRC. The main channel for rockbox is \texttt{\#rockbox} +Also you can ask on IRC. The main channel for Rockbox is \texttt{\#rockbox} on \url{irc://irc.freenode.net}. A bunch of helpful developers and users are usually around. Just join and ask -- if someone knows the answer you'll usually get an answer pretty quickly. More information including IRC logs @@ -70,7 +70,7 @@ you finding important parts or parts you could skip. The following icons are used: \note{This indicates a note. A note starts always with the text ``Note''. For easier finding of notes we have put this an icon in the margin like - here. Notes are used to mark informations that could help you + here. Notes are used to mark information that could help you or indicate a possible ``weirdness'' in rockbox that would be explained. } \warn{This is a warning. In contrast to notes mentioned above, a warning -- cgit v1.2.3