Re: Proof read updated ejabberd debconf template
Neil Castelino wrote: > Hello Justin, one more question, should I say something in the debcobf > template > instead of "(lowercase)" something like "your input if containing uppercase > characters will be converted to lowercase"? What would be your suggestion? Well, what the first draft says is # Please enter a host name for this Jabber server (lowercase). and I commented > (And couldn't it just quietly normalise the string to lowercase > behind the scenes?) in other words, instead of telling users to avoid uppercase, it could just normalise the input on the assumption that hostnames are always naturally case-insensitive without mentioning it. I was thinking that perhaps you might drop the word "(lowercase)", but I didn't think it mattered very much either way - after all, if people are going to be typing in the name of an existing hostname, that'll be lowercase already. If in fact it's already normalising the string behind the scenes (the same way as hostnames get normalised in ordinary DNS lookups) then I don't think you need to say anything extra - it just makes me slightly more in favour of dropping the word "(lowercase)". -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Re: Proof read updated ejabberd debconf template
Hello Justin, one more question, should I say something in the debcobf template instead of "(lowercase)" something like "your input if containing uppercase characters will be converted to lowercase"? What would be your suggestion? Best, Neil Castelino Justin B Rye schrieb am Do., 10. Aug. 2017, 13:28: > Neil Castelino wrote: > >> This says "host name" twice and "hostnames" once. In principle > >> "hostname" is a technical term regulated by RFCs while "host name" > >> might just mean any name a host is known by. Assuming that you > >> don't actually mean "fully qualified domain name", I'd recommend > >> standardising on "hostname" (to match "username" below). > > > > Since we can use something like "localhost" or "jabber1" or > > "foo.bar.org", would I use still use "hostname" or "host name" as it may > > be a FQDN? > > I think you still want "hostname". For things like Jabber (and the > XMPP RFCs) that's the word used for "however much of an alphanumeric > label you need to identify the server"; you rarely need to distinguish > hostnames from domain names unless you're specifically talking about > DNS. > -- > JBR with qualifications in linguistics, experience as a Debian > sysadmin, and probably no clue about this particular package >
Re: Proof read updated ejabberd debconf template
Alright, perfect! Thank you very much for your help Justin! Best, Neil Castelino On Thu, Aug 10, 2017 at 1:28 PM, Justin B Rye wrote: > Neil Castelino wrote: > >> This says "host name" twice and "hostnames" once. In principle > >> "hostname" is a technical term regulated by RFCs while "host name" > >> might just mean any name a host is known by. Assuming that you > >> don't actually mean "fully qualified domain name", I'd recommend > >> standardising on "hostname" (to match "username" below). > > > > Since we can use something like "localhost" or "jabber1" or > > "foo.bar.org", would I use still use "hostname" or "host name" as it may > > be a FQDN? > > I think you still want "hostname". For things like Jabber (and the > XMPP RFCs) that's the word used for "however much of an alphanumeric > label you need to identify the server"; you rarely need to distinguish > hostnames from domain names unless you're specifically talking about > DNS. > -- > JBR with qualifications in linguistics, experience as a Debian > sysadmin, and probably no clue about this particular package >
Re: Proof read updated ejabberd debconf template
Neil Castelino wrote: >> This says "host name" twice and "hostnames" once. In principle >> "hostname" is a technical term regulated by RFCs while "host name" >> might just mean any name a host is known by. Assuming that you >> don't actually mean "fully qualified domain name", I'd recommend >> standardising on "hostname" (to match "username" below). > > Since we can use something like "localhost" or "jabber1" or > "foo.bar.org", would I use still use "hostname" or "host name" as it may > be a FQDN? I think you still want "hostname". For things like Jabber (and the XMPP RFCs) that's the word used for "however much of an alphanumeric label you need to identify the server"; you rarely need to distinguish hostnames from domain names unless you're specifically talking about DNS. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Re: Proof read updated ejabberd debconf template
Hello Justin, thank you for the detail, it is very helpful! On Thu, Aug 10, 2017 at 12:24:21AM +0100, Justin B Rye wrote: > This says "host name" twice and "hostnames" once. In principle > "hostname" is a technical term regulated by RFCs while "host name" > might just mean any name a host is known by. Assuming that you > don't actually mean "fully qualified domain name", I'd recommend > standardising on "hostname" (to match "username" below). Since we can use something like "localhost" or "jabber1" or "foo.bar.org", would I use still use "hostname" or "host name" as it may be a FQDN? Best, Neil Castelino
Re: Proof read updated ejabberd debconf template
Neil Castelino wrote:
> I am helping maintain the ejabberd package and was hoping to get someone
> to quickly proofread the changes that I made to the template and let me
> know if it's alright before I ask for translations. Thank you!
Okay - thanks for providing the actual template for easy diffing!
> Template: ejabberd/hostname
> Type: string
> Default: localhost
> _Description: Host name for this Jabber server:
> Please enter a host name for this Jabber server (lowercase).
> .
> If you would like to configure multiple hostnames for this server, you will
> have to do so manually in /etc/ejabberd/ejabberd.yml after installation.
This says "host name" twice and "hostnames" once. In principle
"hostname" is a technical term regulated by RFCs while "host name"
might just mean any name a host is known by. Assuming that you
don't actually mean "fully qualified domain name", I'd recommend
standardising on "hostname" (to match "username" below).
(And couldn't it just quietly normalise the string to lowercase
behind the scenes?)
> Template: ejabberd/user
> Type: string
> _Description: Jabber server administrator username:
> Please provide the name of an account to administrate the ejabberd server.
> After the installation of ejabberd you can use this account to log in with
> any
> Jabber client to do administrative tasks or go to
> https://${hostname}:5280/admin/ and log in with this account to enter the
> admin
> interface.
That's a bit hard to follow, because the "or" is only offering an
alternative to the "with any Jabber client" part, not the "use this
account to log in [...] to do administrative tasks" part (which is
true either way). And I assume it's saying that the second
alternative is using any web browser... if so, make it:
After the installation of ejabberd, you can log in to this account using
either any Jabber client or a web browser pointed at the administrative
https://${hostname}:5280/admin/ interface.
> .
> You only need to enter the username part here (such as ${user}), but
> the full Jabber ID (such as ${user}@${hostname}) is required to
> access the ejabberd web interface.
> .
> Please leave this field empty if you don't want to create an
> administrator account automatically.
>
> Template: ejabberd/password
> Type: password
> _Description: Jabber server administrator password:
> Please enter the password for the administrative user.
>
> Template: ejabberd/verify
> Type: password
> _Description: Re-enter password to verify:
> Please enter the same administrator password again to verify that you have
> typed it
> correctly.
>
> Template: ejabberd/nomatch
> Type: error
> _Description: Password input error
> The two passwords you entered did not match or were empty. Please try again.
>
> Template: ejabberd/invaliduser
> Type: error
> _Description: Invalid administrator account username
> The username you have typed contains forbidden characters. Please respect
> the
> JID syntax (http://tools.ietf.org/html/rfc6122#appendix-A.5). If you used
> a full JID (e.g. user@hostname), you have to use the same host name
> you typed into the host name configuration step.
"Hostname" again, and that URL redirects to HTTPS.
While I'm changing that line I'd rephrase it to
If you used
a full JID (e.g. user@hostname), the hostname needs to match the one
previously specified.
> Template: ejabberd/invalidhostname
> Type: error
> _Description: Invalid hostname or special characters in hostname
> The hostname which you have typed contains forbidden characters. Please
> correct
> the hostname entered.
This starts by implying that having special characters in the
hostname is just one of the things that can trigger the error, but
then carries on as if it's the only possible diagnosis. Assuming
that the problem might be, for instance, that I've typed in a
thousand hyphens, it should probably be:
_Description: Invalid hostname
The hostname specified contains forbidden characters or is otherwise
invalid. Please try again.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-english@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.
Template: ejabberd/hostname
Type: string
Default: localhost
_Description: Hostname for this Jabber server:
Please enter a hostname for this Jabber server (lowercase).
.
If you would like to configure multiple hostnames for this server, you will
have to do so manually in /etc/ejabberd/ejabberd.yml after installation.
Template: ejabberd/user
Type: string
_Description: Jabber server administrator username:
Please p
Proof read updated ejabberd debconf template
Hello,
I am helping maintain the ejabberd package and was hoping to get someone
to quickly proofread the changes that I made to the template and let me
know if it's alright before I ask for translations. Thank you!
Best,
Neil Castelino
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-english@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.
Template: ejabberd/hostname
Type: string
Default: localhost
_Description: Host name for this Jabber server:
Please enter a host name for this Jabber server (lowercase).
.
If you would like to configure multiple hostnames for this server, you will
have to do so manually in /etc/ejabberd/ejabberd.yml after installation.
Template: ejabberd/user
Type: string
_Description: Jabber server administrator username:
Please provide the name of an account to administrate the ejabberd server.
After the installation of ejabberd you can use this account to log in with any
Jabber client to do administrative tasks or go to
https://${hostname}:5280/admin/ and log in with this account to enter the admin
interface.
.
You only need to enter the username part here (such as ${user}), but
the full Jabber ID (such as ${user}@${hostname}) is required to
access the ejabberd web interface.
.
Please leave this field empty if you don't want to create an
administrator account automatically.
Template: ejabberd/password
Type: password
_Description: Jabber server administrator password:
Please enter the password for the administrative user.
Template: ejabberd/verify
Type: password
_Description: Re-enter password to verify:
Please enter the same administrator password again to verify that you have
typed it
correctly.
Template: ejabberd/nomatch
Type: error
_Description: Password input error
The two passwords you entered did not match or were empty. Please try again.
Template: ejabberd/invaliduser
Type: error
_Description: Invalid administrator account username
The username you have typed contains forbidden characters. Please respect the
JID syntax (http://tools.ietf.org/html/rfc6122#appendix-A.5). If you used
a full JID (e.g. user@hostname), you have to use the same host name
you typed into the host name configuration step.
Template: ejabberd/invalidhostname
Type: error
_Description: Invalid hostname or special characters in hostname
The hostname which you have typed contains forbidden characters. Please correct
the hostname entered.
