display | more...

For technical purposes that will become clearer later, this document is upside-down. If this is your first visit, skip to the bottom for explanations and instructions.

248
ø
ø
o
 

249
ù
ù
u
 

250
ú
ú
u
 

251
û
û
u
 

252
ü
ü
u
 

253
ý
ý
y
 

254
þ
þ
th
 

255
ÿ
ÿ
y
 

240
ð
ð
th
 

241
ñ
ñ
n
 

242
ò
ò
o
 

243
ó
ó
o
 

244
ô
ô
o
 

245
õ
õ
o
 

246
ö
ö
o, oe
 

247
÷
÷
/
 

232
è
è
e
 

233
é
é
e
 

234
ê
ê
e
 

235
ë
ë
e
 

236
ì
ì
i
 

237
í
í
i
 

238
î
î
i
 

239
ï
ï
i
 

224
à
à
a
 

225
á
á
a
 

226
â
â
a
 

227
ã
ã
a
 

228
ä
ä
a, ae
 

229
å
å
a
 

230
æ
æ
ae
 

231
ç
ç
c
 

216
Ø
Ø
O
 

217
Ù
Ù
U
 

218
Ú
Ú
U
 

219
Û
Û
U
 

220
Ü
Ü
U, Ue
 

221
Ý
Ý
Y
 

222
Þ
Þ
th
 

223
ß
ß
ss
 

208
Ð
Ð
Th
 

209
Ñ
Ñ
N
 

210
Ò
Ò
O
 

211
Ó
Ó
O
 

212
Ô
Ô
O
 

213
Õ
Õ
O
 

214
Ö
&Öuml;
O, Oe
 

215
×
×
*
 

200
È
È
E
 

201
É
É
E
 

202
Ê
Ê
E
 

203
Ë
Ë
E
 

204
Ì
Ì
I
 

205
Í
Í
I
 

206
Î
Î
I
 

207
Ï
Ï
I
 

192
À
À
A
 

193
Á
Á
A
 

194
Â
Â
A
 

195
Ã
Ã
A
 

196
Ä
Ä
A
 

197
Å
Å
A
 

198
Æ
Æ
AE
 

199
Ç
Ç
C
 

184
¸
¸
 

185
¹
¹
 

186
º
º
 

187
»
»
 

188
¼
¼
1/4
 

189
½
½
1/2
 

190
¾
¾
3/4
 

191
¿
¿
 

176
°
°
 

177
±
±
 

178
²
²
 

179
³
³
 

180
´
´
 

181
µ
µ
micro
 

182

¶
paragraph
 

183
·
·
 

168
¨
¨
 

169
©
©
 

170
ª
ª
 

171
«
«
 

172
¬
¬
~
 

173
­
­
-
 

174
®
®
(R)
 

175
¯
¯
 

160
 
 

 

161
¡
¡
 

162
¢
¢
cents
 

163
£
£
pounds
 

164
¤
¤
 

165
¥
¥
yen
 

166
¦
¦
|
 

167
§
§
section
 

152
˜
(˜)
~
 

153

(™)
TM
 

154
š
(š)
s, sh
 

155

(›)
>
 

156
œ
(œ)
oe
 

157

 

158
ž
(ž)
z
 

159
Ÿ
(Ÿ)
ye
 

144

 

145

(‘)
 

146

(’)
 

147

(“)
 

148

(”)
 

149

(•)
 

150

 

151

 

136
ˆ
(ˆ)
 

137

(‰)
per mil
 

138
Š
(Š)
S
 

139

(‹)
<
 

140
Œ
(&OElig;)
OE
 

141

 

142
Ž
(&Zcaron;)
Z
 

143

 

128

&euro;
 

129

 

130

(NONE)
,
 

131
ƒ
(&#402;)
f
 

132

(&#8222;)
"
 

133

(&#8230;)
...
 

134

(&dagger;)
 

135

(&Dagger;)
 


Why does this document exist?

This document helps users to make titles with special characters from the "upper 128" of the ISO-8859-1 character set. For technical reasons, an explanation, as well as instructions for use, are down here at the bottom.

The basic idea is to build an entity-free title in the E2 search box at the top of the document. Some people are not able to type in special characters, nor do they have the Windows Character Map program available. Such people can come here an build their titles.

Since we're working with the search box, it's a good idea to keep it as close as possible to the special characters that will be used the most frequently: lower-case accented characters and umlauts. That's why it's upside-down.


An Explanation of the table

The table above displays the upper 128 characters of the ISO-8859-1 character set. Each cell contains four pieces of information about a specific character:

Code:
Character:
Entity:
Alternate forms:

48
0
(&#48;)
f

Code
is the numeric (decimal) code for the character. If the code appears in ITALICS, the corresponding character IS NOT an acceptable character in a node title. If the code appears in BOLD, the corresponding character IS an acceptable character in a node title.
Character
is the visual representation of the character.
Entity
is the associated HTML entity for the character. If the entity appears in parentheses, it's actually a different entity that has an identical appearance.
Alternate forms
indicate acceptable alternate forms for the character.

Which special characters are acceptable in titles, and why?

Acceptable special characters:

  • should indicate a pronunciation that is not represented by an unadorned Roman letter. This leaves out all of the symbol characters.
  • should be standard. This leaves out all of the characters with codes 128-159.
  • should not be a dipthong or a ligature.


How to use this node for your titles

  • Ordinary Users can use this document to build a title string to search for a node (and possibly create a new node), as wel as find out if it's necessary to create "alternate version" nodeshells that get linked to the "correct" title.
  • Gods can use this document to build an entity-free title string for renaming nodes. Build the string in the search box, select the text, then follow all of the steps you normally follow to change a node title. However, instead of typing in the new title as you normally would, paste the string you copied out of this document.
  • Simply type ordinary characters in the search box.
  • For each special character, look for its entry in the table above.
    • If the character is acceptable for a node title, copy the visual representation of the character from the table, and paste it into the search box.
    • If the character is not acceptable, type in the character's alternate form instead. If there's no alternate form, DON'T USE IT. At any rate, try to avoid putting a symbol in a title if at all possible. We demand this for factual writeups.

Finally, if you create a node that had acceptable special characters, create a nodeshell where all of the special characters are replaced by alternate forms. For Germanic titles containing umlauts, you may have to create two nodeshells. Then ask an editor to firmlink the nodeshell to the correct title for you.


But wait, there's more:

You may not need to use this document. You may, of course, have Windows Character map available. But a much simpler way to do it may already be available: Type a title into the search box, replacing special characters with the corresponding HTML entity sequences. So, if you're looking for "Süper Düper Title", type "Samp;uuml;per D&uuml;per Title". Then search for the sequence. Hopefully, you'll get a "Nothing found" or a results list. At the bottom of the results node, you'll see:

Of course, I could let you create a new "Süper Düper Title" node. You can correct the capitalization, if there's a need.

  

Simply copy "Süper Düper Title" from between the quotes and paste it into the edit box, and click "Create Node". Presto!