Quoting Torsten Landschoff ([EMAIL PROTECTED]): > Agreed. The wording was not mine anyway but I did not get around to fix > this. How about: > > _Description: Omit OpenLDAP server configuration > If you enable this option, no initial configuration or database will be > created for you. > > ?
This seems fine to me. You may just need adding the final question mark in the short description of the template (common use for boolean templates which should be the only ones asking questions, indeed....at least IMHO) > > > Template: slapd/dump_database > > Type: select > > Choices: always, when needed, never > > Default: when needed > > -_Description: Dump databases to file on upgrade > > - Before upgrading to a new version of the OpenLDAP server the data of > > +_Description: Dump databases to file on upgrade: > > Hmm, that colon would look ugly in the dialog frontend, don't you think? > I'd expect the UI to add it when needed. Am I mistaken? Theoretically, yes, but that became quite common use now. UI adding ponctuation is really not trivial as the way punctuation is used varies from one language to another (for instance, questions in Spanish have to start with a reverted question mark). In dialog, such colon does not really look weird as the "short description" usually comes just before the field where the input occurs. > > Template: slapd/move_old_database > > Type: boolean > > Default: true > > -_Description: Move old database > > +_Description: Move old database? > > Why a question mark? That's a yes/no question which debconf options > should not be!? Well, I would say that when asking someone about a Yes/No answer, you're indeed asking him/her a question..:-) This is a bit debatable, for sure (for instance, the gnome interface does not give a Yes/No choice but has a checkbox). Indeed, I tend to recommend using questions for boolean because, this is what seems the most appropriate in the most common situation. > > > There are still files in /var/lib/ldap which will probably break > > - the configuration process. With this option enabled the maintainer > > + the configuration process. If you choose this option, the maintainer > > s/choose/enable/ I'd say. Yep. The only thing which influences me is that we have often recommended the "if you choose this option" wording in other packages. > > > Template: slapd/admin > > Type: string > > -_Description: Admin entry > > +_Description: Admin entry: > > The admin entry is the entry in the directory which has full read and > > write access. > > Hrm, this should be removed as it is not used anymore. I suggest unmarking those for translation, then (or removing them completely of course)....However, if there's a chance for these to be used in the future, just keep them so that you also keep the existing translations. > > -_Description: Which database backend would you like to use? > > +_Description: Database backend to use: > > While the BDB backend is the recommended choice of the OpenLDAP > > developers, > > the LDBM backend has proven to be more reliable for some Debian users, > > especially when the BDB database wasn't properly configured. When using > > the > > Guess I should add "hdb". > > Okay, enough food for thought ;) That very last template was indeed a big nightmare for me. A lot of jargon involved and thus tricky to translate. It is indeed quite likely that it exceeds the screen size in the dialog interface for a 80x25 terminal, so it will for instance scroll when installed on an initial installation. You can test this by running the podebconf-display-po on an existing PO file (even incomplete). Don't forget sending me the new templates.pot file as soon as the changes are made....No problem if further changes are required. Indeed, if the templates are still very likely to change, I suggest the following: -post to debian-i18n and mention that translating openldap2.2 templates is currently not really needed -as soon as they're stabilized, then post a call for translations in the same place, pointing people to the templates.pot file and mentioning existing translations. In the same time, warn existing translators with podebconf-report-po Grüsse...(where the hell is the german "ess" on my french keyboard? :-)))
