Hello, Sarah and Jeremy!
We has discussed in June question about translation of FC3 Release
I understand Red Hat team should be very careful with this document but
end user is waiting good translation of whole product.
I suppose translation teams could provide good enough "unofficial"
translation of Release Notes.
I see some points to discuss:
- remark of "unofficial" status of translation in title
- copyright notice of original document and translation
- file format and encoding ( plain text and html in unicode UTF-8 )
Please find attached translation of Release Notes for FC3 test2 as
Russian translation team
Sarah/Bernd & Team,
I noticed that it is sometimes
frustration to lose the SSH Key, and the lack
of an automated way to update the key (Due to
format PC, bad drive, or whatever reason)
So, I want to suggest an enhancement here
to the current system (If it is doable).
Everyone of us has a PIN we use to Take/Release
modules, can we have a link to Update our SSH key
and use the same PIN to authenticate the person ?
The goal here is to make the adminstration less,
avoid the mistakes, and allow the person to update
his/her key when needed.
What do you think about that?
This is a reminder of the mailing lists for the Fedora Project, and
the purpose of each list. You can view this information at
When you're using these mailing lists, please take the time to choose
the one that is most appropriate to your post. If you don't know the
right mailing list to use for a question or discussion, please contact
me. This will help you get the best possible answer for your question,
and keep other list subscribers happy!
Mailing lists are email addresses which send email to all users
subscribed to the mailing list. Sending an email to a mailing list
reaches all users interested in discussing a specific topic and users
available to help other users with the topic.
The following mailing lists are available. To subscribe, send email to <listname>-request(a)redhat.com
(replace <listname> with the desired mailing list name such as
fedora-list) with the word subscribe in the subject.
fedora-announce-list - Announcements of changes and events. To stay
aware of news, subscribe to this list.
fedora-list - For users of releases. If you want help with a problem
installing or using , this is the list for you.
fedora-test-list - For testers of test releases. If you would like to
discuss experiences using TEST releases, this is the list for you.
fedora-devel-list - For developers, developers, developers. If you are
interested in helping create releases, this is the list for you.
fedora-docs-list - For participants of the docs project
fedora-desktop-list - For discussions about desktop issues such as user
interfaces, artwork, and usability
fedora-config-list - For discussions about the development of
fedora-tools-list - For discussions about the toolchain (gcc, gdb,
etc...) within Fedora
fedora-patches-list - For submitting patches to Fedora maintainers, and
used in line with BugWeek
fedora-legacy-announce - For announcements about the Fedora Legacy
fedora-legacy-list - For discussions about the Fedora Legacy Project
fedora-selinux-list - For discussions about the Fedora SELinux Project
fedora-marketing-list - For discussions about marketing and expanding
the Fedora user base
fedora-de-list - For discussions about Fedora in the German language
fedora-es-list - For discussions about Fedora in the Spanish language
fedora-ja-list - For discussions about Fedora in the Japanese language
fedora-i18n-list - For discussions about the internationalization of
fedora-trans-list - For discussions about translating the software and
documentation associated with the Fedora Project
Brazilian Portuguese: fedora-trans-pt_br
Simplified Chinese: fedora-trans-zh_cn
Traditional Chinese: fedora-trans-zh_tw
I would like to announce that we reached 100% Arabic Translated
We still will go through a tough time unifying and tuning the
translation. Yet, the state on it right now is good enough. I would like
to thank the fedora team, and the arabic fedora arabic translation team.
I was facing a strange problem in the past 3 days that denied my access to
Fedora server. It was so weird that I suspect something related to my
connection not Fedora repository. I mentioning it here for the record and for
others who may face such a problem in the future.
I can checkout out a file, update a file but not a whole folder or module!
[munzir@localhost translate]$ ssh -vvv i18n(a)redhat.com
OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to redhat.com [126.96.36.199] port 22.
debug1: connect to address 188.8.131.52 port 22: Connection timed out
ssh: connect to host redhat.com port 22: Connection timed out
#ifconfig ppp0 mtu 576
This is an mtu (maximum transmission unit) problem. It defines the maximum
size of a packet that can be transferred in one frame over a network. mtu is
hard coded to a default of 1500 in my Fedora Core 3 system which is suitable
for fast connections like DSL but not dialups.
Now! is this a solvable bug? Where do I need to report it? Should ordinary
users know this weird setting?
Munzir Taha PGP Key available
gpg --recv-keys --keyserver www.mandrakesecure.net F0671821
Telecommunications and Electronics Engineer
Mandrake Club Member
Maintainer of the Open Arabic Bugs Project at
Maintainer of Fedora Arabic Translation Project
CIW Designer, ICDL, MOUS, Linux+, LPI 101
New Horizons CLC, Riyadh, SA
After going through alot of ssh key pair forums, faqs, tests, I have
come to the conclusion that the first steps I took in creating the
keys were wrong, resulting in a un-successful connection to the cvs.
I am attaching my public key on this email, and kindly requesting you
to reconfigure my account's setup with the attached key.
My login is "achillee"
Some of you may have observed that the number of entries of each locale
are quite different. The reason is that po files in some locales and/or
modules are not kept up to date with the corresponding pot file. To
ensure po files stay up2date, it is a good idea to run the following
command before you start working on a file and before you commit the
msgmerge po-file pot-file > tmp-file (this is to merge with the latest
mv tmp-file po-file
msgfmt -cvo /dev/null po-file (this is view translation stat as well as
to do basic format check)
If you are the coordinator for the entire locale, and want to do this
regularly for all modules in this locale, you can use the attached
simple script to do so:
1) put the script into a directory in your command path
2) chmod 755
3) be aware of potential file conflicts