diff options
-rw-r--r-- | manual/advanced_topics/archos-flashing.tex | 36 | ||||
-rw-r--r-- | manual/advanced_topics/main.tex | 4 | ||||
-rw-r--r-- | manual/appendix/appendix.tex | 18 | ||||
-rw-r--r-- | manual/configure_rockbox/display_options.tex | 8 | ||||
-rw-r--r-- | manual/configure_rockbox/sound_settings.tex | 2 | ||||
-rw-r--r-- | manual/getting_started/h10_install.tex | 6 | ||||
-rw-r--r-- | manual/getting_started/installation.tex | 10 | ||||
-rw-r--r-- | manual/getting_started/ipod_install.tex | 4 | ||||
-rw-r--r-- | manual/getting_started/iriver_install.tex | 2 | ||||
-rw-r--r-- | manual/getting_started/main.tex | 12 | ||||
-rw-r--r-- | manual/getting_started/sansa_install.tex | 4 | ||||
-rw-r--r-- | manual/main_menu/fmradio.tex | 2 | ||||
-rw-r--r-- | manual/plugins/alpinecdc.tex | 8 | ||||
-rw-r--r-- | manual/plugins/solitaire.tex | 4 | ||||
-rw-r--r-- | manual/plugins/split_editor.tex | 4 | ||||
-rw-r--r-- | manual/plugins/text_editor.tex | 2 | ||||
-rw-r--r-- | manual/plugins/wavplay.tex | 4 | ||||
-rw-r--r-- | manual/rockbox_interface/main.tex | 8 | ||||
-rw-r--r-- | manual/rockbox_interface/tagcache.tex | 2 | ||||
-rw-r--r-- | manual/rockbox_interface/wps.tex | 4 | ||||
-rw-r--r-- | manual/working_with_playlists/main.tex | 4 |
21 files changed, 74 insertions, 74 deletions
diff --git a/manual/advanced_topics/archos-flashing.tex b/manual/advanced_topics/archos-flashing.tex index 747fd5c0a4..29133ae6c2 100644 --- a/manual/advanced_topics/archos-flashing.tex +++ b/manual/advanced_topics/archos-flashing.tex | |||
@@ -37,7 +37,7 @@ the Archos firmware to there, too. | |||
37 | \note{For now, the binary contained in the brand new player flash package does | 37 | \note{For now, the binary contained in the brand new player flash package does |
38 | contain Rockbox built from current CVS in the second image slot. This is to | 38 | contain Rockbox built from current CVS in the second image slot. This is to |
39 | lower the risk of flashing (at least one of the images will hopefully work) in | 39 | lower the risk of flashing (at least one of the images will hopefully work) in |
40 | case you don't program a second image yourself in the first step. Of course the | 40 | case you do not program a second image yourself in the first step. Of course the |
41 | second image can be replaced like with the other models.} | 41 | second image can be replaced like with the other models.} |
42 | 42 | ||
43 | There are two programming tools supplied: | 43 | There are two programming tools supplied: |
@@ -45,18 +45,18 @@ There are two programming tools supplied: | |||
45 | \begin{itemize} | 45 | \begin{itemize} |
46 | \item The first one is called \fname{firmware\_flash.rock} and is used to | 46 | \item The first one is called \fname{firmware\_flash.rock} and is used to |
47 | program the whole flash with a new content. You can also use it to revert | 47 | program the whole flash with a new content. You can also use it to revert |
48 | back to the original firmware you've hopefully backup-ed. In the ideal case, | 48 | back to the original firmware you have hopefully backup-ed. In the ideal case, |
49 | you'll need this tool only once. You can view this as "formatting" the flash | 49 | you'll need this tool only once. You can view this as "formatting" the flash |
50 | with the desired image structure. | 50 | with the desired image structure. |
51 | \item The second one is called \fname{rockbox\_flash.rock} and is used to | 51 | \item The second one is called \fname{rockbox\_flash.rock} and is used to |
52 | reprogram only the second image. It won't touch any other byte, should be | 52 | reprogram only the second image. It will not touch any other byte, should be |
53 | safe to fool around with. If the programmed firmware is in-operational, you | 53 | safe to fool around with. If the programmed firmware is in-operational, you |
54 | can still use the \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} start with the Archos firmware and Rockbox booted | 54 | can still use the \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} start with the Archos firmware and Rockbox booted |
55 | from disk to try better. | 55 | from disk to try better. |
56 | \end{itemize} | 56 | \end{itemize} |
57 | 57 | ||
58 | The non-user tools are in the \fname{flash} subdirectory of the CVS source | 58 | The non-user tools are in the \fname{flash} subdirectory of the CVS source |
59 | files. There's an authoring tool which composed the firmware file with the | 59 | files. There is an authoring tool which composed the firmware file with the |
60 | bootloader and the 2 images. The bootloader project, a firmware extraction | 60 | bootloader and the 2 images. The bootloader project, a firmware extraction |
61 | tool, the plugin sources, and the tools for the UART boot feature: a monitor | 61 | tool, the plugin sources, and the tools for the UART boot feature: a monitor |
62 | program for the box and a PC tool to drive it. Feel free to review the sources | 62 | 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 | |||
72 | starts programming, there are a lot of sanity checks. If any fails, it will not | 72 | starts programming, there are a lot of sanity checks. If any fails, it will not |
73 | program. Before releasing this, we have checked the flow with exactly these | 73 | program. Before releasing this, we have checked the flow with exactly these |
74 | files supplied here, starting from the original firmware in flash. It worked | 74 | files supplied here, starting from the original firmware in flash. It worked |
75 | reliably, there's no reason why such low level code should behave different on | 75 | reliably, there is no reason why such low level code should behave different on |
76 | your box. | 76 | your box. |
77 | 77 | ||
78 | \opt{player}{ | 78 | \opt{player}{ |
@@ -86,11 +86,11 @@ your box. | |||
86 | } | 86 | } |
87 | } | 87 | } |
88 | 88 | ||
89 | There's one ultimate safety net to bring back boxes with even completely | 89 | There is one ultimate safety net to bring back boxes with even completely |
90 | garbled flash content: the \emph{UART} boot mod, which in turn requires the | 90 | garbled flash content: the \emph{UART} boot mod, which in turn requires the |
91 | serial mod. It can bring the dead back to life, in that it is possible to | 91 | serial mod. It can bring the dead back to life, in that it is possible to |
92 | re-flash independently from the outside, even if the flash is completely erased. | 92 | re-flash independently from the outside, even if the flash is completely erased. |
93 | It has been used that during development, else Rockbox in flash wouldn't have | 93 | It has been used that during development, else Rockbox in flash would not have |
94 | been possible. Extensive development effort went into the exploitation of the | 94 | been possible. Extensive development effort went into the exploitation of the |
95 | UART boot mod. Mechanically adept users with good soldering skills can easily | 95 | UART boot mod. Mechanically adept users with good soldering skills can easily |
96 | perform these mods. Others may feel uncomfortable using the first tool | 96 | 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 | |||
102 | a while. Several users have used them extensively, even flashing while playing! | 102 | a while. Several users have used them extensively, even flashing while playing! |
103 | Although it worked, it is not the recommended method. | 103 | Although it worked, it is not the recommended method. |
104 | 104 | ||
105 | About the safety of operation: Since we have dual boot, you're not giving up | 105 | About the safety of operation: Since we have dual boot, you are not giving up |
106 | the Archos firmware. It is still there when you hold | 106 | the Archos firmware. It is still there when you hold |
107 | \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} during startup. So even if Rockbox from flash is not 100\% stable for | 107 | \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} during startup. So even if Rockbox from flash is not 100\% stable for |
108 | everyone, you can still use the box, re-flash the second image with an updated | 108 | everyone, you can still use the box, re-flash the second image with an updated |
109 | Rockbox copy, etc. | 109 | Rockbox copy, etc. |
110 | 110 | ||
111 | The flash chip being used by Archos is specified for 100,000 cycles, so you don't need to worry about that wearing out. | 111 | The flash chip being used by Archos is specified for 100,000 cycles, so you do not need to worry about that wearing out. |
112 | 112 | ||
113 | \subsection{Requirements} | 113 | \subsection{Requirements} |
114 | You need two things: | 114 | You need two things: |
115 | \begin{itemize} | 115 | \begin{itemize} |
116 | \item The first is a \playername. Be sure you're using the correct package, | 116 | \item The first is a \playername. Be sure you are using the correct package, |
117 | they are different! | 117 | they are different! |
118 | \item Second, you need an in-circuit programmable flash. \opt{recorder,recorderv2fm,player}{The older chips are not flashable.}\opt{ondio}{This should always | 118 | \item Second, you need an in-circuit programmable flash. \opt{recorder,recorderv2fm,player}{The older chips are not flashable.}\opt{ondio}{This should always |
119 | be flashable on Ondios, because Archos does itself provide flash updates for | 119 | be flashable on Ondios, because Archos does itself provide flash updates for |
120 | 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=??), | 120 | 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=??), |
121 | you're out of luck. The only chance then is to solder in the right chip | 121 | you are out of luck. The only chance then is to solder in the right chip |
122 | (SST39VF020), at best with the firmware already in. If the chip is blank, | 122 | (SST39VF020), at best with the firmware already in. If the chip is blank, |
123 | you'll need the UART boot mod as well. | 123 | you'll need the UART boot mod as well. |
124 | \end{itemize} | 124 | \end{itemize} |
@@ -151,11 +151,11 @@ Long version, step by step procedure: | |||
151 | This is purely for security reasons, flashing does not need more power than usual. | 151 | This is purely for security reasons, flashing does not need more power than usual. |
152 | \item Run the \fname{firmware\_flash.rock} plugin. It again tells you about your | 152 | \item Run the \fname{firmware\_flash.rock} plugin. It again tells you about your |
153 | 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 | 153 | 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 |
154 | hardware mask value will be kept, it won't overwrite it. Hitting \opt{recorder,recorderv2fm}{\ButtonFTwo}\opt{ondio}{\ButtonUp}\opt{player}{\ButtonOn} gives you | 154 | hardware mask value will be kept, it will not overwrite it. Hitting \opt{recorder,recorderv2fm}{\ButtonFTwo}\opt{ondio}{\ButtonUp}\opt{player}{\ButtonOn} gives you |
155 | 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 | 155 | 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 |
156 | the sanity check fails, you have the wrong kind of boot ROM and are out of luck | 156 | the sanity check fails, you have the wrong kind of boot ROM and are out of luck |
157 | by now, sorry. | 157 | by now, sorry. |
158 | \item In the unlikely event that the programming should give you any error, don't | 158 | \item In the unlikely event that the programming should give you any error, do not |
159 | switch off the box! Otherwise you'll have seen it working for the last time. | 159 | switch off the box! Otherwise you'll have seen it working for the last time. |
160 | While Rockbox is still in DRAM and operational, we could upgrade the plugin via | 160 | While Rockbox is still in DRAM and operational, we could upgrade the plugin via |
161 | USB and try again. If you switch it off, it is gone. | 161 | USB and try again. If you switch it off, it is gone. |
@@ -188,9 +188,9 @@ Long version: | |||
188 | 188 | ||
189 | The second image is the working copy, the \fname{rockbox\_flash.rock} plugin from | 189 | The second image is the working copy, the \fname{rockbox\_flash.rock} plugin from |
190 | this package re-programs it. The plugins needs to be consistent with the Rockbox | 190 | this package re-programs it. The plugins needs to be consistent with the Rockbox |
191 | plugin API version, otherwise it will detect mismatch and won't run. | 191 | plugin API version, otherwise it will detect mismatch and will not run. |
192 | 192 | ||
193 | It requires an exotic input, a UCL-compressed image, because that's the internal | 193 | It requires an exotic input, a UCL-compressed image, because that is the internal |
194 | format. UCL is a nice open-source compression library. The decompression is very | 194 | format. UCL is a nice open-source compression library. The decompression is very |
195 | fast and less than a page of C-code. The efficiency is even better than Zip with | 195 | fast and less than a page of C-code. The efficiency is even better than Zip with |
196 | maximum compression, reduces file size to about 58\% of the original size. For | 196 | maximum compression, reduces file size to about 58\% of the original size. For |
@@ -212,7 +212,7 @@ Here are the steps: | |||
212 | content to the USB drive, replacing the old. | 212 | content to the USB drive, replacing the old. |
213 | \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 | 213 | \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 |
214 | 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 | 214 | 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 |
215 | version you're about to flash. It is required if you are currently running | 215 | version you are about to flash. It is required if you are currently running |
216 | RomBox. | 216 | RomBox. |
217 | \item Just \emph{play} the \fname{.ucl} file in the \fname{.rockbox} directory, | 217 | \item Just \emph{play} the \fname{.ucl} file in the \fname{.rockbox} directory, |
218 | this will kick off the \fname{rockbox\_flash.rock} plugin. It is a bit similar | 218 | 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 | |||
229 | and now preferred one. Use this if available. | 229 | and now preferred one. Use this if available. |
230 | 230 | ||
231 | If you like or have to, you can also flash the Archos image as the second one. | 231 | If you like or have to, you can also flash the Archos image as the second one. |
232 | E.g. in case Rockbox from flash doesn't work for you. This way you keep the dual | 232 | E.g. in case Rockbox from flash does not work for you. This way you keep the dual |
233 | bootloader and you can easily try different later. The \fname{.ucl} of the Archos | 233 | bootloader and you can easily try different later. The \fname{.ucl} of the Archos |
234 | firmware is included in the package. | 234 | firmware is included in the package. |
235 | 235 | ||
diff --git a/manual/advanced_topics/main.tex b/manual/advanced_topics/main.tex index 7d2909d6ab..ae50eb9527 100644 --- a/manual/advanced_topics/main.tex +++ b/manual/advanced_topics/main.tex | |||
@@ -380,7 +380,7 @@ Example of a configuration file: | |||
380 | When your \dap{} powers on, it loads the Archos firmware in ROM, which | 380 | When your \dap{} powers on, it loads the Archos firmware in ROM, which |
381 | automatically checks your \daps{} root directory for a file named | 381 | automatically checks your \daps{} root directory for a file named |
382 | \firmwarefilename. Note that Archos firmware can only read the first | 382 | \firmwarefilename. Note that Archos firmware can only read the first |
383 | ten characters of each filename in this process, so don't rename your old | 383 | ten characters of each filename in this process, so do not rename your old |
384 | firmware files with names like \firmwarefilename.\fname{old} and so on, | 384 | firmware files with names like \firmwarefilename.\fname{old} and so on, |
385 | because it is possible that the \dap{} will load a file other than the one | 385 | because it is possible that the \dap{} will load a file other than the one |
386 | you intended. | 386 | you intended. |
@@ -398,6 +398,6 @@ You just ``play'' a file with the extension % | |||
398 | This can be used to test new firmware versions without deleting your | 398 | This can be used to test new firmware versions without deleting your |
399 | current version. | 399 | current version. |
400 | 400 | ||
401 | \opt{gigabeat}{\note{This feature doesn't work on the gigabeat currently.}} | 401 | \opt{gigabeat}{\note{This feature does not work on the gigabeat currently.}} |
402 | 402 | ||
403 | \opt{archos}{\input{advanced_topics/archos-flashing.tex}} | 403 | \opt{archos}{\input{advanced_topics/archos-flashing.tex}} |
diff --git a/manual/appendix/appendix.tex b/manual/appendix/appendix.tex index 6965d26533..1ec12c8f34 100644 --- a/manual/appendix/appendix.tex +++ b/manual/appendix/appendix.tex | |||
@@ -19,7 +19,7 @@ For open bug reports refer to | |||
19 | \subsection{Rules for submitting new bug reports} | 19 | \subsection{Rules for submitting new bug reports} |
20 | 20 | ||
21 | \begin{enumerate} | 21 | \begin{enumerate} |
22 | \item Check that the bug hasn't already been reported | 22 | \item Check that the bug has not already been reported |
23 | \item Always include the following information in your bug report: | 23 | \item Always include the following information in your bug report: |
24 | \end{enumerate} | 24 | \end{enumerate} |
25 | 25 | ||
@@ -40,9 +40,9 @@ For open feature requests refer to | |||
40 | \subsection{Rules for submitting a new feature request} | 40 | \subsection{Rules for submitting a new feature request} |
41 | 41 | ||
42 | \begin{enumerate} | 42 | \begin{enumerate} |
43 | \item Check that the feature hasn't already been requested. | 43 | \item Check that the feature has not already been requested. |
44 | Duplicates are really boring! | 44 | Duplicates are really boring! |
45 | \item Check that the feature hasn't already been implemented. | 45 | \item Check that the feature has not already been implemented. |
46 | Download the latest current/daily build and/or search the mail list archive. | 46 | Download the latest current/daily build and/or search the mail list archive. |
47 | \item Check that the feature is possible to implement (see \reference{ref:NODO}). | 47 | \item Check that the feature is possible to implement (see \reference{ref:NODO}). |
48 | \end{enumerate} | 48 | \end{enumerate} |
@@ -70,7 +70,7 @@ The recording hardware (the MAS) does not allow us to do this | |||
70 | The Archos Multimedia is a completely different beast. It is an entirely | 70 | The Archos Multimedia is a completely different beast. It is an entirely |
71 | different architecture, different CPU and upgrading the software is done | 71 | different architecture, different CPU and upgrading the software is done |
72 | a completely different way. We do not wish to venture into this. Others | 72 | a completely different way. We do not wish to venture into this. Others |
73 | may do so. We won't. | 73 | may do so. We will not. |
74 | \item Multi{}-band (or graphic) equaliser\\ | 74 | \item Multi{}-band (or graphic) equaliser\\ |
75 | We cannot access information for that kind of visualisation from the MP3 | 75 | We cannot access information for that kind of visualisation from the MP3 |
76 | decoding hardware. | 76 | decoding hardware. |
@@ -79,11 +79,11 @@ The recording hardware (the MAS) does not allow us to do this | |||
79 | \item Change tempo of a song without changing pitch!\\ | 79 | \item Change tempo of a song without changing pitch!\\ |
80 | The MP3 decoding hardware does not allow this. | 80 | The MP3 decoding hardware does not allow this. |
81 | \item Graphic frequency (spectrum analyser!)\\ | 81 | \item Graphic frequency (spectrum analyser!)\\ |
82 | We can't access the audio waveform from the MP3 decoder so we can't analyse | 82 | We cannot access the audio waveform from the MP3 decoder so we cannot analyse |
83 | it. Even if we had access to it, the CPU would probably be too slow to | 83 | it. Even if we had access to it, the CPU would probably be too slow to |
84 | perform the analysis anyway. | 84 | perform the analysis anyway. |
85 | \item Cool sound effects!\\ | 85 | \item Cool sound effects!\\ |
86 | Adding new sound effects requires reprogramming the MAS chip, and we can't | 86 | Adding new sound effects requires reprogramming the MAS chip, and we cannot |
87 | do that. The MAS chip is programmable, but we have no access to the chip | 87 | do that. The MAS chip is programmable, but we have no access to the chip |
88 | documentation. | 88 | documentation. |
89 | } | 89 | } |
@@ -104,7 +104,7 @@ The recording hardware (the MAS) does not allow us to do this | |||
104 | support for more file systems will just take away valuable ram for | 104 | support for more file systems will just take away valuable ram for |
105 | unnecessary features. You can partition your \dap{} fine, just make sure | 105 | unnecessary features. You can partition your \dap{} fine, just make sure |
106 | the first one is FAT32 and then make the other ones whatever file system | 106 | the first one is FAT32 and then make the other ones whatever file system |
107 | you want. Just don't expect Rockbox to understand them. | 107 | you want. Just do not expect Rockbox to understand them. |
108 | \item Add scandisk{}-like features!\\ | 108 | \item Add scandisk{}-like features!\\ |
109 | It would be a very slow operation that would drain the batteries and | 109 | It would be a very slow operation that would drain the batteries and |
110 | take a lot of useful ram for something that is much better and faster | 110 | 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 | |||
112 | \end{itemize} | 112 | \end{itemize} |
113 | 113 | ||
114 | \chapter{Changelog} | 114 | \chapter{Changelog} |
115 | \section{What's new since v2.5?} | 115 | \section{What is new since v2.5?} |
116 | Changes in version 2.5 | 116 | Changes in version 2.5 |
117 | 117 | ||
118 | \chapter{Credits} | 118 | \chapter{Credits} |
@@ -128,4 +128,4 @@ People that have contributed to the project, one way or another. Friends! | |||
128 | \input{appendix/fdl.tex} | 128 | \input{appendix/fdl.tex} |
129 | \newpage | 129 | \newpage |
130 | \section{The GNU General Public License} | 130 | \section{The GNU General Public License} |
131 | \input{appendix/gpl-2.0.tex} \ No newline at end of file | 131 | \input{appendix/gpl-2.0.tex} |
diff --git a/manual/configure_rockbox/display_options.tex b/manual/configure_rockbox/display_options.tex index 16fb15d186..7906d05581 100644 --- a/manual/configure_rockbox/display_options.tex +++ b/manual/configure_rockbox/display_options.tex | |||
@@ -150,7 +150,7 @@ | |||
150 | line length. | 150 | line length. |
151 | \opt{HAVE_LCD_BITMAP}{ | 151 | \opt{HAVE_LCD_BITMAP}{ |
152 | \item[Screen Scrolls Out of View:] | 152 | \item[Screen Scrolls Out of View:] |
153 | On lists with long entries that don't fit on the screen using | 153 | On lists with long entries that do not fit on the screen using |
154 | \opt{recorder,recorderv2fm,h1xx,h300}{\ButtonOn+\ButtonRight/ | 154 | \opt{recorder,recorderv2fm,h1xx,h300}{\ButtonOn+\ButtonRight/ |
155 | \ButtonLeft}\opt{ondio}{\ButtonMenu+\ButtonRight/\ButtonLeft} | 155 | \ButtonLeft}\opt{ondio}{\ButtonMenu+\ButtonRight/\ButtonLeft} |
156 | the complete content will be scrolled right/left. With this option set to | 156 | the complete content will be scrolled right/left. With this option set to |
@@ -239,13 +239,13 @@ | |||
239 | \end{description} | 239 | \end{description} |
240 | } | 240 | } |
241 | \item[Default Codepage:] | 241 | \item[Default Codepage:] |
242 | A codepage describes the way extended characters that aren't available | 242 | A codepage describes the way extended characters that are not available |
243 | within the ASCII character set are encoded. ID3v1 tags don't have a | 243 | within the ASCII character set are encoded. ID3v1 tags do not have a |
244 | codepage encoding contained so Rockbox needs to know what encoding has | 244 | codepage encoding contained so Rockbox needs to know what encoding has |
245 | been used when generating these tags. This should be ``ISO-8859-1'' but | 245 | been used when generating these tags. This should be ``ISO-8859-1'' but |
246 | to support languages outside Western Europe most applications use | 246 | to support languages outside Western Europe most applications use |
247 | the setting of your operating system instead. If your operating system | 247 | the setting of your operating system instead. If your operating system |
248 | uses a different codepage and you're getting garbled extended characters | 248 | uses a different codepage and you are getting garbled extended characters |
249 | you should adjust this settings. In most cases sticking to | 249 | you should adjust this settings. In most cases sticking to |
250 | ``ISO-8859-1'' would be sufficient. | 250 | ``ISO-8859-1'' would be sufficient. |
251 | \end{description} | 251 | \end{description} |
diff --git a/manual/configure_rockbox/sound_settings.tex b/manual/configure_rockbox/sound_settings.tex index ff6b82a7ad..ec201f93d3 100644 --- a/manual/configure_rockbox/sound_settings.tex +++ b/manual/configure_rockbox/sound_settings.tex | |||
@@ -175,7 +175,7 @@ change to customise your listening experience. | |||
175 | 175 | ||
176 | The practical upshot of this is that MDB produces a more authentic sounding | 176 | The practical upshot of this is that MDB produces a more authentic sounding |
177 | bass by tricking the brain into believing it is hearing tones that the | 177 | bass by tricking the brain into believing it is hearing tones that the |
178 | headphones or speakers aren't capable of reproducing. Try it and see | 178 | headphones or speakers are not capable of reproducing. Try it and see |
179 | what you think. | 179 | what you think. |
180 | 180 | ||
181 | The MDB parameters are as follows: | 181 | The MDB parameters are as follows: |
diff --git a/manual/getting_started/h10_install.tex b/manual/getting_started/h10_install.tex index 81661deb6a..bb212a6504 100644 --- 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: | |||
4 | \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. | 4 | \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. |
5 | \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. | 5 | \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. |
6 | \end{itemize} | 6 | \end{itemize} |
7 | 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. | 7 | 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. |
8 | 8 | ||
9 | \subsubsection{UMS mode and the UMS trick} | 9 | \subsubsection{UMS mode and the UMS trick} |
10 | It is possible to force a MTP \playertype{} to start up in UMS mode using the following procedure: | 10 | 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 | |||
28 | \end{itemize}} | 28 | \end{itemize}} |
29 | \item Connect your \playertype{} to the computer using UMS mode and the UMS trick\opt{h10_5gb}{ if necessary}. | 29 | \item Connect your \playertype{} to the computer using UMS mode and the UMS trick\opt{h10_5gb}{ if necessary}. |
30 | \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{}. | 30 | \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{}. |
31 | \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}.}} | 31 | \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}.}} |
32 | \note{You should keep a safe backup of this file for use if you ever wish to switch back to the \playerman{} firmware.} | 32 | \note{You should keep a safe backup of this file for use if you ever wish to switch back to the \playerman{} firmware.} |
33 | \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.} | 33 | \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.} |
34 | 34 | ||
35 | \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{}. | 35 | \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{}. |
36 | \end{enumerate} | 36 | \end{enumerate} |
diff --git a/manual/getting_started/installation.tex b/manual/getting_started/installation.tex index 3e2611638c..fcb431b96a 100644 --- a/manual/getting_started/installation.tex +++ b/manual/getting_started/installation.tex | |||
@@ -13,7 +13,7 @@ | |||
13 | There are two ways of installing Rockbox: automated and manual. While the | 13 | There are two ways of installing Rockbox: automated and manual. While the |
14 | manual way is older, more tested and proven to work correctly, the | 14 | manual way is older, more tested and proven to work correctly, the |
15 | automated installation is based on a nice graphical application that does | 15 | automated installation is based on a nice graphical application that does |
16 | almost everything that's needed for you. It is still important that you have | 16 | almost everything that is needed for you. It is still important that you have |
17 | an overview of the installation process to be able to select the correct | 17 | an overview of the installation process to be able to select the correct |
18 | installation options. | 18 | installation options. |
19 | 19 | ||
@@ -169,7 +169,7 @@ filesystem.} | |||
169 | detected value, especially if you experience problems with Rockbox.}} | 169 | detected value, especially if you experience problems with Rockbox.}} |
170 | 170 | ||
171 | \note{Rockbox Utility currently lacks some guiding messages. Please have a | 171 | \note{Rockbox Utility currently lacks some guiding messages. Please have a |
172 | look at the manual installation instructions if you're stuck | 172 | look at the manual installation instructions if you are stuck |
173 | during installation.} | 173 | during installation.} |
174 | 174 | ||
175 | \subsection{Manual Installation} | 175 | \subsection{Manual Installation} |
@@ -346,7 +346,7 @@ use. | |||
346 | } | 346 | } |
347 | 347 | ||
348 | \section{Updating Rockbox} | 348 | \section{Updating Rockbox} |
349 | Updating Rockbox is easy even if you don't use the Rockbox Utility. | 349 | Updating Rockbox is easy even if you do not use the Rockbox Utility. |
350 | Download a Rockbox build. | 350 | Download a Rockbox build. |
351 | (The latest release of the Rockbox software will always be available from | 351 | (The latest release of the Rockbox software will always be available from |
352 | \url{http://www.rockbox.org/download/}). Unzip the build to the root directory | 352 | \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. | |||
361 | \subsection{Automatic Uninstallation} | 361 | \subsection{Automatic Uninstallation} |
362 | You can uninstall Rockbox automatically by using Rockbox Utility. If you | 362 | You can uninstall Rockbox automatically by using Rockbox Utility. If you |
363 | installed Rockbox manually you can still use Rockbox Utility for uninstallation | 363 | installed Rockbox manually you can still use Rockbox Utility for uninstallation |
364 | but won't be able to do this selectively. | 364 | but will not be able to do this selectively. |
365 | 365 | ||
366 | \opt{h1xx,h300}{\note{Rockbox Utility can't uninstall the bootloader due to | 366 | \opt{h1xx,h300}{\note{Rockbox Utility cannot uninstall the bootloader due to |
367 | the fact that it requires a flashing procedure. To uninstall the bootloader | 367 | the fact that it requires a flashing procedure. To uninstall the bootloader |
368 | completely follow the manual uninstallation instructions below.}} | 368 | completely follow the manual uninstallation instructions below.}} |
369 | 369 | ||
diff --git a/manual/getting_started/ipod_install.tex b/manual/getting_started/ipod_install.tex index 5a019b5403..97b13bfd71 100644 --- a/manual/getting_started/ipod_install.tex +++ b/manual/getting_started/ipod_install.tex | |||
@@ -67,7 +67,7 @@ should see the message ``[INFO] Bootloader installed successfully.'' Press | |||
67 | ENTER again to exit ipodpatcher and then quit the Terminal application. | 67 | ENTER again to exit ipodpatcher and then quit the Terminal application. |
68 | 68 | ||
69 | \item \warn{If you received a ``Resource busy'' error from | 69 | \item \warn{If you received a ``Resource busy'' error from |
70 | ipodpatcher, then this means you didn't complete step | 70 | ipodpatcher, then this means you did not complete step |
71 | \ref{subsec:macos_umount}. Go back to Disk Utility, unmount your | 71 | \ref{subsec:macos_umount}. Go back to Disk Utility, unmount your |
72 | \dap{} and then run ipodpatcher again.} | 72 | \dap{} and then run ipodpatcher again.} |
73 | 73 | ||
@@ -92,7 +92,7 @@ package -- see \reference{sec:installing_fonts} for more information. | |||
92 | \download{bootloader/ipod/ipodpatcher/linux32x86/ipodpatcher} (32-bit x86 | 92 | \download{bootloader/ipod/ipodpatcher/linux32x86/ipodpatcher} (32-bit x86 |
93 | binary) or \download{bootloader/ipod/ipodpatcher/linux64amd64/ipodpatcher} | 93 | binary) or \download{bootloader/ipod/ipodpatcher/linux64amd64/ipodpatcher} |
94 | (64-bit amd64 binary). You can save this anywhere you wish, but the next | 94 | (64-bit amd64 binary). You can save this anywhere you wish, but the next |
95 | steps will assume you've saved it in your home directory. | 95 | steps will assume you have saved it in your home directory. |
96 | 96 | ||
97 | \item Attach your \dap{} to your computer. | 97 | \item Attach your \dap{} to your computer. |
98 | 98 | ||
diff --git a/manual/getting_started/iriver_install.tex b/manual/getting_started/iriver_install.tex index de3c8c0552..f1ee1b69e2 100644 --- a/manual/getting_started/iriver_install.tex +++ b/manual/getting_started/iriver_install.tex | |||
@@ -96,7 +96,7 @@ | |||
96 | damaged). The screen will simply display the text ``bootloader USB mode''. | 96 | damaged). The screen will simply display the text ``bootloader USB mode''. |
97 | After you disconnect the \dap{} from USB the bootloader will | 97 | After you disconnect the \dap{} from USB the bootloader will |
98 | continue booting Rockbox. As in bootloader USB mode the firmware | 98 | continue booting Rockbox. As in bootloader USB mode the firmware |
99 | itself hasn't been loaded this is also a simple way of updating Rockbox. | 99 | itself has not been loaded this is also a simple way of updating Rockbox. |
100 | After the disconnect the bootloader will load the updated version of | 100 | After the disconnect the bootloader will load the updated version of |
101 | Rockbox. | 101 | Rockbox. |
102 | } | 102 | } |
diff --git a/manual/getting_started/main.tex b/manual/getting_started/main.tex index 92576dde68..fdaf2a45f8 100644 --- a/manual/getting_started/main.tex +++ b/manual/getting_started/main.tex | |||
@@ -32,7 +32,7 @@ firmware. There is, however, more help available. The Rockbox website at | |||
32 | written by members of the Rockbox community and this should be your first port | 32 | written by members of the Rockbox community and this should be your first port |
33 | of call when looking for further help. | 33 | of call when looking for further help. |
34 | 34 | ||
35 | If you can't find the information you're searching for on the Rockbox | 35 | If you cannot find the information you are searching for on the Rockbox |
36 | website there are a number of support channels you should have a look at. | 36 | website there are a number of support channels you should have a look at. |
37 | You can try the Rockbox forums located at \url{http://forums.rockbox.org/}. | 37 | You can try the Rockbox forums located at \url{http://forums.rockbox.org/}. |
38 | Another option are the mailing lists which can be found at | 38 | Another option are the mailing lists which can be found at |
@@ -74,15 +74,15 @@ are used: | |||
74 | or indicate a possible ``weirdness'' in rockbox that would be explained. | 74 | or indicate a possible ``weirdness'' in rockbox that would be explained. |
75 | } | 75 | } |
76 | \warn{This is a warning. In contrast to notes mentioned above, a warning | 76 | \warn{This is a warning. In contrast to notes mentioned above, a warning |
77 | should be taken more seriously. While ignoring notes won't cause any serious | 77 | should be taken more seriously. While ignoring notes will not cause any serious |
78 | damage ignoring warnings \emph{could} cause serious damage. If you're new to | 78 | damage ignoring warnings \emph{could} cause serious damage. If you are new to |
79 | rockbox you should really read the warnings before doing anything that is | 79 | rockbox you should really read the warnings before doing anything that is |
80 | warned about. | 80 | warned about. |
81 | } | 81 | } |
82 | \blind{This icon marks a section that are intended especially for the blind | 82 | \blind{This icon marks a section that are intended especially for the blind |
83 | and visually impaired. As they can't | 83 | and visually impaired. As they cannot |
84 | read the manual in the same way sighted people can do we've added some | 84 | read the manual in the same way sighted people can do we have added some |
85 | additional descriptions. If you aren't blind or visually impaired you most | 85 | additional descriptions. If you are not blind or visually impaired you most |
86 | likely can completely skip these blocks. To make this easier, there is an | 86 | likely can completely skip these blocks. To make this easier, there is an |
87 | icon shown in the margin on the right. | 87 | icon shown in the margin on the right. |
88 | } | 88 | } |
diff --git a/manual/getting_started/sansa_install.tex b/manual/getting_started/sansa_install.tex index 989878e36a..8b333e3ab2 100644 --- a/manual/getting_started/sansa_install.tex +++ b/manual/getting_started/sansa_install.tex | |||
@@ -60,7 +60,7 @@ should see the message ``[INFO] Bootloader installed successfully.'' Press | |||
60 | ENTER again to exit sansapatcher and then quit the Terminal application. | 60 | ENTER again to exit sansapatcher and then quit the Terminal application. |
61 | 61 | ||
62 | \item \warn{If you received a ``Resource busy'' error from | 62 | \item \warn{If you received a ``Resource busy'' error from |
63 | sansapatcher, then this means you didn't complete step | 63 | sansapatcher, then this means you did not complete step |
64 | \ref{subsec:macos_umount}. Go back to Disk Utility, unmount your | 64 | \ref{subsec:macos_umount}. Go back to Disk Utility, unmount your |
65 | \dap{} and then run sansapatcher again.} | 65 | \dap{} and then run sansapatcher again.} |
66 | 66 | ||
@@ -77,7 +77,7 @@ Wait for it to connect, and then eject and unplug it in the normal way. | |||
77 | \download{bootloader/sandisk-sansa/sansapatcher/linux32x86/sansapatcher} (32-bit x86 | 77 | \download{bootloader/sandisk-sansa/sansapatcher/linux32x86/sansapatcher} (32-bit x86 |
78 | binary) or \download{bootloader/sandisk-sansa/sansapatcher/linux64amd64/sansapatcher} | 78 | binary) or \download{bootloader/sandisk-sansa/sansapatcher/linux64amd64/sansapatcher} |
79 | (64-bit amd64 binary). You can save this anywhere you wish, but the next | 79 | (64-bit amd64 binary). You can save this anywhere you wish, but the next |
80 | steps will assume you've saved it in your home directory. | 80 | steps will assume you have saved it in your home directory. |
81 | 81 | ||
82 | \item Attach your \dap{} to your computer. | 82 | \item Attach your \dap{} to your computer. |
83 | 83 | ||
diff --git a/manual/main_menu/fmradio.tex b/manual/main_menu/fmradio.tex index 1b2bbbf879..d51c4d61d2 100644 --- a/manual/main_menu/fmradio.tex +++ b/manual/main_menu/fmradio.tex | |||
@@ -3,7 +3,7 @@ | |||
3 | \opt{RECORDER_PAD}{ | 3 | \opt{RECORDER_PAD}{ |
4 | \note{The early V2 models were in fact FM Recorders in disguise, | 4 | \note{The early V2 models were in fact FM Recorders in disguise, |
5 | so they had the FM radio still mounted. Rockbox enables it if present - | 5 | so they had the FM radio still mounted. Rockbox enables it if present - |
6 | in case this menu doesn't show on your unit you can skip this chapter.\\} | 6 | in case this menu does not show on your unit you can skip this chapter.\\} |
7 | } | 7 | } |
8 | \opt{sansa}{ | 8 | \opt{sansa}{ |
9 | \note{Not all Sansas have a radio receiver. Generally all american models do, | 9 | \note{Not all Sansas have a radio receiver. Generally all american models do, |
diff --git a/manual/plugins/alpinecdc.tex b/manual/plugins/alpinecdc.tex index 008bb62975..8d0fcee746 100644 --- a/manual/plugins/alpinecdc.tex +++ b/manual/plugins/alpinecdc.tex | |||
@@ -13,11 +13,11 @@ Hookup to Archos works by connecting the headphone output including the remote | |||
13 | pin (you need a 4-ring 3.5 mm plug for that) to the changer jack of the radio. | 13 | pin (you need a 4-ring 3.5 mm plug for that) to the changer jack of the radio. |
14 | M-Bus radios have a DIN-style circular jack with 8 pins (7 in a $\sim$ 270 degree | 14 | M-Bus radios have a DIN-style circular jack with 8 pins (7 in a $\sim$ 270 degree |
15 | circle, one in the center). A standard 5-pin DIN plug is OK for this, since we | 15 | circle, one in the center). A standard 5-pin DIN plug is OK for this, since we |
16 | don't use the other (power) pins. | 16 | do not use the other (power) pins. |
17 | 17 | ||
18 | As OEM, they shuffled the pins around a bit, better check first if it is not | 18 | As OEM, they shuffled the pins around a bit, better check first if it is not |
19 | genuine Alpine. The bus pin is pulled high to 12 volts with a $\sim$ 2kOhm resistor, | 19 | genuine Alpine. The bus pin is pulled high to 12 volts with a $\sim$ 2kOhm resistor, |
20 | pulses driven low. Because it's open collector, this is not harmful to the | 20 | pulses driven low. Because it is open collector, this is not harmful to the |
21 | Archos.\\ | 21 | Archos.\\ |
22 | ASCII art of the 4-pin headphone plug: | 22 | ASCII art of the 4-pin headphone plug: |
23 | \begin{verbatim} | 23 | \begin{verbatim} |
@@ -28,12 +28,12 @@ ASCII art of the 4-pin headphone plug: | |||
28 | |_| ground -> Alpine pin 2 + 3 | 28 | |_| ground -> Alpine pin 2 + 3 |
29 | \end{verbatim} | 29 | \end{verbatim} |
30 | 30 | ||
31 | The remote pin can be programmed bidirectional, that's the reason this works. | 31 | The remote pin can be programmed bidirectional, that is the reason this works. |
32 | Very luckily the M-Bus uses a single wire communication and the two radios I | 32 | Very luckily the M-Bus uses a single wire communication and the two radios I |
33 | tried are happy with the 3.3 Volt level the Arcos can deliver. So the | 33 | tried are happy with the 3.3 Volt level the Arcos can deliver. So the |
34 | connection is a simple cable! For all protocols requiring more lines, an | 34 | connection is a simple cable! For all protocols requiring more lines, an |
35 | external controller would be necessary. | 35 | external controller would be necessary. |
36 | 36 | ||
37 | \note{Archos FMs don't have the remote pin internally connected, but | 37 | \note{Archos FMs do not have the remote pin internally connected, but |
38 | one unit that was opened was internally prepared for it, a matter of closing a | 38 | one unit that was opened was internally prepared for it, a matter of closing a |
39 | bridge.} | 39 | bridge.} |
diff --git a/manual/plugins/solitaire.tex b/manual/plugins/solitaire.tex index 1c723bd3bb..f66778295d 100644 --- a/manual/plugins/solitaire.tex +++ b/manual/plugins/solitaire.tex | |||
@@ -3,7 +3,7 @@ | |||
3 | 3 | ||
4 | This is the classic Klondike solitaire game for Rockbox. | 4 | This is the classic Klondike solitaire game for Rockbox. |
5 | This is probably the best-known solitaire in the world. Many people | 5 | This is probably the best-known solitaire in the world. Many people |
6 | don't even realize that other games exist. Though the name may not | 6 | do not even realize that other games exist. Though the name may not |
7 | be familiar, the game itself certainly is. This is due in no small | 7 | be familiar, the game itself certainly is. This is due in no small |
8 | part to Microsoft's inclusion of the the game in every version of | 8 | part to Microsoft's inclusion of the the game in every version of |
9 | Windows. Though popular, the odds of winning are rather low, perhaps | 9 | Windows. Though popular, the odds of winning are rather low, perhaps |
@@ -72,4 +72,4 @@ visit\\ | |||
72 | \opt{IAUDIO_X5_PAD,IRIVER_H10_PAD,SANSA_E200_PAD,SANSA_C200_PAD,GIGABEAT_PAD}{\ButtonPower} | 72 | \opt{IAUDIO_X5_PAD,IRIVER_H10_PAD,SANSA_E200_PAD,SANSA_C200_PAD,GIGABEAT_PAD}{\ButtonPower} |
73 | & Show menu\\ | 73 | & Show menu\\ |
74 | \end{btnmap} | 74 | \end{btnmap} |
75 | \end{table} \ No newline at end of file | 75 | \end{table} |
diff --git a/manual/plugins/split_editor.tex b/manual/plugins/split_editor.tex index c9bafcc4fc..a38a49d5a8 100644 --- a/manual/plugins/split_editor.tex +++ b/manual/plugins/split_editor.tex | |||
@@ -97,7 +97,7 @@ The whole process of splitting an mp3 file consists of three steps: | |||
97 | tuning the split indicator position at the end of a recording. | 97 | tuning the split indicator position at the end of a recording. |
98 | \item | 98 | \item |
99 | \includegraphics[width=0.53cm]{plugins/images/icon-splitedit-loop-4} | 99 | \includegraphics[width=0.53cm]{plugins/images/icon-splitedit-loop-4} |
100 | Playback doesn't loop, the borders of the visible | 100 | Playback does not loop, the borders of the visible |
101 | area as well as the split point indicator are ignored. This mode is | 101 | area as well as the split point indicator are ignored. This mode is |
102 | best used when playing the song outside of the borders of the displayed | 102 | best used when playing the song outside of the borders of the displayed |
103 | region. | 103 | region. |
@@ -154,7 +154,7 @@ In the save dialogue it is possible to specify which of the files you | |||
154 | want to save and their names. When finished, select | 154 | want to save and their names. When finished, select |
155 | ``Save'' and the files will be written to | 155 | ``Save'' and the files will be written to |
156 | disk. Note that files can not be overwritten, so filenames that | 156 | disk. Note that files can not be overwritten, so filenames that |
157 | don't exist yet must be chosen. If unsure whether the | 157 | do not exist yet must be chosen. If unsure whether the |
158 | file already exists simply try to save it. If another file with this | 158 | file already exists simply try to save it. If another file with this |
159 | name exists the dialogue will return and you can choose another | 159 | name exists the dialogue will return and you can choose another |
160 | filename | 160 | filename |
diff --git a/manual/plugins/text_editor.tex b/manual/plugins/text_editor.tex index 3f4d348975..758cd443d6 100644 --- a/manual/plugins/text_editor.tex +++ b/manual/plugins/text_editor.tex | |||
@@ -16,7 +16,7 @@ the \setting{Virtual Keyboard} (see \reference{sec:virtual_keyboard}). | |||
16 | \item When finished editing exit the Text Editor. You'll be shown a list of | 16 | \item When finished editing exit the Text Editor. You'll be shown a list of |
17 | save options. | 17 | save options. |
18 | \end{itemize} | 18 | \end{itemize} |
19 | \note{When you haven't changed the file the Text Editor will quit immediately.} | 19 | \note{When you have not changed the file the Text Editor will quit immediately.} |
20 | 20 | ||
21 | \begin{table} | 21 | \begin{table} |
22 | \begin{btnmap}{}{} | 22 | \begin{btnmap}{}{} |
diff --git a/manual/plugins/wavplay.tex b/manual/plugins/wavplay.tex index 6246269991..350c76126a 100644 --- a/manual/plugins/wavplay.tex +++ b/manual/plugins/wavplay.tex | |||
@@ -10,8 +10,8 @@ plugin automatically and the Wavplay screen | |||
10 | appears. This screen gives information about samplerate and length of the | 10 | appears. This screen gives information about samplerate and length of the |
11 | playing file. | 11 | playing file. |
12 | \note{Seeking within the \fname{.wav}-file or changing the volume once the | 12 | \note{Seeking within the \fname{.wav}-file or changing the volume once the |
13 | plugin is running isn't possible. Wavplay uses the sound settings that were | 13 | plugin is running is not possible. Wavplay uses the sound settings that were |
14 | used before (except for pitch).} | 14 | used before (except for pitch).} |
15 | The only action that can be performed is to stop by pressing \ButtonOff, and | 15 | The only action that can be performed is to stop by pressing \ButtonOff, and |
16 | Wavplay will be exited and you are returned to the filebrowser. If the end of | 16 | Wavplay will be exited and you are returned to the filebrowser. If the end of |
17 | the file has been reached, you will also be returned to the filebrowser. \ No newline at end of file | 17 | the file has been reached, you will also be returned to the filebrowser. |
diff --git a/manual/rockbox_interface/main.tex b/manual/rockbox_interface/main.tex index 7a26074e34..1326db8787 100644 --- a/manual/rockbox_interface/main.tex +++ b/manual/rockbox_interface/main.tex | |||
@@ -191,7 +191,7 @@ paragraph. | |||
191 | 191 | ||
192 | On the bottom of the unit is the connector for the | 192 | On the bottom of the unit is the connector for the |
193 | \playerman{} subpack or dock. On the top of the unit is a charge | 193 | \playerman{} subpack or dock. On the top of the unit is a charge |
194 | indicator light, which may feel a bit like a button, but isn't. | 194 | indicator light, which may feel a bit like a button, but is not. |
195 | 195 | ||
196 | From the top of the \dap{} on the left hand side is the headphone socket, then the | 196 | From the top of the \dap{} on the left hand side is the headphone socket, then the |
197 | remote connector. Below this is a cover which protects the \opt{x5}{USB host | 197 | 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: | |||
329 | Rockbox has a dual-boot feature. It loads the original firmware from | 329 | Rockbox has a dual-boot feature. It loads the original firmware from |
330 | the file \fname{/System/OF.mi4}. To boot into the original firmware, | 330 | the file \fname{/System/OF.mi4}. To boot into the original firmware, |
331 | press and hold the \ButtonLeft{} button while turning on the player. | 331 | press and hold the \ButtonLeft{} button while turning on the player. |
332 | \note{The iriver firmware doesn't shut down properly when you turn it off, | 332 | \note{The iriver firmware does not shut down properly when you turn it off, |
333 | it only goes to sleep. To get back into Rockbox when exiting from the | 333 | it only goes to sleep. To get back into Rockbox when exiting from the |
334 | iriver firmware, you will need to reset the player by \opt{h10}{inserting a | 334 | iriver firmware, you will need to reset the player by \opt{h10}{inserting a |
335 | pin in the reset hole}\opt{h10_5gb}{taking out battery}.} | 335 | 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. | |||
374 | Rockbox is playlist oriented. This means that every time you play an audio file, | 374 | Rockbox is playlist oriented. This means that every time you play an audio file, |
375 | a so-called ``dynamic playlist'' is generated, unless you play a saved | 375 | a so-called ``dynamic playlist'' is generated, unless you play a saved |
376 | playlist. You can modify the dynamic playlist while playing and also save | 376 | playlist. You can modify the dynamic playlist while playing and also save |
377 | it to a file. If you don't want to use playlists you can simply play your | 377 | it to a file. If you do not want to use playlists you can simply play your |
378 | files directory based. | 378 | files directory based. |
379 | Playlists are covered in detail in \reference{ref:working_with_playlists}. | 379 | Playlists are covered in detail in \reference{ref:working_with_playlists}. |
380 | 380 | ||
@@ -390,7 +390,7 @@ The contents of the context menu vary, depending on the situation it gets | |||
390 | called. The context menu itself presents you with some operations you can | 390 | called. The context menu itself presents you with some operations you can |
391 | perform with the currently highlighted file. In the file browser this is | 391 | perform with the currently highlighted file. In the file browser this is |
392 | the file (or directory) that is highlighted by the cursor. From the WPS this is | 392 | the file (or directory) that is highlighted by the cursor. From the WPS this is |
393 | the currently playing file. Also there are some actions that don't apply | 393 | the currently playing file. Also there are some actions that do not apply |
394 | to the current file but refer to the screen from which the context menu | 394 | to the current file but refer to the screen from which the context menu |
395 | gets called. One example is the playback menu, which can be called using | 395 | gets called. One example is the playback menu, which can be called using |
396 | the context menu from within the WPS. | 396 | the context menu from within the WPS. |
diff --git a/manual/rockbox_interface/tagcache.tex b/manual/rockbox_interface/tagcache.tex index c489eb65ee..56481dd5cf 100644 --- a/manual/rockbox_interface/tagcache.tex +++ b/manual/rockbox_interface/tagcache.tex | |||
@@ -108,7 +108,7 @@ $\rightarrow$ System $\rightarrow$ Limits}) in order to view long lists of | |||
108 | tracks in the ID3 database browser.\\ | 108 | tracks in the ID3 database browser.\\ |
109 | 109 | ||
110 | There is no option to turn off database completely. If you do not want | 110 | There is no option to turn off database completely. If you do not want |
111 | to use it just don't do the initial build of the database and do not load it | 111 | to use it just do not do the initial build of the database and do not load it |
112 | to RAM.} | 112 | to RAM.} |
113 | % | 113 | % |
114 | \begin{table} | 114 | \begin{table} |
diff --git a/manual/rockbox_interface/wps.tex b/manual/rockbox_interface/wps.tex index fedd5e156e..b233f08020 100644 --- a/manual/rockbox_interface/wps.tex +++ b/manual/rockbox_interface/wps.tex | |||
@@ -205,8 +205,8 @@ function in the \setting{File Context Menu}. | |||
205 | The \setting{Pitch Screen} allows you to change the pitch and (at the same | 205 | The \setting{Pitch Screen} allows you to change the pitch and (at the same |
206 | time) the playback speed of your \dap. The pitch value can be adjusted | 206 | time) the playback speed of your \dap. The pitch value can be adjusted |
207 | between 50\% and 200\%. 50\% means half the normal playback speed and the | 207 | between 50\% and 200\%. 50\% means half the normal playback speed and the |
208 | pitch that's an octave lower than the normal pitch. 200\% means double | 208 | pitch that is an octave lower than the normal pitch. 200\% means double |
209 | playback speed and the pitch that's an octave higher than the normal pitch. | 209 | playback speed and the pitch that is an octave higher than the normal pitch. |
210 | It is not possible to change the pitch without changing the playback speed and | 210 | It is not possible to change the pitch without changing the playback speed and |
211 | vice versa. Changing the pitch can be done in two modes: procentual and | 211 | vice versa. Changing the pitch can be done in two modes: procentual and |
212 | semitone. Initially (after the \dap{} is switched on), procentual mode | 212 | semitone. Initially (after the \dap{} is switched on), procentual mode |
diff --git a/manual/working_with_playlists/main.tex b/manual/working_with_playlists/main.tex index b8ac2f5e21..f6c651dfd1 100644 --- a/manual/working_with_playlists/main.tex +++ b/manual/working_with_playlists/main.tex | |||
@@ -103,7 +103,7 @@ options: | |||
103 | \item [Insert last.] Add track(s) to end of playlist. | 103 | \item [Insert last.] Add track(s) to end of playlist. |
104 | 104 | ||
105 | \item [Queue.] Queue is the same as Insert except queued tracks are | 105 | \item [Queue.] Queue is the same as Insert except queued tracks are |
106 | deleted immediately from the playlist after they've been played. Also, | 106 | deleted immediately from the playlist after they have been played. Also, |
107 | queued tracks are not saved to the playlist file (see | 107 | queued tracks are not saved to the playlist file (see |
108 | \reference{ref:playlistoptions}). | 108 | \reference{ref:playlistoptions}). |
109 | 109 | ||
@@ -159,7 +159,7 @@ select \setting{Save Current Playlist} or enter the | |||
159 | \setting{Save Current Playlist}. | 159 | \setting{Save Current Playlist}. |
160 | Either method will bring you to the \setting{Virtual Keyboard} (see | 160 | Either method will bring you to the \setting{Virtual Keyboard} (see |
161 | \reference{sec:virtual_keyboard}), enter a filename for your playlist and | 161 | \reference{sec:virtual_keyboard}), enter a filename for your playlist and |
162 | accept it and you're done. | 162 | accept it and you are done. |
163 | 163 | ||
164 | \subsection{Loading saved playlists} | 164 | \subsection{Loading saved playlists} |
165 | \subsubsection{Through the \setting{File Browser}} | 165 | \subsubsection{Through the \setting{File Browser}} |