Guido Caruso: Sponsor found (but CVS says...)
by g.caruso@fedoraserver.org
Hi.
My cvsdocs membership has been approved.
When I try to get the module from the server I get these messages:
[guido xe3 ~]$ export CVS_RSH=ssh
[guido xe3 ~]$ export
CVSROOT=:ext:gcaruso i18n redhat com:/usr/local/CVS
[guido xe3 ~]$ cvs -z9 co translate/
Connection closed by 66.187.233.241
cvs [checkout aborted]: end of file from server (consult above messages
if any)
Why? I cannot work in this way!!
Guido.-
17 years, 6 months
[Fwd: [Fedora-marketing-list] idea on explaining the mp3 question]
by Dimitris Glezos
Sam's following mail gave me an idea: Provide the user with Fedora "tips
of the day" somewhere in the browser splash page (of course nothing
splashy or popup).
Post FC6 we can talk about how we can enhance the browser splash page,
among other doc things.
-dim
-------- Forwarded message --------
From: Sam Folk-Williams <samfw(a)redhat.com>
To: Discussions on expanding the Fedora user base
<fedora-marketing-list(a)redhat.com>
Subject: [Fedora-marketing-list] idea on explaining the mp3 question
Date: Mon, 02 Oct 2006 12:41:16 -0400
Hi,
I know this is an overly-discussed issue, but since I get so many
questions on it I wanted to run this idea past everyone.
A common complaint I hear is that people think Fedora is "broken" when
it doesn't play MP3s. This leads to mailing list and forum traffic,
negative word-of-mouth exposure, and needless confusion.
I think the problem is that when you try to play an MP3 file... nothing
happens at all or you get an ugly codec message -- both of these indeed
seem to indicate something is broken. Why not have a pop up that
explains why Fedora doesn't play MP3s and give a link to the wiki where
it is explained in further detail?
I could file an RFE on this.... I think it would cut down on the
confusion. Has this been previously discussed? Thoughts?
Sam
--
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, 6 months
Re: release-notes/devel/po sv.po,1.4,1.5
by Paul W. Frields
On Sun, 2006-10-01 at 21:54 -0700, Magnus wrote:
> Author: raada
>
> Update of /cvs/docs/release-notes/devel/po
> In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12406
>
> Modified Files:
> sv.po
> Log Message:
The Swedish translation is completely finished! Thanks, Magnus, and
great job! I noticed that this was checked in directly to Docs CVS, and
that may happen for some translations, rather than (or in addition to)
using i18n.redhat.com. (We are happy either way, of course!) For any
non-translators interested in checking the progress on translations, you
can run this command:
$ msgfmt --stat -o /dev/null <PO_file>
The output looks like this for a finished translation:
795 translated messages.
<pedantic audience="newcomers">
Obviously it's important that we don't overwrite a finished
translation with an unfinished one, so it's wise to keep an eye on the
fedora-docs-commits list to see these as they come in. In case of a
problem, we can always revert the CVS copy if needed.
Bob, our intrepid editor-in-chief, said the other day that if we got
just one extra translation it will be worth the delay. So I guess now
everything else is gravy!
</pedantic>
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Project Board: http://fedoraproject.org/wiki/Board
Fedora Docs Project: http://fedoraproject.org/wiki/DocsProject
17 years, 6 months
Problem in f.r.c/docs/fedora-install-guide-en/fc5
by Patrick W. Barnes
I'm not sure if someone has been doing work on the Docs infrastructure, but
something is a little broken. Pages of the Installation Guide for FC5 are
damaged. They are being rendered with an HTML header instead of using the
PHP include. This causes breakage when PHP functions are called for the
footer of the pages.
An example of the error output:
PHP Fatal error: Call to a member function on a non-object
in /scratch/fedorascratch/LIVE-2006-09-30-20.45/tmp/html/docs/fedora-install-guide-en/fc5/ch-rootpassword.php
on line 50
PHP Fatal error: Call to a member function on a non-object
in /scratch/fedorascratch/LIVE-2006-09-30-20.45/tmp/html/docs/fedora-install-guide-en/fc5/ch-timezone.php
on line 25
PHP Fatal error: Call to a member function on a non-object
in /scratch/fedorascratch/LIVE-2006-09-30-20.45/tmp/html/docs/fedora-install-guide-en/fc5/sn-utc.php
on line 22
Tickets are being automatically created in the Fedora Ticket System every
half-hour. Whomever is working on the Docs infrastructure or the
Installation Guide should check on this. If you need a hand, ping me
off-list.
--
Patrick "The N-Man" Barnes
nman64(a)n-man.com
http://www.n-man.com/
LinkedIn:
http://www.linkedin.com/in/nman64
Have I been helpful? Rate my assistance!
http://rate.affero.net/nman64/
--
17 years, 6 months
fedora-install-guide
by g.caruso@fedoraserver.org
Hi at all.
I am translating fedora-install-guide into italian language. What's
about its FC6 version?
Thanks in advance.
Guido Caruso
17 years, 6 months
Guido Caruso: Sponsor founded
by g.caruso@fedoraserver.org
>Email back to this list when you have a sponsor and we can quickly
>approve your cvsdocs membership.
Hi! I have my sponsor:
Francesco Tombolini <tombo adamantio net>
Guido.-
17 years, 6 months
Re: UPDATE: More translation time!
by Nikos Charonitakis
thanks for extra time.
Now we can do QA and complete Greek Release-notes.
we will use it for sure.
For Greek team
Nikos Charonitakis
On 10/2/06, Paul W. Frields <stickster(a)gmail.com> wrote:
> Hello Translators,
>
> [ You're receiving this email personally because your
> email address was pulled from one of our PO files for
> the Fedora Core Release Notes. A copy is sent to
> fedora-trans-list as well. ]
>
> We understand that we piled a LOT of work on you guys for the FC6
> Release Notes, with not very much time to do it. And we feel bad about
> it. This was entirely due to process problems, and had *nothing* to do
> with the great work you continue to do on a regular basis. A lot of the
> material entering the release notes came in on the wiki in the last week
> or two, meaning not only did we get the POT out late, but it was full of
> new strings in a lot of cases.
>
> I'd like to specially recognize Francesco Tombolini, working on the
> Italian translation. Francesco actually finished his entire PO file
> somehow, despite all the obstacles, so I wanted to single him out for
> some special praise!
>
> But we certainly can't expect everyone to get so much work done in such
> a small time. That's why we've secured MORE TIME for the release notes
> translation. We have a new deadline for PO delivery of:
>
> * * * 1200 UTC, Thu Oct 05 2006 * * *
>
> That's another ~3.5 days! In other words, we're trying to give you back
> just about every bit of time we cut by being late. You can continue to
> work on the existing POT in i18n.redhat.com/release-notes. We have
> changed nothing since it was delivered last week.
>
> WHAT WE COULD USE FROM YOU:
>
> (Other than the translation, of course!) Just a quick reply to this
> message. Let us know if you think you can finish the remaining work in
> that time. If you don't think this is a good idea, you don't have to do
> anything extra. But if you want some extra time, and will use it,
> please let us know as soon as you can!
>
> We will be discussing an improved plan for the FC7 cycle. Please join
> us on fedora-docs-list(a)redhat.com and put in your ideas if possible.
>
>
> cc: Core team, FDP
>
> --
> Paul W. Frields, RHCE http://paul.frields.org/
> gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
> Fedora Project Board: http://fedoraproject.org/wiki/Board
> Fedora Docs Project: http://fedoraproject.org/wiki/DocsProject
>
>
>
17 years, 6 months
Re: Release notes translation -- what's up?
by Paul W. Frields
On Thu, 2006-09-28 at 21:52 +0200, Thomas Canniot wrote:
> Le mercredi 27 septembre 2006 à 22:15 -0400, Paul W. Frields a écrit :
> > On Thu, 2006-09-28 at 01:49 +0100, Dimitris Glezos wrote:
> > > We are less than 3 days before the translation freeze and the POT file for the
> > > relnotes hasn't landed yet on i18n?
> > >
> > > Can we get some information about what's going on?
> >
> > The Docs Project folks have reached out for a number of Translation
> > people, but with no luck --
> >
> > -- UNTIL: Aman got back and checked in with us tonight. See his earlier
> > message; the new POT is available which translators should merge and
> > work on as soon as possible. We apologize for the short notice. We
> > were about a day late or so with our output, which didn't help. Rest
> > assured this is not the end of this particular story, and we are going
> > to step up our efforts to jump-start improvement of this process.
>
>
> Thanks, but ... when I look at all the modifications that have been made
> for the last relnotes issue, I really feel disappointed. I thought that
> keeping complete and up to date translations of all the relnotes issues
> during summer would avoid having so much strings to translate for the
> latest issue. I was wrong.
>
> It seems that beat writers were not keen on writing before fc6 final
> release, then I should suggest that translators may need much more of a
> week to translate the final relnotes issue. Moreover, more time could
> avoid the panic/confusion that we saw this week.
I couldn't agree more, Thomas. The blame falls on a lot of different
factors:
1. The wiki makes it easier for people to put up release notes, but it
also makes them easier to change. A lot of these changes are minor or
cosmetic, but they still result in untranslated strings. I watched the
wiki all summer, and edited it constantly to make sure that the language
was clear and easier to translate. But the result is that translators
are not necessarily saving themselves work by translating early and
often. And yes, too many beat writers are waiting until the last
minute.
2. When we edited the test3 version of the release notes, we used our
new wiki conversion engine, and then the editors (including primarily
me) retagged things into proper DocBook. When we got the new POT ready
for final, we realized that we were going to have to retag everything
the same way to avoid creating brand-new untranslated strings. As I
understand the issue, msgmerge thinks these are completely different
strings:
"Use the command <code>msgmerge -U</code>."
"Use the command <command>msgmerge -U</code>."
Or at least they're "fuzzy." Which means the numbers *look* inflated.
Maybe there's less work than it looks like, but a string is still a
string, and someone has to look at it.
3. No one from the Translation Project management responded to our
email for some time to move the POT. We were very lucky that Aman
stopped by IRC -- I think he's still on vacation, no less -- and helped
us out.
4. Our normal editorial staff had some unplanned downtime as a result
of "real-life" issues. Sometimes these things happen, it's just life.
But on top of that, we have *VERY* few people actively helping on Docs
Project. In fact, you can probably count them on two hands.
> I couldn't check my mail as much as I usually do this week. I got an
> internet connection on Monday, but did not took the POT file as it was
> not really up to date as it should. Now that I can, I am before a
> 393-strings-that-need-overreading document. I am VERY sad to tell that I
> won't be able to translate that much of strings in so a little time :'(
>
> French relnotes won't be on the DVD, oh sh*t :(
I am very disappointed at the way this process went, but I feel that in
a lot of ways, we really did do our best given the circumstances.
However, that doesn't mean we can't improve. I would like to propose
the following -- and I'm just brainstorming here:
1. No release notes translations to be done until test3, to minimize
wasted effort from translators. *A LOT* changes from test1 until final,
but not nearly as much from test3 until final.
2. Set the new deadline for translation *10 days* before the target
date instead of 7. This gives us wiggle room, so at worst, if we're a
day or two late, there's still more than a week to translate.
3. A sort of Docs/Translation "summit" meeting on IRC to work out a
more rigorous scheduling routine, to avoid unnecessary delays.
Your comments and thoughts are appreciated. I am setting the follow-up
to fedora-trans-list. Any interested Docs people should be subscribed
here as well.
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Project Board: http://fedoraproject.org/wiki/Board
Fedora Docs Project: http://fedoraproject.org/wiki/DocsProject
17 years, 6 months