-This is ../info/internals.info, produced by makeinfo version 3.12s from
+This is ../info/internals.info, produced by makeinfo version 4.0 from
internals/internals.texi.
INFO-DIR-SECTION XEmacs Editor
also have to be marked manually. That is done by the function
`mark_profiling_info'
- 9. Hash tables in Xemacs belong to a kind of special objects that
+ 9. Hash tables in XEmacs belong to a kind of special objects that
make use of a concept often called 'weak pointers'. To make a
long story short, these kind of pointers are not followed during
the estimation of the live objects during garbage collection. Any
the object is a real Lisp object `Lisp_Type_Record' or just an integer
or a character. Integers and characters are the only two types that are
stored directly - without another level of indirection, and therefore
-they don´t have to be marked and collected. *Note How Lisp Objects Are
+they don't have to be marked and collected. *Note How Lisp Objects Are
Represented in C::.
The second case is the one we have to handle. It is the one when we
objects are allocated and handled using that scheme of `lcrecords'.
Each object is `malloc'ed separately instead of placing it in one of
the contiguous frob blocks. All types that are currently stored using
-`lcrecords'´s `alloc_lcrecord' and `make_lcrecord_list' are the types:
+`lcrecords''s `alloc_lcrecord' and `make_lcrecord_list' are the types:
vectors, buffers, char-table, char-table-entry, console, weak-list,
database, device, ldap, hash-table, command-builder, extent-auxiliary,
extent-info, face, coding-system, frame, image-instance, glyph,