New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RTF text encoding does not use codepage (Origin: bugzilla #564614) #3199

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity major in component general for ---
Reported in version 1.5.7.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2008-12-15 14:11:53 +0000, gobi wrote:

When doxygen generates RTF it always generate text in UTF-8 encoding. It does not see the translator. By RTF spec RTF text must be charset encoded but everything gets UTF-8 and all text is broken in RTF.

On 2008-12-16 06:20:59 +0000, gobi wrote:

It looks I reported wrong this bug. I investigated some more and figured out that problem is different.

The problem is:

For example I am creating Japanese documentation. It looks that Doxygen internally convert input files to UTF-8. Afterward it converting to translator encoding then it calls postProcess virtual method of Generators. At this point RTF postProcess method works somehow wrong. At least in my case which is Japanese.

So I commented out postProcess call then RTF has got readable. Doxygen is finishing not clearly. However it generates RTF it finishes with this error log:

.....
Combining RTF output...
Error: RTF integrity test failed at line 3268 of /home/gobi/workspace/socnew/docs/rtf/refman.rtf due to a bracket mismatch.
Please try to create a small code example that produces this error
and send that to dimitri@stack.nl.

On 2008-12-16 18:39:51 +0000, Dimitri van Heesch wrote:

Can you attach a minimal example (source + config file in a zip) that allows me to reproduce the problem?

On 2008-12-17 07:01:29 +0000, gobi wrote:

Created attachment 124842
Minimal code produces error to create RTF documents in Japanese

When you produce japanese documentation from attached source you will receive following error and RTF won't be opened by either Open Office3.0 and MS Office.


Error: RTF integrity test failed at line 166 of /home/gobi/workspace/socnew/docs/rtf/refman.rtf due to a bracket mismatch.
Please try to create a small code example that produces this error
and send that to dimitri@stack.nl.

On 2008-12-17 07:12:52 +0000, gobi wrote:

Created attachment 124844
Small code + config + generated broken RTF

OK, I A attached very small code + configuration + generated RTF with error.

Thank you.

On 2008-12-25 11:40:49 +0000, Dimitri van Heesch wrote:

I can reproduce the integrity warning with version 1.5.7.1, but is has disappeared in my working version, so please check if the problem is gone in the next official release.

On 2009-02-24 15:36:30 +0000, Alexey Efimov wrote:

I have a same problem in version 1.5.8 running on Windows XP SP3.
I want generate russian documentation in RTF format but have error message:

Combining RTF output...
Error: RTF integrity test failed at line 246 of Z:/prcg_doc2/rtf/refman.rtf due to a bracket mismatch.

I've checked some of OUTPUT_LANGUAGE values, and got the same results for Chinese, Greek, Hungarian, Japanese, Russian, Ukrainian languages etc.

On 2009-02-24 15:56:00 +0000, Alexey Efimov wrote:

Created attachment 129413
code + small config + generated rtf

Attached a code example, small config file and produced rtf doc.

On 2009-02-24 15:57:13 +0000, Alexey Efimov wrote:

Created attachment 129414
code + small config + generated rtf

Attached a code example, small config file and produced rtf doc.

On 2011-08-07 07:47:53 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2011-08-14 14:05:31 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.5. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment