Hi,
As I found Japanese docs a bit out of date, not updated for years,
I've tried to update some of them. Unfortunately, there is no
Japanese master and Japanese users community seems to be
on the way of extinction slowly after Mr. Kikuchi has gone.
So I think there is no place except here to review them.
Are there Japanese native speakers in this list? Please review
my translation on lp:~futatuki/mailman/2.1-ja-translation,
under messages/ja.
Regards,
--
Yasuhito FUTATSUKI <futatuki(a)poem.co.jp>
Sorry for breaking the thread, I just joined the mailing list :-)
I'm a native speaker, so I thought I might shed some light.
In german there are two different kinds of pronouns that can be used.
One is formal(Sie) while the other is informal(Du) like the ancient
(you/thou) in english.
He changed the rejection reason to include:
If you however were granted the ability to post to this address, we will
gladly forward your message.
I'm unaware of any other software out there that includes both versions
of pronouns (formal/informal). If the distinction is made, it's usually
using different translations (German/formal, German/informal).
Currently the german translation uses the formal pronouns which is
perfectly fine and most software out there does this.
The proposed change that "makes it friendlier" simply adds the informal
versions.
My personal opinion is:
This just makes reading the text harder by disrupting the normal reading
experience.
I don't think the modification of the rejection reason is such a good
idea. I think it can confuse more than help.
"If your message is rejected because you are not allowed to post to the
list but you were granted the ability to post to the address" is a
contradiction.
I would not change the translations.
simon
> On 04/25/2016 08:24 PM, Klaus Puchstein wrote:
>> Hello to all,
>>
>> the***more 'friendly-sounding' translations*is, what Iwanted.
>>
>> It's good for the quality ofthe software. I think, more people will use it.
>>
>> Thanks for quick reaction.
>>
>> Klaus Puchstein
>
>
> It is not possible for me to evaluate your suggestion, as I can't
> understand the German language.
>
> Google translates
>
> Sie/Du als Absender sind/bist nicht Mitglied der Liste -- E-Mails an die
> Liste sind aber nur für Mitglieder erlaubt! Wenn Sie/Du aber
> trotzdem die Moeglichkeit bekommen hast/haben, an diese Adresse zu
> antworten, leiten wir Deine/Ihre Mail gern weiter.
>
> to English as
>
> You / you as the sender are / not are a member of the list - emails to
> the List are allowed but only for members! If you / But thou
> still the possibility you get / have to to this address
> respond, we will forward your / your email gladly.
>
> Clearly this is a bad translation, can you provide a better one.
>
> However, my concern is it seems to say something that might not be
> generally applicable to all list's desired treatment of non-member
> posts. Whatever change is made to the translation upstream is going to
> affect all German language notices for non-member posts to all lists in
> all installations and must therefore be generic and address only why the
> message was held, not what will be done about it.
>
> Also, you seem to want some change to the postheld.txt template too.
> This template
>
>> Ihre Mail an "%(listname)s" mit dem Subject/Betreff
>>
>> %(subject)s
>>
>> wird zurückgehalten, bis der Listenmoderator Ihre E-Mail genehmigt.
>>
>> Der Grund, weshalb eine Genehmigung erforderlich ist:
>>
>> %(reason)s
>>
>> Entweder wird Ihre E-Mail in Kürze freigegeben und über die Liste
>> verteilt, oder Sie erhalten eine Mitteilung über eine Ablehnung durch den
>> Moderator.
>>
>> Sie können diese E-Mail *zurückziehen*, solange sie noch nicht
>> verteilt worden ist. Wenn Sie NICHT mehr verteilt werden soll,
>> besuchen Sie den folgenden Link:
>>
>> %(confirmurl)s
>
>
> is used for the user notification of any held message regardless of
> reason. It can't contain anything that is specific to a non-member post
> because it is used for other reasons as well.
On 04/21/2016 04:47 AM, Stephen J. Turnbull wrote:
> -i18n removed, I'm not subscribed.
>
> Barry Warsaw writes:
>
> > We need a Mailman 3 translation champion, someone who understand
> > the technical and more importantly, social issues involved, and can
> > spend time and energy on helping bring a good story to fruition.
> > I'm happy to give wide latitude to the champion to help shape a
> > solution that works for us. Maybe that's you Simon?
>
> I can help somewhat, I know the technology, I have a "friend in the
> business" (a lawyer buddy who's heavily invested in legal translation
> software), I've been involved with the Mailman and Debian translation
> communitiess in the past. But right now I'm "busy as Barry", and for
> the near future GSoC is going to sop up most of my Mailman time.
I guess I could take some sort of lead on that.
I played around a little with pootle and I really like it. It's
easy to use, fast and anyone that registers can start translating.
The main question would be selfhosting vs using gnu's hosted version.
GNU is using v 2.5. 2.7.3 is the current version which changed quite a
bit. The newer version has some sort of revision support has the ability
to add comments to translations.
The biggest change is that adding new files/ updating them requires
filesystem access in 2.7.3
So I think that GNU is going to stick to 2.5 for the time being.
Selfhosting would have a couple of upsides
* Easier access to generated po files (scriptable)
* Easier upgrade of po files
* More features (v2.7.3)
pootle has a couple of features that I think are nice to have.
* Offline translation support
(they have a very nice peace of software called virtaal)
* Terminology support
(we provide recommended translations for common words)
* Used by (big) organizations
(mozilla, document foundation, ...)
* Relatively fine grained permissions
(users can get permissions based on languages as well as projects
The trend seems to be to use self hosted pootle servers, at least
mozilla and libreoffice do, there are probably more.
I don't think selfhosting would be that hard. It's based on
python+django and uses redis.
If you want I can spin up an instance on my server and provide
interested people credentials to play with. (existing demo instances
don't allow adding/managing projects)
