Motorola MK4000 Reference Guide - Page 44

Using Additional Fonts in Native Applications, Things to Consider when Using Additional Fonts

Get Motorola MK4000 - Micro Kiosk - 128 MB RAM PDF manuals and user guides View all Motorola MK4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 44 highlights

4 - 4 MK4000 MicroKiosk for CE .NET 5.0 Product Reference Guide Using the third option, i.e., copying fonts to the \windows\fonts directory, makes it easier to manage the system. Note that fonts copied to \windows or \windows\fonts do not persist over power cycles or cold boots. Use the copy file feature to persist them over power cycles or cold boots. Using Additional Fonts in Native Applications Any application written in EVC can use the additional fonts using either MFC or Win32 APIs. If a specified font is missing, the system uses an available font for display. Using Additional Fonts in Managed Applications All fonts installed in the system are available to the .Net Compact Framework during runtime. Using Additional Fonts in Browser Applications Regardless of how you installed the font in the system, to reference it using a browser page, specify the font as a STYLE, or use FONT tags. Use intuitive names for the fonts (use FontViewer on a Windows desktop and locate the Typeface Name line), and use quotes to enclose names with spaces. If the specified font is missing, Internet Explorer uses its default font to display the text. Things to Consider when Using Additional Fonts • Different font styles (e.g., bold and italic) often require separate TTF files; be sure to provide all required styles. Do not reference styles by name (e.g., Arial Bold); set the style separately from the font (e.g., using a "b" or "strong" tag, or a style). • For best results, do not direct the system font path to a storage card (PCMCIA), as this can negatively impact system performance. If this method is necessary, test the use of a storage card thoroughly for fonts to ensure proper operation. • Most Web pages contain information that tells the browser what language encoding (the language and character set) to use. If the page does not include that information, and the Language Encoding Auto-Select feature is on, Internet Explorer can usually determine the appropriate language encoding. If not, manually select it using View menu > Encoding > More, then select the appropriate language. NOTE If the Auto-Select feature or a specific language pack is not installed, Internet Explorer prompts you to download the files. Adding languages does not guarantee Web pages display in the preferred language.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
4 - 4
MK4000 MicroKiosk for CE .NET 5.0 Product Reference Guide
Using the third option, i.e., copying fonts to the \windows\fonts directory, makes it easier to manage the system.
Note that fonts copied to \windows or \windows\fonts do not persist over power cycles or cold boots. Use the
copy file feature to persist them over power cycles or cold boots.
Using Additional Fonts in Native Applications
Any application written in EVC can use the additional fonts using either MFC or Win32 APIs. If a specified font
is missing, the system uses an available font for display.
Using Additional Fonts in Managed Applications
All fonts installed in the system are available to the .Net Compact Framework during runtime.
Using Additional Fonts in Browser Applications
Regardless of how you installed the font in the system, to reference it using a browser page, specify the font as
a STYLE, or use FONT tags. Use intuitive names for the fonts (use FontViewer on a Windows desktop and
locate the
Typeface Name
line), and use quotes to enclose names with spaces. If the specified font is missing,
Internet Explorer uses its default font to display the text.
Things to Consider when Using Additional Fonts
•
Different font styles (e.g., bold and italic) often require separate TTF files; be sure to provide all required
styles. Do not reference styles by name (e.g., Arial Bold); set the style separately from the font (e.g.,
using a “b” or “strong” tag, or a style).
•
For best results, do not direct the system font path to a storage card (PCMCIA), as this can negatively
impact system performance. If this method is necessary, test the use of a storage card thoroughly for
fonts to ensure proper operation.
•
Most Web pages contain information that tells the browser what language encoding (the language and
character set) to use. If the page does not include that information, and the Language Encoding
Auto-Select feature is on, Internet Explorer can usually determine the appropriate language encoding. If
not, manually select it using
View
menu >
Encoding > More
, then select the appropriate language.
NOTE
If the Auto-Select feature or a specific language pack is not installed, Internet Explorer prompts you to
download the files. Adding languages does not guarantee Web pages display in the preferred language.