doxygen-develop

[Doxygen-develop] feature request: utf encoding

[<pm...@fr...>]

Hello,

since the encoding of my source files is utf-8 since some time, would it be
possible to add utf support to doxygen?

For HTML, this means
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
instead of
<meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">

Greetings and thanks a lot for this great tool, I use it more and more!
Peter

-- 
http://pmrb.free.fr/contact/

Re: [Doxygen-develop] feature request: utf encoding

[Jens S. <jen...@us...>]

Hi Peter,

On Fri, Nov 24, 2006 at 06:43:30PM +0100, Peter M=FCnster wrote:
> since the encoding of my source files is utf-8 since some time, would i=
t be
> possible to add utf support to doxygen?

of course. It should be not very difficult.

> For HTML, this means
> <meta http-equiv=3D"Content-Type" content=3D"text/html;charset=3Dutf-8"=
>
> instead of
> <meta http-equiv=3D"Content-Type" content=3D"text/html;charset=3Diso-88=
59-1">

I tried it once for German documents but did not complete it.
Nevertheless the attached patch give should you sufficient ideas what
needs to be changed. (translator_de.h needs to be recoded to UTF-8 as
well, this is missing in the patch to keep it small.)

HTML is trivial, but do not forget other output formats. LaTeX could
cause trouble. I noticed failures for a special Doxygen configuration.
I think it was the PDF output created via LaTeX which failed because of a
missing escaping of "_" but I forgot about it.

After manual fixing two or three escaping errors I was able to process a
large document containing German and Russian texts.

Manual pages should also not depend on the encoding (the manual page
encoding is hardcoded into man. It may be necessary to recode these from
UTF-8 via an external script on systems which expect classical
encodings).

I don't know the RTF format.

Using UTF-8 per default would also allow to drop the stupid Use Windows
encoding option in the config file.
It's also still possible to use INPUT_FILTER =3D "iconv -f iso-8859-1 -t =
UTF-8 -c"
for latin1 encoded source to keep these workings.

Jens

Re: [Doxygen-develop] feature request: utf encoding

[<pm...@fr...>]

On Sat, 25 Nov 2006, Jens Seidel wrote:

> Using UTF-8 per default would also allow to drop the stupid Use Windows
> encoding option in the config file.

Or even better: instead of
USE_WINDOWS_ENCODING = yes/no
something like
USE_ENCODING = utf-8/iso-8859-1/iso-8859-15/etc. (default = utf-8)

>      /*! return the language charset. This will be used for the HTML output */
>      virtual QCString idLanguageCharset()
>      {
> -      return "iso-8859-1";
> +      return "UTF-8";
>      }

Thanks! For the time being, I'll use this part of your patch.
Cheers, Peter

-- 
http://pmrb.free.fr/contact/

Re: [Doxygen-develop] feature request: utf encoding

[<pm...@fr...>]

On Sun, 26 Nov 2006, Peter M=FCnster wrote:

> On Sat, 25 Nov 2006, Jens Seidel wrote:
>=20
> > Using UTF-8 per default would also allow to drop the stupid Use W=
indows
> > encoding option in the config file.
>=20
> Or even better: instead of
> USE_WINDOWS_ENCODING =3D yes/no
> something like
> USE_ENCODING =3D utf-8/iso-8859-1/iso-8859-15/etc. (default =3D utf=
-8)

Hello and happy new year!

I've just seen, that there are already such requests in the bugzilla
database (numbers 150916, 159291 and 330109).

Is there perhaps already a developer working on this?

Cheers, Peter

--=20
http://pmrb.free.fr/contact/

Re: [Doxygen-develop] feature request: utf encoding

[Hyunwoo P. <par...@dg...>]

Hi. :)

I also have same problem.
so, I added one more language, "english.utf8" for utf8 with attached patch file.

in doxyfile config, "OUTPUT_LANGUAGE = english.utf8" will select the english and utf8 encoding.

I think it`s very easy to make another language such as korean.utf8, french.utf8, ..., like this manner.

Regards.
Hyunwoo Park.


Peter Münster 쓴 글:
> On Sun, 26 Nov 2006, Peter Münster wrote:
> 
>> On Sat, 25 Nov 2006, Jens Seidel wrote:
>>
>>> Using UTF-8 per default would also allow to drop the stupid Use Windows
>>> encoding option in the config file.
>> Or even better: instead of
>> USE_WINDOWS_ENCODING = yes/no
>> something like
>> USE_ENCODING = utf-8/iso-8859-1/iso-8859-15/etc. (default = utf-8)
> 
> Hello and happy new year!
> 
> I've just seen, that there are already such requests in the bugzilla
> database (numbers 150916, 159291 and 330109).
> 
> Is there perhaps already a developer working on this?
> 
> Cheers, Peter
>