Browsing Czech translation

1322.

<p><b>eMovix Boot Labels</b>
<p>eMovix provides a variety of different boot configurations which can be selected at boot time via a boot label (comparable to Lilo or Grub). The many different boot configurations mainly influence the Video output.
<p>The <b>default</b>, <b>movix</b>, or <b>MoviX</b> labels start a general Vesa video driver.
<p>The <b>TV</b> labels can be used to direct video to the TV output of the graphic board. eMovix provides TVout drivers for different brands of graphic boards.
<p>The <b>FB</b> labels refer to configurations that start a Frame Buffer driver in different screen resolutions.
<p>The <b>AA</b> labels make eMovix output the video through the Ascii-Art library which displays the picture in text mode through the usage of simple Acsii characters.
<p>The <b>hd</b> label makes eMovix boot from the local harddisk instead of the medium. This can be used to prevent accidental starting of an eMovix medium.
<p>The <b>floppy</b> label makes eMovix boot from the local floppy drive instead of the medium.

1361.

<p>If this option is checked, K3b will generate the System Use Sharing Protocol records (SUSP) specified by the Rock Ridge Interchange Protocol (IEEE-P1282).
<p>Rock Ridge extends the ISO-9660 filesystem by features equal to the UNIX filesystems (permissions, symbolic links, very long filenames, ...). It uses ISO-8859 or UTF-16 based characters and allows 255 octets.
<p>Rock Ridge extensions are located at the end of each ISO-9660 directory record. This makes the Rock Ridge tree closely coupled to the ISO-9660 tree.
<p><b>It is highly recommended to use Rock Ridge extensions on every data CD or DVD.</b>

1400.

<p><b>No Change</b><br>
If this option is checked, K3b will leave all spaces in filenames as they are.
<p><b>Strip</b><br>
If this option is checked, K3b will remove all spaces from all filenames.<br>
Example: 'my good file.ext' becomes 'mygoodfile.ext'
<p><b>Extended Strip</b><br>
If this option is checked K3b will remove all spaces in all filenames and capitalize all letters following a space.<br>
Example: 'my good file.ext' becomes 'myGoodFile.ext'
<p><b>Replace</b><br>
If this option is checked, K3b will replace all spaces in all filenames with the specified characters.<br>
Example: 'my good file.ext' becomes 'my_good_file.ext'

1538.

<p>The sample data encoding is signed linear (2's complement), unsigned linear, u-law (logarithmic), A-law (logarithmic), ADPCM, IMA_ADPCM, GSM, or Floating-point.</p>
<p><b>U-law</b> (actually shorthand for mu-law) and <b>A-law</b> are the U.S. and international standards for logarithmic telephone sound compression. When uncompressed u-law has roughly the precision of 14-bit PCM audio and A-law has roughly the precision of 13-bit PCM audio. A-law and u-law data is sometimes encoded using a reversed bit-ordering (i.e. MSB becomes LSB).<br> <b>ADPCM </b> is a form of sound compression that has a good compromise between good sound quality and fast encoding/decoding time. It is used for telephone sound compression and places where full fidelity is not as important. When uncompressed it has roughly the precision of 16-bit PCM audio. Popular versions of ADPCM include G.726, MS ADPCM, and IMA ADPCM. It has different meanings in different file handlers. In .wav files it represents MS ADPCM files, in all others it means G.726 ADPCM. <br> <b>IMA ADPCM</b> is a specific form of ADPCM compression, slightly simpler and slightly lower fidelity than Microsoft's flavor of ADPCM. IMA ADPCM is also called DVI ADPCM.<br> <b>GSM</b> is a standard used for telephone sound compression in European countries and is gaining popularity because of its good quality. It is usually CPU intensive to work with GSM audio data.</p> <p><em>Description based on the SoX manpage</em></p>

1567.

<p><b>Command</b><br>
Please insert the command used to encode the audio data. The command has to read raw little endian (see <em>Swap Byte Order</em>) 16-bit stereo audio frames from stdin.
<p>The following strings will be replaced by K3b:<br>
<b>%f</b> - The filename of the resulting file. This is where the command has to write its output to.<br>
<em>The following refer to metadata stored for example in the ID3 tag of am mp3 file (Be aware that these values might be empty).</em><br>
<b>%t</b> - Title<br>
<b>%a</b> - Artist<br>
<b>%c</b> - Comment<br>
<b>%n</b> - Track number<br>
<b>%m</b> - Album Title<br>
<b>%r</b> - Album Artist<br>
<b>%x</b> - Album comment<br>
<b>%y</b> - Release Year