[Doxygen-develop] Info on the status of the language translators (March 20, 2003)

[Petr P. <Pr...@sk...>]

Related to the doxygen 1.3-rc3-20030317 in CVS. Full
translator_report.txt
included in the attached zip file. Posted to doxygen-develop, copied to
doxygen-users. The previous report was from February 17, 2003.

Summary:=20
 - Three new up-to-date translators.
 - New option USE_WINDOWS_ENCODING is important for some languages.=20
 - The Hungarian and Norwegian maintainers are asked to try harder.
 - Polish and Danish maintainers are asked to polish ;) their code.
 - Finnish and Swedish are suggested to be removed from doxygen 1.3.


Hi,

Firstly, thanks to all active language maintainers. Three of the
translators
became up-to-date since the last info: Croatian, Korean, and Polish. For
Polish and Danish, please have a look at the details in the translator
report.

Thanks

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
ATTENTION!=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

If you are the language maintainer, this is a good time to update your
translator now because the 1.3 release looks to happen soon. Please,
think
about users who do not use sources from CVS, but only the precompiled
binaries. The 1.3 will be a bigger leap. I guess that more people would
like
to try it.

Thanks

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
IMPORTANT!
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Dimitri included a new option USE_WINDOWS_ENCODING which makes selecting
output encoding dynamic. When the language defines different encoding
for MS
Windows and different for Unix, then the translator probably uses the
decode() or similar inline method to produce the desired output encoding
of
compiled-in strings. It ensures that strings from the translator_xx.h
source
will be converted to the desired encoding. The strings from the
processed
files are expected to use the same encoding that is suggested by the new
option.

Earlier, the decision was done in compile time: doxygen compiled under
Windows assumed that the processed files will be in Windows encoding;
doxygen compiled under Unix assumed theat the processed files will be in
Windows encoding. In other words, it was impossible to generate
correctly
encoded documentation from the processed files that were prepared using
the
other OS (in some languages).

If your language uses that approach, please check if the new option is
used
and if it used correctly in your translator_xx.h.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Current status
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The total is 28 languages: 13 of them are up-to-date, 11 of them is only
slightly behind -- max. 8 simple methods should be implemented to become
up-to-date. Two languages require more work: Hungarian and Norwegian. So
I
ask the maintainers to try a bit harder. The doxygen infrastructure
(i.e.
the translator adapter classes) could then be simplified. Look at the
translator_report.txt in the attached zip file.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Suggestion to remove Finnish and Swedish
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

We still did not found new Finnish and Swedish maintainers. Their
translators became extremely obsolete, and it seems that the original
maintainers are not in touch with doxygen any more (read it
"unreachable").
 =20
The mentioned translators do not support so many methods, that it is
probably more correct to use the English translator instead. So I
suggest to
remove the the Finnish and Swedish languages support completely from
doxygen
version 1.3.

 =20
With regards,
  Petr

--=20
Petr Prikryl (pri...@sk...)