Language team list
by Dimitris Glezos
Hi all.
In our effort to organize L10N, we'd like to have somewhere listed the current
active language teams. These are languages that have a team with some kind of
structure and communication channel.
I have compiled a table with some info on:
http://fedoraproject.org/wiki/L10N/Teams#teams
Please fill in your language and at least a maintainer/coordinator for it.
In the next few days we'll be testing with the Documentation Project the process
of doing translations on `cvs.fedoraproject.org`. Stay tuned.
-d
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
17 years, 2 months
[Fwd: Translations: String freezes, CVS converging, Packaging]
by Dimitris Glezos
Forwarding the email sent to -devel-list.
-------- Αρχικό Μήνυμα --------
Θέμα: Translations: String freezes, CVS converging, Packaging
Ημερομηνία: Tue, 06 Mar 2007 22:02:24 +0000
Από: Dimitris Glezos <dimitris(a)glezos.com>
Απάντηση: Development discussions related to Fedora Core
<fedora-devel-list(a)redhat.com>
Προς: Development discussions related to Fedora Core <fedora-devel-list(a)redhat.com>
Hi all.
The L10n project has been discussing for a while now (also at FOSDEM with
mspevack) about ways to improve our translation processes. We estimate that more
than 1 out of 3 users uses a non-English desktop.
First of all, let's clarify here that for the time being, we are referring only
to applications that Fedora is upstream (anaconda, system-config-*, and
basically most of the non-deprecated stuff that appears on [1]).
[1]:http://i18n.redhat.com/cgi-bin/i18n-status?page=status&locale=es&branc...
The plan in mind includes three actions.
## String freezes
For F7, the RelEng team has introduced string freezes in the schedule [2]. This
means that application strings for F7 should be complete *by 19/3*. Translations
made after this date (and before the freeze) should be guaranteed to be included
in the release.
[2]: http://fedoraproject.org/wiki/Core/Schedule
To do this we need to try not to add new strings after the freeze and let the
L10n folks know if they need to do so. Also, maintainers should repackage before
each release (and after the translation freeze) without a bug needing to be
opened.
## CVS convergence
Right now translations are done on `i18n.redhat.com`. This requires contributors
to have one account on the Fedora Account System (FAS) and a different
one for translations. With the merge of Core and Extras, now is a good
point to get rid of this distinction.
The plan is to move all PO files on Fedora infrastructure under a new
CVS group (cvsl10n) [3]. An email will be sent to all translators to create a
FAS account if they don't have one and join the cvs group. Members of the L10n
team and ambassadors will help with this process.
[3]: http://fedoraproject.org/wiki/L10N/Projects/CVSInfrastructure
At this point we could discuss the idea for Fedora to act as upstream for
the translations of outside-hosted projects such as yum, smolt, and
pungi. The proposal is to host and maintain those project's
translations with the existing Fedora L10n community.
## Packaging translations
One final plan (and probably the one that needs most discussion) is about
changing the way we package translations. Right now PO files live inside the
application and are packaged there (GNOME-style). The plan is to move the PO
files in to their own directory and distinct package [4] (KDE-style langpacks).
[4]: http://fedoraproject.org/wiki/L10N/Projects/TranslationsPackage
Cons: L10n team should maintain a package (or many) and packages should be
altered to accomodate the different locations of PO files.
Pros (many): increased modularity and maintenance (L10n repackages at
will). App packages will be smaller in size -- we could provide
one langpack or different ones per language.
Comments, suggestions?
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
17 years, 2 months
usermode - linenumber diff
by Renato Pavičić
Hi,
Not sure how to create bug report on this one, if it's needed at all.
usermode.pot (currently) has 98 lines. My lang PO has 97. After being
updated (one fuzzy line appeared within last 24 hours from my last check).
Anyway, I've checked other PO files, and it appears that some PO's jahve
98, while others have 97 lines.
Wjhat kind of a problem should I report (and where?)
--
Best regards,
Renato Pavicic
mailto:repavici@globalnet.hr
also mailto:renato@translator-shop.org
homepage: www.translator-shop.org
Official Opera translator for Croatian language since April 2006
17 years, 2 months
Reminders like "anaconda/ca to be released"
by Josep Puigdemont
Hi,
For modules I've taken for translation, I will receive a reminder every
4 hours about the module being released if I don't commit my changes.
These are the times and dates for the last 5 reminders I've received
today:
Mon, 12 Mar 2007 16:40:21 -0400 (21:40 CET)
Mon, 12 Mar 2007 12:40:22 -0400 (17:40 CET)
Mon, 12 Mar 2007 08:40:22 -0400 (13:40 CET)
Mon, 12 Mar 2007 04:40:11 -0400 (09:40 CET)
Mon, 12 Mar 2007 00:40:11 -0400 (05:40 CET)
Could someone update the cron job so these messages are not sent that
often?
I'd propose to send a maximum of on reminder a day during string freeze
periods, and one reminder a week otherwise (or something you think is
reasonable).
Thanks a lot!
/Josep
17 years, 2 months
moving all .po files to UTF-8
by Bill Nottingham
A recent thread on the fedora development list discussed the benefits
of having the translations in UTF-8 by default:
https://www.redhat.com/archives/fedora-devel-list/2007-March/msg00056.html
Rather than doing it at build time, for all the software that's translated
in/by Fedora, it seems simplest to do it in the .po files itself. Therefore,
at some point in the next few days, we intend to do this in the CVS
repository.
Does anyone forsee any issues with this?
(This would only involve changing roughly 36 of the 3900+ .po files in
the translate repository.)
Bill
17 years, 2 months
Google Summer of Code 2007 - Πόστερ
by Simos Xenitellis
Καλησπέρα,
To Google Summer of Code είναι ένας ετήσιος διαγωνισμός για
φοιτητές/σπουδαστές της τριτοβάθμιας εκπαίδευσης με αντικείμενο την
πληροφορική και το ελεύθερο λογισμικό.
Αρκετά έργα ελεύθερου λογισμικού λαμβάνουν μέρος στο διαγωνισμό
στέλνοντας προτάσεις για έργα που μπορούν να αναληθφούν.
Δείτε
http://code.google.com/soc/
Ένα από τα έργα αυτά είναι το GNOME - http://www.gnome.org/ - το γραφικό
περιβάλλον επιφάνειας εργασίας που είναι διαθέσιμο στις διανομές Ubuntu
Linux, Fedora Core (και αλλού), και έχει φτιάξει μια αφίσα που μπορείτε
να αναρτήσετε στο εκπαιδευτικό σας ίδρυμα.
Η αφίσα αυτή έχει μεταφραστεί και στα ελληνικά. Δείτε
http://live.gnome.org/SummerOfCode2007/Poster
Μπορείτε να πάρετε την αφίσα και να την τροποποιήσετε για άλλο έργο
ελεύθερου λογισμικού, όπως για παράδειγμα το έργο One Laptop Per Child
(OLPC), Ubuntu Linux και Fedora Linux.
Φιλικά,
Σίμος
17 years, 2 months
Improving the currency of anaconda's pot file
by Jeremy Katz
Since we're really bad at manually updating anaconda's pot file, I'd
like to move to it happening more regularly. But to do so in a way
that's reasonable time-wise, we'll need to stop doing the automatic
msgmerge of po files for anaconda. Given that many of the modules on
i18n.redhat.com aren't automatically msgmerge'd, I don't think this
should be a big problem, but wanted to check for feedback before just
making the change.
So thoughts?
Jeremy
17 years, 2 months
