Dmitry wrote: >>> * Now localization names have to be specified twice while building, e.g. >>> -Did=article-ru -Dsfx=ru. It's very inconvenient. If suffix is intended >>> to specify the language, why do we need a special article ID then?
>> The article ID must always be specified, otherwise the entire documentation >> set is built, which is almost never what you want. (In the case of PDF, this >> even means that you get the entire set in one document.) >> >> The suffix is needed for non-English versions. Technically, it doesn't >> specify a language, but a subdirectory. It is necessary to find the right >> sources. If you mostly work in the same language, you can set it as a >> default in manual/src/build/build.xml. > If they both serve the same purpose (logically, not technically), why > cannot we modify the build scripts so that the entered suffix would be > concatenated with the article name before further processing? So that > -Did=article -Dsfx=ru would be enough for the Russian version instead of > specifying "ru" twice? It's not hard to implement, but there are two reasons why I don't like it: 1) Purity. The id argument is for passing the id of the manual (or part thereof) that has to be built. If you remove part of it, it's no longer what it's supposed to be. 2) Ending ids with hyphen + language code in the non-English sets is a convention, not a hard requirement. There are docs that don't have this suffix in the ids. After the suggested change, you couldn't build those docs anymore. Also, I still think the benefit (you save 3 keystrokes out of 30-50) is simply not worth it. True: if you build 6 language versions of a certain manual one after another, you have to replace each language code twice on the command line. I would find that pretty annoying too :-) But again, this is extremely exceptional! Nobody has ever had to do this before, and in all likeliness nobody ever will. People build their own docs, not those in other languages, and certainly not at the same time. You just had the bad luck to be the person that had to rebuild *everything* for the transition to the new site. (And even *that* would not have been necessary if the site builders had taken more care to preserve existing links and file names.) All that being said, I'd like to hear more opinions, especially from the non-English contributors. If you guys really want it, it can be done. Cheers, Paul Vinkenoog ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
