config.xml to Chinese #9894
Comments
wb2712
changed the title
albert-github
added
needinfo
|
No idea what you want to express with this issue and the images that you show. Why do you want to translate doxygen yourself and not use a version from GitHub Actions like from: https://github.com/doxygen/doxygen/actions/runs/4330803787 ? Regarding the 2 issues:
I can see that the |
|
Because my mother tongue is Chinese, English is not very good, and I also want to recommend this software to my colleagues, but there are too many configuration options, I hope to read Chinese directly |
|
The picture shows the environment I compiled with mingw, because I did not use msvc to compile, so the format of the dependent library is different Some modifications were also made in order to compile successfully in my environment. Finally, the compilation is successful, but the file size is different from the official release version, so it cannot be run |
Strange that the created executable cannot be run. When you don't use the MSVC environment, did you install the iconv under mingw? |
|
The screenshot shows |
|
The source code I just downloaded two days #9854 Compile successfully after rolling back this change |
The 1.9.1 version has not been changed so this would be logical (we don't do back patches).
Might be a bit of a cache effect / the fact that during the first part of the run a lot of dot images were already transformed into images (something that doxygen remembers by means of the md5 files on the HTML directory. (Cannot tell as I don't see the doxygen settings file you used). Still no idea "What is the purpose of translating the config.xml into Chinese?" When multiple languages should be supported there can be many more things to be considered, like:
|
1.9.6 The problem still exists, I am using the 1.9.6 version, I said the wrong version
This software is very useful, I am in China, I want to recommend this software to my colleagues, but there are too many configuration options, and the English explanation is not friendly, so I simply translated the explanation text in config.xml, But in the end it failed. iconv "everything software"
By the way, can this save function have a different filename depending on the log and configuration? Manually modify the file name each time |
|
generated_src |
|
There are indeed a lot of configuration options so one can loose track. Furthermore the description is sometimes a bit cryptic and for non-native English speakers quite often hard to understand (I'm not a native English speaker either). I wanted to look at doxygen_config.txt but it says: "Not found" so it is not possible to see your settings. I looked at the log file in doxygen_log.zip and see here:
lets do some tests
Furthermore I see in doxygen_log.zip some non alarming things:
You mentioned:
which save function? Note: the last master version of doxygen (1.9.7 (2b9f286)) has a new setting (and some reorganization / different placing of some settings) so this means that your config.xml doesn't work anymore with current master (due to the new setting).
Regarding the configoptions.cpp, this file contains still a mixture of translated text and original English text (as there is some extra text added to this file due to the xml settings that are translated into more readable text like: but in general these automatically generated texts will, probably, be quite well understandable. |
|
I had a closer look at the fact that I got problems in respect to: this can be easily solved in the original with the other imports and by adding just befor the Resulting file: configgen.py.tar.gz Note: this is only working for Python 3! Compiling the code went OK on my side.
Generation the documentation fails (though the html documentation is generated), the problem that does arise here is that there are warnings given, indicating that the I only looked at the Another problem that will occur with the generation of the documentation is that the pdf will not be generated as the texts are now a mix of English and Chinese and Chinese requires a different engine for generating the pdf. That said I think the manual should only appear in English (otherwise all other texts should also be translated and just Google translate is not sufficient for this). |
|
@doxygen Some points:
The big issue for all this is the possibility to translate (requiring some dedicated people who can do the initial translation), maintain the translations and the gains from it. What is your opinion about all this? |
|
I'm trying to solve this error |
Which error? |
|
If you can't solve it in the short term, I can accept the function of only use to help understand and view the configuration options Use the official English version during actual operation
This preservation Even if the software compiled with this file cannot run normally, as long as you can check the configuration explanation, it is acceptable |
.../doc/config.doc:2160: error: Found unknown command '\end' |
|
Regarding the |
|
My compilation environment is python3 |
|
Did you try to build the documentation i.e |
yes ，You try my new file in the last reply |
|
No I didn't as I didn't find time yet to study it and the name |
|
Regarding the changing of the "save" file name you mean the "Save log ..." functionality in the doxygen wizard? |
|
Yes, it can be used to export configuration, then you should change the name |
|
It is still the log as you got the information by means of |
|
Of the warnings as indicated in #9894 (comment) the warnings |
So far the focus has been to be able to make the output language specific, basically assuming the developers using doxygen can speak English well enough to configure and run it, but the readers of the documentation do not need to speak English. I think it is ok to make it easier for someone to localize the configuration and doxywizard strings in the GUI, but for us to keep other localizations up to date is not really maintainable. Given how difficult it already is to keep the output translators up to date now, I think it is better to for others to maintain this in separate repositories if they have a need for it. For doxywizard |
|
So with the |
Give me English, I can't retrieve it in xml |
|
I don't quite understand how to operate in the background |
|
I don't know what you mean with:
There are no further English texts for this as the Chinese part comes from the the run with your config.xml, or do you mean a The English version of the file: english_config.doc.tar.gz
Don't get this I have configuration files but no source code so I cannot test this. |
|
As long as the configuration is the same as mine, test with any open source code, C++version.
…---Original---
From: ***@***.***>
Date: Tue, Mar 7, 2023 19:23 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [doxygen/doxygen] config.xml to Chinese (Issue #9894)
I don't know what you mean with:
Give me English, I can't retrieve it in xml
There are no further English texts for this as the Chinese part comes from the the run with your config.xml, or do you mean a doc/config.doc as run with the default English version? The later might have slightly different line numbers! (I see e.g. that the first warning gives in the Chines version line 1451 but it is in the English version 1448, probably the word command has been translated into Chinese).
The English version of the file: english_config.doc.tar.gz
I don't quite understand how to operate in the background
My configuration has been given to you, you can try
Don't get this I have configuration files but no source code sou I cannot test this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I can reproduce the "pdf" problem with the doxygen internals, looks like the problem occurs with the non call / caller graphs (i.e. collaboration / inheritance / include ... graphs). |
|
\ref must be followed by English
|
|
The effect I want has been solved, can’t run doxygen does not affect my use |
Based on some comments in doxygen#9894 make the generated texts in the output configurable: - setup defaults (configgenpy: setDefaultGenerate) - read the values to be read (configgen.py: parseGenerate) - set the texts to be used (config.xml, for the English texts these are the same as the defaults in configgen.py)
|
Did you notice this attachment |
The current performance bottleneck is this step, which can only run in a single thread. Is there a way to increase the speed of this step?
|
I didn't really have time to look at it and I also saw your remarks #9894 (comment) so I thought all was OK had low priority.
No, the HtmlHelp compiler is an old and non maintained program. There is no chance getting it faster other than using another program for it that has the same functionality. Regarding the error (about the 488 character limit), I didn't see it before, please attach a, small, self contained example (source+configuration file in a, compressed, tar or zip file) that allows us to reproduce the problem? Please don't add external links as they might not be persistent. |
There may be a problem with the translation, I don't quite understand what it means This compressed package is the part I modified in the process of solving the Chinese configuration before, give it to you synchronously. In addition, when running at full speed as mentioned before, the gui will freeze, I have solved it,
Which software also parses hhp files?
source https://github.com/egege/webrtc-src/tree/master/modules |
|
Building the doxygen documentation I get the error this is due to the line: that should read Note the extra whitespace after the Or in terms of the original config.xml file this is line 1258. (I also get an error generating the pdf version, but this is due to the fact that not all the right packages are loaded for the Chinese translation).
No advise, please search the web.
small example ? |
I have tried other, only this folder can reproduce |
Based on some comments in doxygen#9894 make the possibility to read real utf-8 files hand writ it properly to the generated files
Based on some comments in doxygen#9894 where a warning was shown like ``` Warning: Keyword string: ... is too long. The maximum size is 488 characters. ``` tit was found that this was due to an extremely long `value` field in the `index.hhk` (index file), limiting this field and placing an ellipse when necessary
|
After some searching and building (without call and caller graphs as it would take quite long on the first build) I found the problem regarding the "488" problem, I've just pushed a proposed patch, pull request #9919 Regarding the utf-8 support I created the proposed pull request #9917 and for some flexibility in the generated string texts I created the proposed pull request #9912 |
albert-github
added
the
fixed but not released
Pay attention to this interface freeze problem. In the previous screenshot, I gave the code to solve it.
Other software is also based on HtmlHelp, there is no better way. |
|
This issue was previously marked 'fixed but not released', |
doxygen
removed
the
fixed but not released
Describe the bug
config to Chinese by google translate
The final compiled program cannot run
In the process, some problems were solved and shared here
I use this software to generate manuals for some large-scale open source software, which helps me quickly understand, but the first run usually freezes and can only be forced to kill, and the second time is much better
FindIconv.cmake
Unable to compile and run correctly, I ended up shielding this problem by a tricky way, but did not solve this problem
The following two issues are not fixed in my environment
#9854
#8335
Expected behavior
Use my translated configuration files in the next version as soon as possible
Or to solve my compilation problem
Screenshots
Additional context
config-chinese.txt
configgen.txt
The text was updated successfully, but these errors were encountered: