devs/foxbox
1
0
Fork 0
forked from len0rd/rockbox
Code Pull requests Activity

FS #8340 by David Bishop. Remove contractions from the manual, as this seems to be common practice in this format and makes it easier to read for non-native english speakers. New manual work should try to adhere to this.

Browse source 
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@16302 a1c6a512-1295-4272-9138-f99709370657
This commit is contained in:
Thom Johansen 2008-02-13 13:32:44 +00:00
parent 09fc078bf5
commit c479b9975d
21 changed files with 74 additions and 74 deletions
Download patch file Download diff file Expand all files Collapse all files

36
manual/advanced_topics/archos-flashing.tex
View file

@ -37,7 +37,7 @@ the Archos firmware to there, too.
\note{For now, the binary contained in the brand new player flash package does
contain Rockbox built from current CVS in the second image slot. This is to
lower the risk of flashing (at least one of the images will hopefully work) in
case you don't program a second image yourself in the first step. Of course the
case you do not program a second image yourself in the first step. Of course the
second image can be replaced like with the other models.}
There are two programming tools supplied:
@ -45,18 +45,18 @@ There are two programming tools supplied:
\begin{itemize}
\item The first one is called \fname{firmware\_flash.rock} and is used to
program the whole flash with a new content. You can also use it to revert
back to the original firmware you've hopefully backup-ed. In the ideal case,
back to the original firmware you have hopefully backup-ed. In the ideal case,
you'll need this tool only once. You can view this as "formatting" the flash
with the desired image structure.
\item The second one is called \fname{rockbox\_flash.rock} and is used to
reprogram only the second image. It won't touch any other byte, should be
reprogram only the second image. It will not touch any other byte, should be
safe to fool around with. If the programmed firmware is in-operational, you
can still use the \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} start with the Archos firmware and Rockbox booted
from disk to try better.
\end{itemize}
The non-user tools are in the \fname{flash} subdirectory of the CVS source
files. There's an authoring tool which composed the firmware file with the
files. There is an authoring tool which composed the firmware file with the
bootloader and the 2 images. The bootloader project, a firmware extraction
tool, the plugin sources, and the tools for the UART boot feature: a monitor
program for the box and a PC tool to drive it. Feel free to review the sources
@ -72,7 +72,7 @@ to bulletproof this code. The new firmware file is completely read before it
starts programming, there are a lot of sanity checks. If any fails, it will not
program. Before releasing this, we have checked the flow with exactly these
files supplied here, starting from the original firmware in flash. It worked
reliably, there's no reason why such low level code should behave different on
reliably, there is no reason why such low level code should behave different on
your box.
\opt{player}{
@ -86,11 +86,11 @@ your box.
}
}
There's one ultimate safety net to bring back boxes with even completely
There is one ultimate safety net to bring back boxes with even completely
garbled flash content: the \emph{UART} boot mod, which in turn requires the
serial mod. It can bring the dead back to life, in that it is possible to
re-flash independently from the outside, even if the flash is completely erased.
It has been used that during development, else Rockbox in flash wouldn't have
It has been used that during development, else Rockbox in flash would not have
been possible. Extensive development effort went into the exploitation of the
UART boot mod. Mechanically adept users with good soldering skills can easily
perform these mods. Others may feel uncomfortable using the first tool
@ -102,23 +102,23 @@ are unlikely to experience problems. The flash tools have been stable for quite
a while. Several users have used them extensively, even flashing while playing!
Although it worked, it is not the recommended method.
About the safety of operation: Since we have dual boot, you're not giving up
About the safety of operation: Since we have dual boot, you are not giving up
the Archos firmware. It is still there when you hold
\opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} during startup. So even if Rockbox from flash is not 100\% stable for
everyone, you can still use the box, re-flash the second image with an updated
Rockbox copy, etc.
The flash chip being used by Archos is specified for 100,000 cycles, so you don't need to worry about that wearing out.
The flash chip being used by Archos is specified for 100,000 cycles, so you do not need to worry about that wearing out.
\subsection{Requirements}
You need two things:
\begin{itemize}
\item The first is a \playername. Be sure you're using the correct package,
\item The first is a \playername. Be sure you are using the correct package,
they are different!
\item Second, you need an in-circuit programmable flash. \opt{recorder,recorderv2fm,player}{The older chips are not flashable.}\opt{ondio}{This should always
be flashable on Ondios, because Archos does itself provide flash updates for
these.} You can find out via Rockbox (\setting{Info $\rightarrow$ Debug $\rightarrow$ Hardware Info}). If the flash info gives you question marks (Flash M=?? D=??),
you're out of luck. The only chance then is to solder in the right chip
you are out of luck. The only chance then is to solder in the right chip
(SST39VF020), at best with the firmware already in. If the chip is blank,
you'll need the UART boot mod as well.
\end{itemize}
@ -151,11 +151,11 @@ Long version, step by step procedure:
This is purely for security reasons, flashing does not need more power than usual.
\item Run the \fname{firmware\_flash.rock} plugin. It again tells you about your
flash and the file it is going to program. After \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} it checks the file. Your
hardware mask value will be kept, it won't overwrite it. Hitting \opt{recorder,recorderv2fm}{\ButtonFTwo}\opt{ondio}{\ButtonUp}\opt{player}{\ButtonOn} gives you
a big warning. If we still didn't manage to scare you off, you can hit\opt{recorder,recorderv2fm}{\ButtonFThree}\opt{ondio}{\ButtonRight}\opt{player}{\ButtonRight} to actually program and verify. The programming takes just a few seconds. If
hardware mask value will be kept, it will not overwrite it. Hitting \opt{recorder,recorderv2fm}{\ButtonFTwo}\opt{ondio}{\ButtonUp}\opt{player}{\ButtonOn} gives you
a big warning. If we still did not manage to scare you off, you can hit\opt{recorder,recorderv2fm}{\ButtonFThree}\opt{ondio}{\ButtonRight}\opt{player}{\ButtonRight} to actually program and verify. The programming takes just a few seconds. If
the sanity check fails, you have the wrong kind of boot ROM and are out of luck
by now, sorry.
\item In the unlikely event that the programming should give you any error, don't
\item In the unlikely event that the programming should give you any error, do not
switch off the box! Otherwise you'll have seen it working for the last time.
While Rockbox is still in DRAM and operational, we could upgrade the plugin via
USB and try again. If you switch it off, it is gone.
@ -188,9 +188,9 @@ Long version:
The second image is the working copy, the \fname{rockbox\_flash.rock} plugin from
this package re-programs it. The plugins needs to be consistent with the Rockbox
plugin API version, otherwise it will detect mismatch and won't run.
plugin API version, otherwise it will detect mismatch and will not run.
It requires an exotic input, a UCL-compressed image, because that's the internal
It requires an exotic input, a UCL-compressed image, because that is the internal
format. UCL is a nice open-source compression library. The decompression is very
fast and less than a page of C-code. The efficiency is even better than Zip with
maximum compression, reduces file size to about 58\% of the original size. For
@ -212,7 +212,7 @@ Here are the steps:
content to the USB drive, replacing the old.
\item Force a disk boot by holding \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} during power-up, or at least rolo into
the new Rockbox version by \emph{Playing} the \fname{ajbrec.ajz}/fname{archos.mod} file. This may not always be necessary, but it is better to first run the
version you're about to flash. It is required if you are currently running
version you are about to flash. It is required if you are currently running
RomBox.
\item Just \emph{play} the \fname{.ucl} file in the \fname{.rockbox} directory,
this will kick off the \fname{rockbox\_flash.rock} plugin. It is a bit similar
@ -229,7 +229,7 @@ and can run directly from flash ROM, saving some RAM. The second way is the newe
and now preferred one. Use this if available.
If you like or have to, you can also flash the Archos image as the second one.
E.g. in case Rockbox from flash doesn't work for you. This way you keep the dual
E.g. in case Rockbox from flash does not work for you. This way you keep the dual
bootloader and you can easily try different later. The \fname{.ucl} of the Archos
firmware is included in the package.

4
manual/advanced_topics/main.tex
View file

@ -380,7 +380,7 @@ Example of a configuration file:
When your \dap{} powers on, it loads the Archos firmware in ROM, which
automatically checks your \daps{} root directory for a file named
\firmwarefilename. Note that Archos firmware can only read the first
ten characters of each filename in this process, so don't rename your old
ten characters of each filename in this process, so do not rename your old
firmware files with names like \firmwarefilename.\fname{old} and so on,
because it is possible that the \dap{} will load a file other than the one
you intended.
@ -398,6 +398,6 @@ You just ``play'' a file with the extension %
This can be used to test new firmware versions without deleting your
current version.
\opt{gigabeat}{\note{This feature doesn't work on the gigabeat currently.}}
\opt{gigabeat}{\note{This feature does not work on the gigabeat currently.}}
\opt{archos}{\input{advanced_topics/archos-flashing.tex}}

18
manual/appendix/appendix.tex
View file

@ -19,7 +19,7 @@ For open bug reports refer to
\subsection{Rules for submitting new bug reports}
\begin{enumerate}
\item Check that the bug hasn't already been reported
\item Check that the bug has not already been reported
\item Always include the following information in your bug report:
\end{enumerate}
@ -40,9 +40,9 @@ For open feature requests refer to
\subsection{Rules for submitting a new feature request}
\begin{enumerate}
\item Check that the feature hasn't already been requested.
\item Check that the feature has not already been requested.
Duplicates are really boring!
\item Check that the feature hasn't already been implemented.
\item Check that the feature has not already been implemented.
Download the latest current/daily build and/or search the mail list archive.
\item Check that the feature is possible to implement (see \reference{ref:NODO}).
\end{enumerate}
@ -70,7 +70,7 @@ The recording hardware (the MAS) does not allow us to do this
The Archos Multimedia is a completely different beast. It is an entirely
different architecture, different CPU and upgrading the software is done
a completely different way. We do not wish to venture into this. Others
may do so. We won't.
may do so. We will not.
\item Multi{}-band (or graphic) equaliser\\
We cannot access information for that kind of visualisation from the MP3
decoding hardware.
@ -79,11 +79,11 @@ The recording hardware (the MAS) does not allow us to do this
\item Change tempo of a song without changing pitch!\\
The MP3 decoding hardware does not allow this.
\item Graphic frequency (spectrum analyser!)\\
We can't access the audio waveform from the MP3 decoder so we can't analyse
We cannot access the audio waveform from the MP3 decoder so we cannot analyse
it. Even if we had access to it, the CPU would probably be too slow to
perform the analysis anyway.
\item Cool sound effects!\\
Adding new sound effects requires reprogramming the MAS chip, and we can't
Adding new sound effects requires reprogramming the MAS chip, and we cannot
do that. The MAS chip is programmable, but we have no access to the chip
documentation.
}
@ -104,7 +104,7 @@ The recording hardware (the MAS) does not allow us to do this
support for more file systems will just take away valuable ram for
unnecessary features. You can partition your \dap{} fine, just make sure
the first one is FAT32 and then make the other ones whatever file system
you want. Just don't expect Rockbox to understand them.
you want. Just do not expect Rockbox to understand them.
\item Add scandisk{}-like features!\\
It would be a very slow operation that would drain the batteries and
take a lot of useful ram for something that is much better and faster
@ -112,7 +112,7 @@ The recording hardware (the MAS) does not allow us to do this
\end{itemize}
\chapter{Changelog}
\section{What's new since v2.5?}
\section{What is new since v2.5?}
Changes in version 2.5
\chapter{Credits}
@ -128,4 +128,4 @@ People that have contributed to the project, one way or another. Friends!
\input{appendix/fdl.tex}
\newpage
\section{The GNU General Public License}
\input{appendix/gpl-2.0.tex}
\input{appendix/gpl-2.0.tex}

8
manual/configure_rockbox/display_options.tex
View file

@ -150,7 +150,7 @@
line length.
\opt{HAVE_LCD_BITMAP}{
\item[Screen Scrolls Out of View:]
On lists with long entries that don't fit on the screen using
On lists with long entries that do not fit on the screen using
\opt{recorder,recorderv2fm,h1xx,h300}{\ButtonOn+\ButtonRight/
\ButtonLeft}\opt{ondio}{\ButtonMenu+\ButtonRight/\ButtonLeft}
the complete content will be scrolled right/left. With this option set to
@ -239,13 +239,13 @@
\end{description}
}
\item[Default Codepage:]
A codepage describes the way extended characters that aren't available
within the ASCII character set are encoded. ID3v1 tags don't have a
A codepage describes the way extended characters that are not available
within the ASCII character set are encoded. ID3v1 tags do not have a
codepage encoding contained so Rockbox needs to know what encoding has
been used when generating these tags. This should be ``ISO-8859-1'' but
to support languages outside Western Europe most applications use
the setting of your operating system instead. If your operating system
uses a different codepage and you're getting garbled extended characters
uses a different codepage and you are getting garbled extended characters
you should adjust this settings. In most cases sticking to
``ISO-8859-1'' would be sufficient.
\end{description}

2
manual/configure_rockbox/sound_settings.tex
View file

@ -175,7 +175,7 @@ change to customise your listening experience.
The practical upshot of this is that MDB produces a more authentic sounding
bass by tricking the brain into believing it is hearing tones that the
headphones or speakers aren't capable of reproducing. Try it and see
headphones or speakers are not capable of reproducing. Try it and see
what you think.
The MDB parameters are as follows:

6
manual/getting_started/h10_install.tex
View file

@ -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 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.
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 does not 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 Rename the \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}} file to \fname{OF.mi4} 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 downloaded in step 1 to \fname{H10EMP.mi4}.}}
\opt{h10_5gb}{\note{If you have a Pure model \playertype{} (which does not 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 directories.}
\note{If you cannot see the \fname{System} directory, you will need to make sure your operating system is configured to show hidden files and directories.}
\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}

10
manual/getting_started/installation.tex
View file

@ -13,7 +13,7 @@
There are two ways of installing Rockbox: automated and manual. While the
manual way is older, more tested and proven to work correctly, the
automated installation is based on a nice graphical application that does
almost everything that's needed for you. It is still important that you have
almost everything that is needed for you. It is still important that you have
an overview of the installation process to be able to select the correct
installation options.
@ -169,7 +169,7 @@ filesystem.}
detected value, especially if you experience problems with Rockbox.}}
\note{Rockbox Utility currently lacks some guiding messages. Please have a
look at the manual installation instructions if you're stuck
look at the manual installation instructions if you are stuck
during installation.}
\subsection{Manual Installation}
@ -346,7 +346,7 @@ use.
}
\section{Updating Rockbox}
Updating Rockbox is easy even if you don't use the Rockbox Utility.
Updating Rockbox is easy even if you do not use the Rockbox Utility.
Download a Rockbox build.
(The latest release of the Rockbox software will always be available from
\url{http://www.rockbox.org/download/}). Unzip the build to the root directory
@ -361,9 +361,9 @@ The new build will be installed over your current build.
\subsection{Automatic Uninstallation}
You can uninstall Rockbox automatically by using Rockbox Utility. If you
installed Rockbox manually you can still use Rockbox Utility for uninstallation
but won't be able to do this selectively.
but will not be able to do this selectively.
\opt{h1xx,h300}{\note{Rockbox Utility can't uninstall the bootloader due to
\opt{h1xx,h300}{\note{Rockbox Utility cannot uninstall the bootloader due to
the fact that it requires a flashing procedure. To uninstall the bootloader
completely follow the manual uninstallation instructions below.}}

4
manual/getting_started/ipod_install.tex
View file

@ -67,7 +67,7 @@ should see the message ``[INFO] Bootloader installed successfully.'' Press
ENTER again to exit ipodpatcher and then quit the Terminal application.
\item \warn{If you received a ``Resource busy'' error from
ipodpatcher, then this means you didn't complete step
ipodpatcher, then this means you did not complete step
\ref{subsec:macos_umount}. Go back to Disk Utility, unmount your
\dap{} and then run ipodpatcher again.}
@ -92,7 +92,7 @@ package -- see \reference{sec:installing_fonts} for more information.
\download{bootloader/ipod/ipodpatcher/linux32x86/ipodpatcher} (32-bit x86
binary) or \download{bootloader/ipod/ipodpatcher/linux64amd64/ipodpatcher}
(64-bit amd64 binary). You can save this anywhere you wish, but the next
steps will assume you've saved it in your home directory.
steps will assume you have saved it in your home directory.
\item Attach your \dap{} to your computer.

2
manual/getting_started/iriver_install.tex
View file

@ -96,7 +96,7 @@
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
itself hasn't been loaded this is also a simple way of updating Rockbox.
itself has not been loaded this is also a simple way of updating Rockbox.
After the disconnect the bootloader will load the updated version of
Rockbox.
}

12
manual/getting_started/main.tex
View file

@ -32,7 +32,7 @@ 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 information you're searching for on the Rockbox
If you cannot find the information you are 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
@ -74,15 +74,15 @@ are used:
or indicate a possible ``weirdness'' in rockbox that would be explained.
}
\warn{This is a warning. In contrast to notes mentioned above, a warning
should be taken more seriously. While ignoring notes won't cause any serious
damage ignoring warnings \emph{could} cause serious damage. If you're new to
should be taken more seriously. While ignoring notes will not cause any serious
damage ignoring warnings \emph{could} cause serious damage. If you are new to
rockbox you should really read the warnings before doing anything that is
warned about.
}
\blind{This icon marks a section that are intended especially for the blind
and visually impaired. As they can't
read the manual in the same way sighted people can do we've added some
additional descriptions. If you aren't blind or visually impaired you most
and visually impaired. As they cannot
read the manual in the same way sighted people can do we have added some
additional descriptions. If you are not blind or visually impaired you most
likely can completely skip these blocks. To make this easier, there is an
icon shown in the margin on the right.
}

4
manual/getting_started/sansa_install.tex
View file

@ -60,7 +60,7 @@ should see the message ``[INFO] Bootloader installed successfully.'' Press
ENTER again to exit sansapatcher and then quit the Terminal application.
\item \warn{If you received a ``Resource busy'' error from
sansapatcher, then this means you didn't complete step
sansapatcher, then this means you did not complete step
\ref{subsec:macos_umount}. Go back to Disk Utility, unmount your
\dap{} and then run sansapatcher again.}
@ -77,7 +77,7 @@ Wait for it to connect, and then eject and unplug it in the normal way.
\download{bootloader/sandisk-sansa/sansapatcher/linux32x86/sansapatcher} (32-bit x86
binary) or \download{bootloader/sandisk-sansa/sansapatcher/linux64amd64/sansapatcher}
(64-bit amd64 binary). You can save this anywhere you wish, but the next
steps will assume you've saved it in your home directory.
steps will assume you have saved it in your home directory.
\item Attach your \dap{} to your computer.

2
manual/main_menu/fmradio.tex
View file

@ -3,7 +3,7 @@
\opt{RECORDER_PAD}{
\note{The early V2 models were in fact FM Recorders in disguise,
so they had the FM radio still mounted. Rockbox enables it if present -
in case this menu doesn't show on your unit you can skip this chapter.\\}
in case this menu does not show on your unit you can skip this chapter.\\}
}
\opt{sansa}{
\note{Not all Sansas have a radio receiver. Generally all american models do,

8
manual/plugins/alpinecdc.tex
View file

@ -13,11 +13,11 @@ Hookup to Archos works by connecting the headphone output including the remote
pin (you need a 4-ring 3.5 mm plug for that) to the changer jack of the radio.
M-Bus radios have a DIN-style circular jack with 8 pins (7 in a $\sim$ 270 degree
circle, one in the center). A standard 5-pin DIN plug is OK for this, since we
don't use the other (power) pins.
do not use the other (power) pins.
As OEM, they shuffled the pins around a bit, better check first if it is not
genuine Alpine. The bus pin is pulled high to 12 volts with a $\sim$ 2kOhm resistor,
pulses driven low. Because it's open collector, this is not harmful to the
pulses driven low. Because it is open collector, this is not harmful to the
Archos.\\
ASCII art of the 4-pin headphone plug:
\begin{verbatim}
@ -28,12 +28,12 @@ ASCII art of the 4-pin headphone plug:
|_| ground -> Alpine pin 2 + 3
\end{verbatim}
The remote pin can be programmed bidirectional, that's the reason this works.
The remote pin can be programmed bidirectional, that is the reason this works.
Very luckily the M-Bus uses a single wire communication and the two radios I
tried are happy with the 3.3 Volt level the Arcos can deliver. So the
connection is a simple cable! For all protocols requiring more lines, an
external controller would be necessary.
\note{Archos FMs don't have the remote pin internally connected, but
\note{Archos FMs do not have the remote pin internally connected, but
one unit that was opened was internally prepared for it, a matter of closing a
bridge.}

4
manual/plugins/solitaire.tex
View file

@ -3,7 +3,7 @@
This is the classic Klondike solitaire game for Rockbox.
This is probably the best-known solitaire in the world. Many people
don't even realize that other games exist. Though the name may not
do not even realize that other games exist. Though the name may not
be familiar, the game itself certainly is. This is due in no small
part to Microsoft's inclusion of the the game in every version of
Windows. Though popular, the odds of winning are rather low, perhaps
@ -72,4 +72,4 @@ visit\\
\opt{IAUDIO_X5_PAD,IRIVER_H10_PAD,SANSA_E200_PAD,SANSA_C200_PAD,GIGABEAT_PAD}{\ButtonPower}
& Show menu\\
\end{btnmap}
\end{table}
\end{table}

4
manual/plugins/split_editor.tex
View file

@ -97,7 +97,7 @@ The whole process of splitting an mp3 file consists of three steps:
tuning the split indicator position at the end of a recording.
\item
\includegraphics[width=0.53cm]{plugins/images/icon-splitedit-loop-4}
Playback doesn't loop, the borders of the visible
Playback does not loop, the borders of the visible
area as well as the split point indicator are ignored. This mode is
best used when playing the song outside of the borders of the displayed
region.
@ -154,7 +154,7 @@ In the save dialogue it is possible to specify which of the files you
want to save and their names. When finished, select
``Save'' and the files will be written to
disk. Note that files can not be overwritten, so filenames that
don't exist yet must be chosen. If unsure whether the
do not exist yet must be chosen. If unsure whether the
file already exists simply try to save it. If another file with this
name exists the dialogue will return and you can choose another
filename

2
manual/plugins/text_editor.tex
View file

@ -16,7 +16,7 @@ the \setting{Virtual Keyboard} (see \reference{sec:virtual_keyboard}).
\item When finished editing exit the Text Editor. You'll be shown a list of
save options.
\end{itemize}
\note{When you haven't changed the file the Text Editor will quit immediately.}
\note{When you have not changed the file the Text Editor will quit immediately.}
\begin{table}
\begin{btnmap}{}{}

4
manual/plugins/wavplay.tex
View file

@ -10,8 +10,8 @@ plugin automatically and the Wavplay screen
appears. This screen gives information about samplerate and length of the
playing file.
\note{Seeking within the \fname{.wav}-file or changing the volume once the
plugin is running isn't possible. Wavplay uses the sound settings that were
plugin is running is not possible. Wavplay uses the sound settings that were
used before (except for pitch).}
The only action that can be performed is to stop by pressing \ButtonOff, and
Wavplay will be exited and you are returned to the filebrowser. If the end of
the file has been reached, you will also be returned to the filebrowser.
the file has been reached, you will also be returned to the filebrowser.

8
manual/rockbox_interface/main.tex
View file

@ -191,7 +191,7 @@ paragraph.
On the bottom of the unit is the connector for the
\playerman{} subpack or dock. On the top of the unit is a charge
indicator light, which may feel a bit like a button, but isn't.
indicator light, which may feel a bit like a button, but is not.
From the top of the \dap{} on the left hand side is the headphone socket, then the
remote connector. Below this is a cover which protects the \opt{x5}{USB host
@ -329,7 +329,7 @@ To turn on and off your Rockbox enabled \dap{} use the following keys:
Rockbox has a dual-boot feature. It loads the original firmware from
the file \fname{/System/OF.mi4}. To boot into the original firmware,
press and hold the \ButtonLeft{} button while turning on the player.
\note{The iriver firmware doesn't shut down properly when you turn it off,
\note{The iriver firmware does not shut down properly when you turn it off,
it only goes to sleep. To get back into Rockbox when exiting from the
iriver firmware, you will need to reset the player by \opt{h10}{inserting a
pin in the reset hole}\opt{h10_5gb}{taking out battery}.}
@ -374,7 +374,7 @@ In list views you can go back one step with \ActionTreeParentDirectory.
Rockbox is playlist oriented. This means that every time you play an audio file,
a so-called ``dynamic playlist'' is generated, unless you play a saved
playlist. You can modify the dynamic playlist while playing and also save
it to a file. If you don't want to use playlists you can simply play your
it to a file. If you do not want to use playlists you can simply play your
files directory based.
Playlists are covered in detail in \reference{ref:working_with_playlists}.
@ -390,7 +390,7 @@ The contents of the context menu vary, depending on the situation it gets
called. The context menu itself presents you with some operations you can
perform with the currently highlighted file. In the file browser this is
the file (or directory) that is highlighted by the cursor. From the WPS this is
the currently playing file. Also there are some actions that don't apply
the currently playing file. Also there are some actions that do not apply
to the current file but refer to the screen from which the context menu
gets called. One example is the playback menu, which can be called using
the context menu from within the WPS.

2
manual/rockbox_interface/tagcache.tex
View file

@ -108,7 +108,7 @@ $\rightarrow$ System $\rightarrow$ Limits}) in order to view long lists of
tracks in the ID3 database browser.\\
There is no option to turn off database completely. If you do not want
to use it just don't do the initial build of the database and do not load it
to use it just do not do the initial build of the database and do not load it
to RAM.}
%
\begin{table}

4
manual/rockbox_interface/wps.tex
View file

@ -205,8 +205,8 @@ function in the \setting{File Context Menu}.
The \setting{Pitch Screen} allows you to change the pitch and (at the same
time) the playback speed of your \dap. The pitch value can be adjusted
between 50\% and 200\%. 50\% means half the normal playback speed and the
pitch that's an octave lower than the normal pitch. 200\% means double
playback speed and the pitch that's an octave higher than the normal pitch.
pitch that is an octave lower than the normal pitch. 200\% means double
playback speed and the pitch that is an octave higher than the normal pitch.
It is not possible to change the pitch without changing the playback speed and
vice versa. Changing the pitch can be done in two modes: procentual and
semitone. Initially (after the \dap{} is switched on), procentual mode

4
manual/working_with_playlists/main.tex
View file

@ -103,7 +103,7 @@ options:
\item [Insert last.] Add track(s) to end of playlist.
\item [Queue.] Queue is the same as Insert except queued tracks are
deleted immediately from the playlist after they've been played. Also,
deleted immediately from the playlist after they have been played. Also,
queued tracks are not saved to the playlist file (see
\reference{ref:playlistoptions}).
@ -159,7 +159,7 @@ select \setting{Save Current Playlist} or enter the
\setting{Save Current Playlist}.
Either method will bring you to the \setting{Virtual Keyboard} (see
\reference{sec:virtual_keyboard}), enter a filename for your playlist and
accept it and you're done.
accept it and you are done.
\subsection{Loading saved playlists}
\subsubsection{Through the \setting{File Browser}}