Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Accessibilty Guide translation request
https://bugzilla.redhat.com/show_bug.cgi?id=518348
Summary: Accessibilty Guide translation request
Product: Fedora Localization
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: l10n-requests
AssignedTo: dimitris(a)glezos.com
ReportedBy: eric(a)christensenplace.us
QAContact: aalam(a)redhat.com
CC: piotrdrag(a)gmail.com, couf(a)skynet.be,
diegobz(a)gmail.com, fedora-trans-list(a)redhat.com
Classification: Fedora
Accessibility Guide
This guide describes how to find and use accessibility features in Fedora.
https://fedorahosted.org/accessibility-guidesvn+ssh://svn.fedorahosted.org/svn/accessibility-guide/pot/
File filter (eg. <code>po/.*</code>)
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Hello,
Thought I'd check here first before actually filing the bug. There seems to be a
problem with the translations available for policycoreutils-gui
(system-config-selinux interface) in Fedora 11. A few parts still show up in
English. The example for bn_IN is here:
http://runab.fedorapeople.org/assorted-bugs/F11-policycoreutils.png
A quick msgunfmt on the policycoreutils.mo files under
/usr/share/locale/<lang-code>/LC_MESSAGES/ gives me widely varied translation
status for a lot of languages with 100% completion[1].
Kannada (3 Translated)
Assamese (503 Translated)
Bengali India (651 Translated)
Version checked: policycoreutils-gui-2.0.62-12.12.fc11.i586
Is there any bug for this or any reference to this issue?
Thanks
Runa
[1] https://translate.fedoraproject.org/projects/policycoreutils/HEAD/
--
blog: http://runab.livejournal.com
irc:
mishti or runa_b on Freenode, Gimpnet, Mozilla, LinuxChix
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Update Transifex instance to version 0.7 or greater
https://bugzilla.redhat.com/show_bug.cgi?id=527327
Summary: Update Transifex instance to version 0.7 or greater
Product: Fedora Localization
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: l10n-requests
AssignedTo: dimitris(a)glezos.com
ReportedBy: rlandman(a)redhat.com
QAContact: aalam(a)redhat.com
CC: piotrdrag(a)gmail.com, couf(a)skynet.be,
diegobz(a)gmail.com, fedora-trans-list(a)redhat.com
Classification: Fedora
Target Release: ---
Description of problem:
Fedora's current Transifex instance is version 0.5.2. This version lacks a
number of features available in later versions of Transifex that are very
important for the Fedora Documentation Project. Specifically, these include the
ability to handle more than one PO file per language per component and the
ability to recognise the BCP 47 language codes that are part of the XML
specification.
An infrastructure ticket is already open:
https://fedorahosted.org/fedora-infrastructure/ticket/1455
but some bugs in Bugzilla now depend on this upgrade, so I'm filing this bug as
a blocker.
Version-Release number of selected component (if applicable):
0.5.2
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Hello,
I am getting a 'Page Unavailable' error while trying to download or submit the
.po files for the Installation Guide. At times, a 'Gateway Timeout' error also
shows up. I thought I'd check here first before filing a ticket, if there is any
outage ongoing for translate.fedoraproject.org.
The page I am looking at is this:
https://translate.fedoraproject.org/projects/docs-install-guide/f12-tx/
Thanks
Runa
--
blog: http://arrbee.wordpress.com
irc:
mishti or runa_b on Freenode, Gimpnet, Mozilla, LinuxChix
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I just got off of a phone conference with other Fedorians where we
discussed the Documentation schedule for F13. Wish I could say it's
ready for public consumption right now but it is still pretty ugly. I'm
sure that John (poelcat) will have it out in a few days.
We worked with Noriko on the translator schedule as well. One of the
bigger changes that will be happening is that we have eliminated the
freezes associated with Alpha and Beta. It will be a continuous work in
progress. This has the benefit of allowing the translators to have time
to translate the Release Notes as they are being developed and not
having hundreds (thousands?) of lines of text made available to them
with a short period of time to work. The same will be done for the
Guides as well. F13 guide development started the day F12 was released
so the new POT files should be made available to the translators now
(pending the Transifex 0.7 upgrade).
I hope this makes for a smoother process for this release. We will
continue to tweak the process along the way as well.
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJLMZOLAAoJEDbiLlqcYamxF+4P/2C4LPE9bUGurzDKPUbEnmRb
+ARwIB4rpCt7N00PdQkiP4h2xYLAoBXfD7t3CjinmzllVdHga5cdkGMjcZLpmv/v
UOBZs1vjwb3mZBb9oUFXwEAZW2rbPomW8rBNkthBS8TXxgvuphjZM4ysnE/uHtDy
q6Wp/hzNYj1pyj2+edIZ5UO8KsYx9K8IvEEoheyj6m7Amm2PLj4YOw5+EPAYOo+/
IL7kBTDkBheXHv+T5BgR9bVlmUeq74V8QxUy543/olQsLSGm7Oc6TfUYYhRPOfQL
QDtcR9E+pTG2RSKi99VHQZ5dmKfJLrhz0GDwbpnmyGCXCG4yOSFlj6ULOvnT8+P8
Uxe2Rh/b1ZDdVQkIiyL6WoCmYqQAKBEw/Mwr7RLAqhsBBS66o0jcS2CpWHkSlu3o
32D6CG7a3HLQR2SfXWIbg+Tu/5B585f8wH8M49zSFwkUgcH9XWCbowk4WYuFpEf9
W+YJ3mXEiSoGyGTicsS9bPhGvoLXCjvsxxja7i21QhV9cVjgQJLdbNHHXhcr5ujp
aIt0gRiiNDLxrnfY9WgyAMwBUQ+7TUoGLCgOPtfaXtsau1vFwBjJ3lresrrHNMBV
YDdmVlmDc+9IQXnfYF40VSLg4Q6oOYdoRjxA2qmR2heVPMSOUqrsJz3fOQmW6S8G
rK8VYa3//cpG6OUcvp30
=0Z7p
-----END PGP SIGNATURE-----
-------- Original Message --------
Subject: [ANNOUNCEMENT] Red Hat Bugzilla 3.4 RC
Date: Tue, 22 Dec 2009 16:19:30 -0500
From: James Laska <jlaska(a)redhat.com>
Reply-To: Fedora Infrastructure <fedora-infrastructure-list(a)redhat.com>
To: fedora-announce-list(a)redhat.com, fedora-devel-announce(a)redhat.com,
fedora-test-list(a)redhat.com, fedora-infrastructure-list(a)redhat.com
CC: fedora-devel-list(a)redhat.com
I am sending this on behalf of Dave Lawrence and the bugzilla team at
Red Hat. Please forward this on to any appropriate lists that were
missed.
========
FINAL CHANGEOVER DATE: Friday, January 8th, 2010 6:00pm EST (23:00:00
UTC)
Mark your calendars! We are expecting the migration to take no more than
6 hours.
Please let us know at bugzilla-owner(a)redhat.com if this date is in
conflict with any release schedules, etc.
Greetings,
The Red Hat Bugzilla team is happy to announce the release candidate of
the next version of Red Hat Bugzilla based on the upstream
3.4 code base.
So far there has been little to no feedback on our betas so please use
this last opportunity to test drive at:
https://partner-bugzilla.redhat.com
Over the years Red Hat has made substantial customizations to Bugzilla
to fit into the Engineering tool chain. Over time the
upstream has incorporated some of these customizations or solved them in
different ways. Upgrading reduces our customization
footprint (and thus maintenance) while bringing many bug fixes &
enhancements.
The main area of focus for our public betas are stability. Functionality
that currently works in our 3.2 code base should continue
to work as expected in the new 3.4 release. These include various ajax
optimizations, needinfo actor support, frontpage.cgi, product
browser, several various UI enhancements, and of course the XMLRPC API.
Please feel free to point your various scripts and third party
applications that use the XMLRPC API at the test server to make sure
they continue to function properly.
There are numerous other changes behind the scenes that we haven't
listed. The goal is to make sure that functionality that people
have come to expect in 3.2 is possible in the new system.
There are also numerous new features/fixes that are part of the upstream
3.4 release. For more detailed information on what has
changed since the last release, check out release notes here:
https://partner-bugzilla.redhat.com/page.cgi?id=release-notes.html
The database is a recent snapshot of the live database so should be
useful for testing to make sure the information is displayed
properly and changeable. Also with a full snapshot it is possible to
test for any performance related issues. Email has been
disabled so that unnecessary spam is not sent out. So feel free to make
changes to bugs to verify proper working order.
We are asking for everyone to get involved as much as possible with
testing and feedback on the beta releases to help us make this
the most robust and stable release possible.
Please file any enhancement requests or bug reports in our current
Bugzilla system go here:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&version=3.4
To see current list of 3.4 related bugs as well as blockers for release,
go here:
https://bugzilla.redhat.com/buglist.cgi?product=Bugzilla&version=3.4
Thanks The Red Hat Bugzilla Team
_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Hi, (sorry if it's not the correct mailing list)
i'm trying to send a translation file to:
https://translate.fedoraproject.org/projects/switchdesk/HEAD/
And I get the following message:
"Sorry, an error is causing troubles to send your file."
Thanks.
Iñigo Varela
In anticipation of the meeting suggested by Sparks on logistics list,
I've created a text version of the schedule that should work well for
customizing or using in gobby.
http://poelstra.fedorapeople.org/schedules/f-13-draft/f-13-docs-trans-sched…
This version is a combination of:
1) key milestones for the release as a whole (to provide context)
2) Documentation tasks
3) Translation tasks
The most helpful feedback you can give me (at the meeting or elsewhere)
is to provide corrections, additions, or deletions based on the version
I've created. It does not help me if you create your own version from
scratch and refer to it because then I have to start all over which is a
big investment of time. A patch or diff against the original file works
too.
Thanks,
John