RE: [Doxygen-users] Again about translations...
Brought to you by:
dimitri
From: Alessandro F. <afa...@da...> - 2001-05-04 17:19:50
|
Hi Petr, ... > As you adviced, the approach like this... > > > QCString trMemberList(const QCString& className) > > ...is the right way. Glad to hear you agree. ... > In other words, changing the trMemberList() and similar > to take some arguments will affect the core code, but > will not break the other maintainers work, nor require from > them any effort until they decide to update their translator. > [ This means that the changes will be less painful (for > Dimitri and others) and the development here can be > more rapid (because of avoiding dependency on > the language maintainers). ] I think changing the core code would be undoubtedly painful, but there should be a strong motivation in the change too. > So, the main problem is to find, where the old method > was called and think deeply whether newly proposed > method will not create some apparent obstacles in future. That's the hardest part cause you must grant sufficient flexibility to guard against every possible future requirement (or at least try to satisfy a large class of them) without even imagining it. > Once this is decided, Dimitri (or someone closely > cooperating with him) can change the interface of > the decided method and create its appropriate > default implementation in the adapter class which > takes advantage of the older method, which > already gives translated string or substring. Agreed. > The maintainters could always look inside a documentation > whether their implementation is up-to-date or should > be updated. (This was not released yet, but the > perl script for generating the documentation will probably > be released soon.) Yes, the latest deep changes in 1.2.7 forced me to a complete revision. > There already are examples of the changed interface > in the last CVS releases. You may have a look at > trFiles() which was totally replaced by trFile(params). > There also are good candidates to use exactly the same > approach, like trAuthors() and trAuthor() -- not done yet. I'll look closer at it > Conclusion: Let's start discussing the changes and > select the first candidates. I haven't the source handy, but from memory I cite those tr functions which produce section titles containing entity names (e.g.class or struct names). More to come. Alessandro |