User manual NAKAMICHI RX505 SERVICE MANUAL

[. . . ] However, the content of this document is provided "as is", without warranties of any kind with regard to its accuracy or reliability, and specifically excluding all implied warranties, for example of merchantability, fitness for purpose, title and non-infringement. In no event shall Picsel be liable for any special, indirect or consequential damages whatsoever resulting from loss of use, data or profits, arising out of or in connection with the use of this document. Picsel reserves the right to revise the document or withdraw it at any time without prior notice. [. . . ] No licence is granted (nor any rights of whatsoever nature granted), express or implied, to any intellectual property by this document. Throughout this document, the trade names and trademarks of some companies and products have been used. No such uses are intended to convey endorsement of or other affiliations with the document. Document number PICSEL-ESF-0008B April 2002 http://www. picsel. com/ Picsel Text File Format Support Page 3 Introduction On handheld computers, traditional applications typically rely on synchronization with a PC to convert content from the original document format into a simpler format used by the device. Firstly, some visual integrity is inevitably lost in the conversion process from a rich format to a simpler one, resulting in documents that do not look exactly like the original. Secondly, the reliance on a PC for synchronization means that direct network access is difficult, and the device is severely hampered when untethered from the PC. Thirdly, traditional applications take a monolithic approach, converting only a single format so that separate applications are needed for each different document type. The approach involves researching the feature set most commonly found in real documents, building support early for the most frequently used elements, and ensuring these features are reproduced with total faithfulness to the original. The emphasis of ePAGE is on displaying rich content rather than on reproducing the document creation facilities of the original application. This level of support already covers the vast majority of characteristics that occur in day to day documents of this type, and the specific features are described with notes where appropriate. Those features planned for future implementation are also described, for completeness. Plain Text While there are many document formats which encode extra information such as page size and pictures into a single file, the most basic commonly used file format for text is called a plain text file. This has no special file structure; from the first byte to the last is a seqeuence of characters. Some of these characters do not appear visually, but instead take new lines or indent to a tab stop, as defined in the ASCII standard (ANSI X3. 4, initially approved in 1969). Feature Plain 7-bit ASCII text Latin1 text Newlines Tabs Unlimited page size Support Yes Yes Yes Yes Yes Notes Converted to sequences of spaces Character Sets ePAGE can work with all characters in the Unicode specification. [. . . ] Some of these characters do not appear visually, but instead take new lines or indent to a tab stop, as defined in the ASCII standard (ANSI X3. 4, initially approved in 1969). Feature Plain 7-bit ASCII text Latin1 text Newlines Tabs Unlimited page size Support Yes Yes Yes Yes Yes Notes Converted to sequences of spaces Character Sets ePAGE can work with all characters in the Unicode specification. Text documents are encoded in other encodings, and ePAGE handles these by converting Latin1 to UTF-16 Unicode. [. . . ]