[Zope3-checkins] Re: SVN: Zope3/trunk/src/zope/app/pas/ loginform.pt added

Mon Oct 11 16:54:41 EDT 2004

Ralph Barthel wrote:
> 
> Added: Zope3/trunk/src/zope/app/pas/browser/loginform.pt
> ===================================================================
> --- Zope3/trunk/src/zope/app/pas/browser/loginform.pt	2004-10-11 13:36:03 UTC (rev 27975)
> +++ Zope3/trunk/src/zope/app/pas/browser/loginform.pt	2004-10-11 13:43:22 UTC (rev 27976)
> @@ -0,0 +1,32 @@
> +<html metal:use-macro="context/@@standard_macros/page">
> +<head>
> +  <title metal:fill-slot="title" i18n:translate="">
> +    Translation Service - Translate
> +  </title>
> +</head>
> +<body><div metal:fill-slot="body"> 
> +    <p i18n:translate="">Please provide Login Information</p>
> +    
> +    <form action="" method="post">
> +      <div class="row">
> +       <div class="label" i18n:translate="">Login</div>
> +       <div class="field">
> +        <input type="text" name="login"/>
> +       </div>
> +      </div>

Sorry for being picky but these i18n texts are ambigious.

In English, "login" can be two things:

- login as in "to log in" (verb)

- login as in user name (noun)

These are usually translated absolutely differently because they mean 
two different things. For the sake of clarity, I would suggest to always 
call the latter a login name. Also, short messages such as button labels 
(usually contain a verb or "Ok"), headings and menu items (usually one 
noun) should generally have explicit message ids like "button-login" so 
that the translator knows exactly in what context the translation is used.

(In this case the noun was used)

> +    <div class="row">
> +      <div class="label" i18n:translate="">Password</div>
> +      <div class="field">
> +        <input type="password" name="password"/>
> +      </div>
> +    </div>
> +    
> +    <div class="row">
> +      <input class="form-element" type="submit" 
> +             name="SUBMIT" value="Login" i18n:attributes="value" />

(Here the button value is the verb "login")

Philipp