Pārlūkot izejas kodu

Another update for the documentation.

AnHardt 10 gadus atpakaļ
vecāks
revīzija
d9b3232e94
1 mainītis faili ar 9 papildinājumiem un 8 dzēšanām
  1. 9
    8
      Documentation/LCDLanguageFont.md

+ 9
- 8
Documentation/LCDLanguageFont.md Parādīt failu

@@ -12,12 +12,13 @@ We have two different technologies for the displays:
12 12
   All of them have a similar but not identical symbol set at the positions 0 to 127 similar to US-ASCII.
13 13
   On the other hand symbols at places higher than 127 have mayor differences.
14 14
   Until now we know of (and support):
15
-  ** 1.) HD44780 and similar with Kana charset A00 https://www.sparkfun.com/datasheets/LCD/HD44780.pdf Page 17
15
+  * 1.) HD44780 and similar with Kana charset A00 https://www.sparkfun.com/datasheets/LCD/HD44780.pdf Page 17
16 16
       These are very common, but sadly not very useful when writing in European languages.
17
-  ** 2.) HD44780 and similar with Western charset A02 https://www.sparkfun.com/datasheets/LCD/HD44780.pdf Page 18
17
+  * 2.) HD44780 and similar with Western charset A02 https://www.sparkfun.com/datasheets/LCD/HD44780.pdf Page 18
18 18
       These are rare, but fairly useful for European languages. Also a limited number of Cyrillic symbols is available.
19
-  ** 3.) HD44780 and similar with Cyrillic charset http://store.comet.bg/download-file.php?id=466 Page 14
19
+  * 3.) HD44780 and similar with Cyrillic charset http://store.comet.bg/download-file.php?id=466 Page 14
20 20
       Some of our Russian friends use them.
21
+
21 22
   At all of them you can define 8 different symbols by yourself. In Marlin they are used for the Feedrate-, Thermometer-, ... symbols
22 23
 
23 24
 * Full graphic displays
@@ -25,9 +26,9 @@ We have two different technologies for the displays:
25 26
   Currently we deal with 128x64 Pixel Displays and divide this area in about 5 Lines with about 22 columns.
26 27
   Therefore we need fonts with a bounding box of about 6x10.
27 28
   Until now we used a
28
-  ** 1.) Marlin-font similar to ISO10646-1 but with special Symbols at the end, what made 'ü' and 'ä' inaccessible, in the size 6x10.
29
-  ** 2.) Because these letters are to big for some locations on the info-screen we use a full ISO10646-1 font in the size of 6x9.
30
-  ** 3.) When we define USE_BIG_EDIT_FONT we use an additional ISO10646-1 font with 9x18, eating up another 3120 bytes of progmem - but readable without glasses.
29
+  * 1.) Marlin-font similar to ISO10646-1 but with special Symbols at the end, what made 'ü' and 'ä' inaccessible, in the size 6x10.
30
+  * 2.) Because these letters are to big for some locations on the info-screen we use a full ISO10646-1 font in the size of 6x9.
31
+  * 3.) When we define USE_BIG_EDIT_FONT we use an additional ISO10646-1 font with 9x18, eating up another 3120 bytes of progmem - but readable without glasses.
31 32
 
32 33
 ## The Languages
33 34
   For the moment Marlin wants to support a lot of languages:
@@ -63,7 +64,7 @@ We have two different technologies for the displays:
63 64
   Other languages ether tried to avoid wording with their special symbols or ignored the problem at all and used the basic symbols without the accents, dots, ... whatever.
64 65
 
65 66
 ## The (partial) Solution
66
-  On a 'perfect' system like Windows or Linux we'd dig out unifont.ttf and some code from the libraries and they'd do what we want. But we are on a embedded system with very limited resources. So we had to find ways so limit the used space (Alone unifont.ttf is about 12MB) and have to make some compromise.
67
+  On a 'perfect' system like Windows or Linux we'd dig out unifont.ttf and some code from the libraries and they'd do what we want. But we are on a embedded system with very limited resources. So we had to find ways to limit the used space (Alone unifont.ttf is about 12MB) and have to make some compromise.
67 68
 
68 69
 ### Aims:
69 70
   * 1.) Make the input for translators as convenient as possible. (Unicode UTF8)
@@ -128,7 +129,7 @@ We have two different technologies for the displays:
128 129
 
129 130
 ## User Instructions
130 131
    Define your hardware and the wanted language in 'Configuration.h'.
131
-   To find out what charset you harware is define language 'test' and compile. In the menu you will see two lines from the upper half of the charset.
132
+   To find out what charset your hardware is define language 'test' and compile. In the menu you will see two lines from the upper half of the charset.
132 133
    * DISPLAY_CHARSET_HD44780_JAPAN   locks like "バパヒビピフブプヘベペホボポマミ"
133 134
    * DISPLAY_CHARSET_HD44780_WESTERN locks like "ÐÑÒÓÔÕÖרÙÚÛÜÝÞß"
134 135
    * DISPLAY_CHARSET_HD44780_CYRILIC locks like "РСТУФХЦЧШЩЪЫЬЭЮЯ"

Notiek ielāde…
Atcelt
Saglabāt