[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Ambassadors] LATAM Release Notes Localization



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Karsten:
Volunteering for LATAM Release notes, I think Pablo from Argentina also
will also help me.

Y.S.
> > - --
> > Nicolas A. Corrarello              p: +54 (11) 4903-4112
> > Fedora Ambassador Argentina        c: +54 (911) 5524-1326
> > Fedora Project                     e: ncorrare fedoraproject org
> > GPG Key: DFC893EE                  h:
www.fedoraproject.org/wiki/NicolasCorrarello
> > GPG Fingerprint: 5C93 42DA 98E1 4EEF B24B  7F8C E145 B2F9 DFC8 93EE
> > Import my key: $ gpg --keyserver pgp.mit.edu --recv-key 0xDFC893EE
> > Learn. Network. Experience open source.
> > Red Hat Summit San Diego  |  May 9-11, 2007
> > Learn more: http://www.redhat.com/promo/summit/2007

Karsten Wade escribió:
> > Last release we had an idea that I'm proposing we try for Fedora 7.  For
> > reasons that should be obvious as you read, the Ambassadors seem to be a
> > natural group to do this.  Perhaps in coordination/collaboration with
> > Fedora Translation/L10n contributors?
> >
> > The basic idea is to distribute to countries/regions a list of "talking
> > points".  Talking points are specific items we want to see covered in
> > any release announcement.  Then each region/language can choose to i)
> > form a small team, and ii) collaborate to write a truly localized
> > release announcement.
> >
> > http://fedoraproject.org/wiki/Docs/Drafts/ReleaseAnnouncements#Process
> >
> > Background
> > ----------
> >
> > In the past, the announcement introduction has been written in English
> > in a semi-humorous way.  To understand it, you had to know specific
> > cultural references.  This made them fairly impossible to translate (or
> > transliterate).  Or even understand, period.
> >
> > This new method would rely entirely upon the local groups to collaborate
> > on an announcement, then distribute it within their region as a formal
> > Fedora release announcement.  One place to start is fedora-announce.
> >
> > How many different language announcements can we get on fedora-announce
> > for Fedora 7?
> >
> > One concern that is that a release announcement is a very big chance to
> > start misinformation about Fedora.  For example, an announcement may be
> > written in a language not read by most of the Fedora leadership, and the
> > authors accidentally choose terms or phrasing that reflect negatively on
> > Fedora.  The quality of the writing or grammar also reflects on Fedora.
> >
> > To lower this risk, it seems like a good idea to have the release
> > announcement draft due for review by the final test (usually test3,
> > occasionally test4).  Every draft announcement then needs an independent
> > review by a reader of that language.
> >
> > I'm sure that this has been done informally in various countries.  This
> > idea is to formalize the process, recognize the people involved with the
> > honor of speaking LOUDLY for Fedora, and make an ever bigger impact with
> > this next release.
> >
> > - Karsten
> >
> >
> > ------------------------------------------------------------------------
> >
> > --
> > Fedora-ambassadors-list mailing list
> > Fedora-ambassadors-list redhat com
> > https://www.redhat.com/mailman/listinfo/fedora-ambassadors-list
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFF5YDQ4UWy+d/Ik+4RAlDPAKCW4pViaGZcnp1mEDVLgIIpOMpfIACePEAP
dLb8ffDFnNYu+aGTZGV5HfM=
=Hrc3
-----END PGP SIGNATURE-----


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]