So they are protected from overflows, and shared between processes

These are global arrays reused several times. When using them msan and
valgrind thus believe they are always initialized, which reduces their
capacity to detect uninitialized values. We can however explicitly tell them
when they are reused, and thus to be considered as uninitialized.

Add x86-32 CI

When pollint() returns 100.0, multiplying by 2.55 doesn't actually seem to
be getting 255 on i386. Multiplying by 255 and dividing by 100, however,
does (probably because float computation with small integer values are
guaranteed to have integer results).

Fixes #1151

This has varying behavior depending on toolchain and processor.

Fixes #1151

When building espeak-ng in a directory that has a long path, 80 bytes to
store it is quite short.

When the current locale doesn't match the current voice, grep would be
surprised by the produced output and believe that this is not text, for
instance with LC_ALL=ru_RU.CP1251 we get:

  TEST      tests/language-replace.test
[...]
testing mk
grep: (standard input): binary file matches
2d1
< Translate 'пејзаж'

But we can give -a to grep so it always considers its input as text.

Fixes #1152

fixes #700

this fixes #891

ref: https://github.com/espeak-ng/espeak-ng/issues/857#issuecomment-962500311

otherwise we get many errors

For the case when word is smaller than 4 characters, we should not look at
the 3rd or 4th character before checking the previous ones, otherwise
we'd at best read uninitialized data, at worse non-existing data.

Ref #853

Now that all errors are fixed.

Fix #1083 and improve some things in German

fname_temp is not always getting filled.

Otherwise we would miss errors produced on shutdown.

Otherwise they will go unnoticed.

Now that all memory errors are fixed.

Ref #220

Some rules test against character not being of a certain type. That may
match with the \0 end-of-text marker, and thus actually step over
it and let MatchRule continue with uninitialized data after it, leading
to potential random behavior.

This commits fixes it by making sure that we don't read past that \0.

This seems to be changing the pronunciation of "capitals" from k'apIt@Lz to
k'apIt,alz, I don't know why, I guess the rule for it was actually
bogus?