> Why were all the double quotes changed to apostrophes? That feels like an > American vs. British English change, and I think double quotes are more > widely used. (This won't matter for translations, of course.) This has been discussed on dle and we finally settled that the use of single quote is what's the closest to the official English typography's quotes. Those are unfortunately non ASCII characters, which would be a problem. Noone during the discussion raised that double/single quotes is an American|British choice, indeed. I'm pretty ignorant on that issue and finally followed the advice of other reviewers. Most of them are from UK but the general policy for dle review is to follow American English conventions. > One other general English issue: I'm not sure if we should use Kerberos4 > and Kerberos5 to refer to the versions of the protocol instead of Kerberos > v4 and Kerberos v5, or Kerberos V4 and Kerberos V5. The primary MIT > Kerberos documentation uses Kerberos V4 and Kerberos V5. Google returns > 58,000 hits for "Kerberos V4" and 42,000 hits for "Kerberos4", and many of > the latter are filenames. (89,000 hits for "Kerberos 4" with the space.) > This *will* matter for translations. Well, we can still change this. Let's settle for 'Kerberos V4'? In such cases, however, a lower cap 'v' seems nicer to me: 'Kerberos v4' I leave the call to you, Russ and krb5 maintainers. > Maybe rephrase the last paragraph as: > > Alternatively, the mode can be set to "full", allowing Kerberos4 > clients to get initial tickets even when preauthentication would > normally be required; to "disable", returning protocol version errors > to all Kerberos4 clients; or to "none", which tells the KDC to not > respond to Kerberos4 requests at all. OK. > Change "use" to "enable" here, I think. "Use" has a slightly different > meaning that doesn't seem as appropriate. OK. > As mentioned earlier, the wording will change as soon as I get around to > having the postrm script use debconf to prompt rather than relying on an > answer given during installation. Yep. Sounds fair. I suggest we handle this when you'll be ready, even if that requires a further call for translations updates. > I'll probably restore the two spaces after periods. I find it much more > readable, and this is a question of style. > > As a matter of procedure, I would recommend against changing things like > that as part of this sort of review, since it makes the diff considerably > longer and, as a question of personal preference with no right answer, I > don't think it's really a good sort of change to be making. Well, I don't exactly agree here. Using or not using double spaces after periods is a matter of general style and consistency among packages, so this is why we include such changes. For sure, this is some unwritten|not yet written policy enforcment, but this has some importance for the overall consistency impression of our users. However, the maintainer(s) has of course the very final word. Please confirm your call about this issue. We need to have this settled *before* the call for translations as changing single spaces to double spaces *will* fuzzy translations and therefore need manual processing. I re-attach all debconf templates as they are now. Issues to solve: -single or double quotes -Kerberos4|Kerberos v4|Kerberos V4 -double spaces after periods
# These templates have been reviewed by the debian-l10n-english # team # # If modifications/additions/rewording are needed, please ask # for an advice to email@example.com # # Even minor modifications require translation updates and such # changes should be coordinated with translators and reviewers. Template: krb5-admin-server/newrealm Type: note _Description: Setting up a Kerberos Realm This package contains the administrative tools required to run the Kerberos master server. . However, installing this package does not automatically set up a Kerberos realm. This can be done later by running the 'krb5_newrealm' command. . Please also read the /usr/share/doc/krb5-kdc/README.KDC file and the administration guide found in the krb5-doc package. Template: krb5-admin-server/kadmind Type: boolean Default: true _Description: Run the Kerberos5 administration daemon (kadmind)? Kadmind serves requests to add/modify/remove principals in the Kerberos database. . It is required by the kpasswd program, used to change passwords. With standard setups, this daemon should run on the master KDC.
# These templates have been reviewed by the debian-l10n-english # team # # If modifications/additions/rewording are needed, please ask # for an advice to firstname.lastname@example.org # # Even minor modifications require translation updates and such # changes should be coordinated with translators and reviewers. Template: krb5-kdc/debconf Type: boolean Default: true _Description: Create the Kerberos KDC configuration automatically? The Kerberos Domain Controller (KDC) configuration files, in /etc/krb5kdc, may be created automatically. . By default, an example template will be copied into this directory with local parameters filled in. . Administrators who already have infrastructure to manage their Kerberos configuration may wish to disable these automatic configuration changes. Template: krb5-kdc/krb4-mode Type: select __Choices: disable, full, nopreauth, none Default: none _Description: Kerberos4 compatibility mode to use: By default, Kerberos4 requests are allowed from principals that do not require preauthentication ('nopreauth'). This allows Kerberos4 services to exist while requiring most users to use Kerberos5 clients to get their initial tickets. These tickets can then be converted to Kerberos4 tickets. . Alternatively, the mode can be set to 'full', allowing Kerberos4 clients to get initial tickets even when preauthentication would normally be required; to 'disable', returning protocol version errors to all Kerberos4 clients; or to 'none', which tells the KDC to not respond to Kerberos4 requests at all. Template: krb5-kdc/run-krb524 Type: boolean _Description: Run a Kerberos5 to Kerberos4 ticket conversion daemon? Krb524d is a daemon that converts Kerberos5 tickets into Kerberos4 tickets for the krb524init program. . It is recommended to enable that daemon if Kerberos4 is enabled, especially when Kerberos4 compatibility is set to 'nopreauth'. Template: krb5-kdc/purge_data_too Type: boolean Default: false _Description: Should the data be purged as well as the package files? By default, purging this package will not delete the KDC database in /var/lib/krb5kdc/principal since this database cannot be recovered once it is deleted. . Choose this option if you wish to delete the KDC database when this package is purged, deleting all of the user accounts and passwords in the KDC.
Description: Digital signature