"desktop-effects" is included in the statistics ("Damn Lies", right?)
but does not seem to be in the list for submitting updates
("Transifex", right?). Is there some other way to submit my updated
(one message!) Swedish version of desktop-effects?
My name is Og Maciel, born in Brazil but living in the United States
since 1991. Graduated from Pace University with a BS in Biochemistry
in 1997. Married since 2000 and father of two wonderful girls!
Been involved with Open Source, and more specifically with the
Brazilian community since 2005, thanks to incentive from Stephan
Hermann. Started as a translator for the Brazilian Team, eventually
being appointed as the administrator, and proud leader of the team
Currently I work exclusively with upstream projects, committing
Brazilian Portuguese translations to GNOME and XFCE, as well as
helping out with Openbox and KDE translations. I also maintain a
project called BillReminder <billreminder.gnulinuxbrasil.org>, where I
get to flex my programming muscles whenever I have some free time.
I look forward to working together with other translation folks and
helping out with the ever going process of translations.
Og B. Maciel
GPG Keys: D5CFC202
The following docs and branches now exist for Documentation:
about-fedora: f8, f9, master
homepage: f8, f9, master (may be deprecated)
readme: f8, f9, master
readme-burning-isos: f8, f9, master
readme-live-image: f8, f9, master
release-notes: f8, f9, master
install-guide: f8, f9, master
Sorry these took so long to complete. I can't seem to get my old level
of Fedora work done, for all the new Fedora work! :-D
Paul W. Frields
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://paul.frields.org/ - - http://pfrields.fedorapeople.org/irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
my name is Micha Pietsch from Dresden in Saxony in the East of Germany. Right now I'm in a 3-year professional training as an IT electronics technician with Deutsche Bahn. I joined Fedora Project as a translater to get into working for the project doing something I'm really good in: my mother language. I hope to be useful for other projects after getting some experience in the community. For me it's the first time working in such a huge project.
I'm using Fedora as my everyday OS and I am totally convinced of it, telling everybody about the advantages and not to be afraid of jumping into the water. I may be deep but not too cold. :-) So I gained some basic Linux skills. Aside from speaking German very well (did I mention that I wrote for our school magazine?) I'm interested web development especially coding Python and Ruby. I like practical but nice and bulletproof CSS design as well as marketing, usuability and web applications in enterprise environments.
So far, so good, I hope I can improve my skills and look forward to learn to work with a community like this!
[barney@steinbrecher]$ gpg --fingerprint 3BAF8C64
pub 1024D/D03C8691 2008-10-11
Schl.-Fingerabdruck = DFCB 7CB3 0F81 A090 B095 B22A 010E DFD0 D03C 8691
uid Micha Pietsch <micha.pietsch(a)gmx.de>
sub 2048g/3BAF8C64 2008-10-11
GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion!
I have published updated schedules based on the great gobby editing
sessions we had this week with the Documentation and Translation teams.
Note each schedule only shows the tasks for that specific team... we
can adjust this if that is confusing:
For a view of all combined tasks for all teams:
As I mentioned during the Documentation session, I hope this process
isn't too frustrating. I think it will take a few iterations to make
sure we are all using and understanding the same terminology. There is
probably still some work to be done around the 0-day tasks as someone
pointed out on the translation list.
So next I'm proposing that both Documentation and Translation meet on
gobby and if possible fedora talk (for audio conversation) next week to
work out the remaining points of difference and confusion :)
Thanks again for your patience and I hope this process is helpful.
(Finally stealing some time again to work on this!)
----- "Paul W. Frields" <stickster(a)gmail.com> wrote:
> We have several problems currently brewing with using hosted git
> of Publican-based documents with L10n's Transifex (Tx).
> 1. Publican uses multiple POT files instead of the single POT model.
> Transifex apparently does not currently handle multiple POT files
Transifex can handle multiple files well, as long as the translators submit file-by-file.
> 2. The current (obsolete but soon to be replaced) Damned Lies (DL)
> used in L10n doesn't respond well to multiple POT files either.
I think we have two options that are feasible (~1 day work) here:
1) Use publican-generated statistics pages
This involves running a script periodically generating statistics pages similar to these for each Publican project:
This option requires us to use the 'trunk' version of publican for generating statistics, as the current version does not work well with current language codes.
2) Use a single PO file for translation and let DL handle statistics.
This is slightly more work, but not rocket-science: We continue to use the ./po/ directory and have a $lang.po file for each language and a $project.pot POT file.
We then need to add perhaps 3 additional targets to the Makefile:
'potmerge' - Merges all pot files in ./pot/$doc.pot to ./po/$project.pot
'poupdate' - msgmerge's all po files in ./po/$lang.po with ./po/$project.pot
'posplit' - copies translations from ./po/$lang.po to each of ./$lang/$doc.po
My make-knowledge is very limited, but it might be possible to hook these targets in to the existing targets even, so that when the 'single po mode' flag is active in the Makefile, we run these when e.g. 'make update-pot' is run etc...?
This option does not require any additional changes in publican upstream. Obviously this is a short-term and stupid solution, as we don't want translators to have to manage massive PO files, but it just might work until we get a more intelligent translation system to handle these.
> 3. There may also be some issues in Tx about support for the ISO
> language codes used in Publican.
Jeff has been helpful and we've confirmed that Publican works with the existing language codes.
Karsten 'quaid' Wade さんは書きました:
> On Tue, 2008-10-07 at 13:01 +1000, Noriko Mizumoto wrote:
>> John Poelstra さんは書きました:
>>> I have published updated schedules based on the great gobby editing
>>> sessions we had this week with the Documentation and Translation teams.
>>> Note each schedule only shows the tasks for that specific team... we
>>> can adjust this if that is confusing:
>> I can not see any deadline date for Installation Guide in trans-tasks.
>> I am assuming that will be 24-Nov from docs-tasks.
>> Could you please clarify this?
> I think it is 27-Oct to 31-Oct for the Preview of the Installation
> Guide. Then it looks like 21-Nov or 20-Nov for the final Installation
> Guide. The Preview is a best-effort, we publish whatever is translated
> by 31-Oct.
> You are correct that those are not explicit in either schedule.
By 21-Oct, translators are quite busy for Software translation.
More time can be spent for GA than PR.
Is any chance to translate IG under Launch phase?
>> Can you also change wording for easy understanding?
>> Current: "Release Notes PO Files completed by Translation."
>> To be: "Release Notes Translation Deadline"
> +1 Sounds better.
>> Current: "Translation Deadline for fedoraproject.org"
>> To be: "fedoraproject.org (web) Translation Deadline"
>> I think the following can be change to better expression.
>> Current: "Translate xxxxx (POT to PO)"
>> To be: "Drop xxxxx PO files (POT to PO)"
> I think that task is, "Translate the strings in the POT file, making or
> updating the PO file for your language." Is that what "drop" means?
Translatable PO files are not necessarily becoming available in order,
but can be available soon as the authors finalize. Like docs team can
drop the bombs of various documents for trans team. Each language team
will schedule how to assign the resource to catch as many bombs as
possible. Red Hat used to use the word 'drop'  internally so that I
use here that is all.
As far as "Translate xxx" date is pointing the earliest PO files
available date, that is fine.
 docs team finalize certain portion of his/her document by this date
and make available to trans team.
> - Karsten
We currently display Arabic and Hebrew translations on the virtual
console in LTR mode using the glyphs in latarcyrheb-sun16. Obviously,
that's not the preferred way.
Should we leave it this way, or do the same substitution to en_US that
we do for CJK locales?