[kde-doc-english]update

[Frederik Fouvry]

| > You define per person two entities, e.g.
| >
| > (1)
| > <!ENTITY Eric.Bischoff
| > "<personname><firstname>Éric</firstname><surname>Bischoff</surname></per
| >sonname>">
| > <!ENTITY Eric.Bischoff.mail "<email>e.bischoff at noos.fr</email>">
| 
| > These can then be freely used in the documentation (both in
| > othercredit elements, author elements, ... and in the running
| > text).
| 
| Thanks for the explanation.
| 
| The problem with that method is that it does not help much normalizing the 
| ROLES_OF_TRANSLATORS and CREDIT_FOR_TRANSLATORS messages.
| 
| In particular, it does not reduce sufficiently the complexity of the 
| <othercredit> section. This complexity is a _major_ cause of compilation 
| errors, amplified by the assymetry of markup between ROLES_OF_TRANSLATORS and 
| CREDIT_FOR_TRANSLATORS.
| 
| In the French team, we started with your idea (two entities, one for the name 
| and the other one for the email), but we quickly switched to the current 
| method, which is perfectly satisfactory.
| 
| So I suggest you reconsider method (1), so every team uses the current French 
| method.

The two methods are not mutually exclusive.  Having an entity for
people's names can help ensuring that they are marked up
completely everywhere.