Re: help posting relnotes to Web
by Paul W. Frields
On Mon, 2006-01-16 at 08:41 -0800, Karsten Wade wrote:
> If anyone has a few minutes, can you help me by posting the latest
> release-notes from CVS to the Web?
>
> You can follow the pages from http://fedora.redhat.com/docs/release-
> notes with new links for FC5 test2. test1 can be left in the table
> below and test2 highlighted.
>
> The Tip box has two kind of links:
>
> * The first is to the absolute latest in CVS HEAD.
>
> * The second to what is tagged FC-5-TEST2-TRANS-FREEZE.
>
> There may be more languages available in HEAD, please test by
> uncommenting in the Makefile and running test builds, along with what
> you know from fedora-docs-commits.
>
> I will check back in a few hours and see if help is needed.
Karsten,
Sorry I missed this email in the morning -- I was working from another
system and didn't check email at the time. I wasn't sure what the deal
was with dealing with non-HEAD builds, so I couldn't handle that part.
What I *did* do:
1. Using the "${FDPBIN}/db2rpm-info" script, I created a skeleton
"rpm-info.xml" file. This file is now *REQUIRED* to do builds. I think
Tommy and/or I noted this in on-list posts, but it probably could stand
more emphasis. Assuming your document parent file is called
"mydoc-en.xml", just run:
$ cd ~/fedora/docs/mydoc/
$ ../docs-common/bin/db2rpm-info mydoc-en.xml > rpm-info.xml
(Only do this when you first create rpm-info.xml, obviously.)
2. I copied the translated titles for the relnotes into the
"rpm-info.xml" file. (The desc element for each lang still needs
translation; the lang="en" version is filled in for reference by
translators.)
3. I did a normal build and publish routine for HEAD, installing into
the docs/relnotes/fc5/test2-latest-${LANG} directories.
4. I added docs/relnotes/fc5/test2-${LANG} directories into which the
frozen tag versions can be installed, but again, I wasn't confident
about doing this right, so I figured the HEAD was more important to get
out there.
I should note that I started work on DocGuide v2 this weekend, which
will include this information of course, but I encourage everyone to get
active and ask questions on the fedora-docs-list if they are having
problems building anything or understanding what's changing. I'm
copying the f-trans-l in case I miss any of our wonderful and helpful
translators who are doing such an AMAZING job getting this content
ready. Seriously, you guys rock.
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Documentation Project: http://fedora.redhat.com/projects/docs/
18 years, 3 months
New Fedora Translation Project Maintainers
by Sarah Wang
Hi everyone,
I'm very pleased to announce that we now have a couple of new
maintainers for the Fedora Translation Project:
Amanpreet Singh Alam <aalam(a)redhat.com>
Chester Cheng <ccheng(a)redhat.com>
>From now on, they will assume the responsibility of coordinating the
Fedora Translation efforts and lead this project to the next level.
Chester has authored the translation guide for Windows users. Aman has
built the Punjabi translation team that integrated some major Open
Source projects such as Gnome, KDE, and Open Office into Fedora
translation. They both have been enthusiastic contributors and
coordinators for this project over the years. So good that I have no
reservations in turning over the leadership role to them. I view this
change as a very positive one. It will no doubt bring fresh perspectives
to the Fedora Translation Project, and increase the response time to
your queries and concerns.
I would like to thank everyone for the patience and support you have
given me over the years. I hope you would extend the same support to our
new Project maintainers and continue contributing to the overall success
of Fedora.
Sarah
18 years, 3 months
Re: Serbian translation script addition request
by Miloš Komarčević
On 12/23/05, ะะณะพั ะะธะปะตัะธั <grejigl-gnomeprevod(a)yahoo.ca> wrote:
> And two further clarify, there will be two locale's, sr and sr@Latn.
>
> Regards,
> Igor
>
> Sarah Wang <sarahs(a)redhat.com> wrote:
> Just to clarify, do you mean to add "sr" locale (sr.po) to all fedora
> packages?
Dear Sarah,
we already have translated sr.po files for all the packages and they
are tied to the "Serbian" language on the status page (some are not
being built and shipped though, but that's already in bugzilla). So
that's all perfectly fine.
As Igor said, we need another set of sr(a)Latn.po files created for all
the packages and the current Serbian translators added to their ACL
as we need to support both scripts concurrently. Not sure if we need a
separate status page for these since they're always generated by a
script and will hopefully always have identical status. Can the CVS be
set up so that when a translator "takes" a module on the "Serbian"
page both of these locales get locked? If, on the other hand, you find
it necessary to create another language page, you can label it
"Serbian (Latin)" in the list. (I don't know how GNOME handles this,
but I couldn't see two separate "languages" on their status page,
while they support both locales; maybe you can check how they did it
in their CVS?)
I hope that clears things a bit, please feel free to ask us more
questions until we get this is completely clarified.
Thanks a lot for your help and time,
Milos
18 years, 3 months
release notes files refactoring
by Karsten Wade
In order to make it easier to move content to and from the Wiki, I have
reworked the release-notes module to match filenames 1:1 with Wiki beat
names.
Below are my notes from refactoring-notes.txt in CVS. Translators need
to follow the directions to get the new files and carry over previous
translations. One reasons to do this conversion is to allow us to use
xmldiff (in cvs.fedora:/cvs/docs/docs-common/bin) more effectively. You
can use this tool to check the differences of the content between the
XML tags, which should be more useful than line-based diff for detecting
content changes.
There will be a one-time PITA for the translators, but following this it
should be *much easier* for translation (due to using xmldiff.)
Note that the DocBook parent XML and sub-XML files do *not* follow the
same layout of content as the pages at
http://fedoraproject.org/wiki/Docs/Beats . This is because the
gathering of information and the display of information are two separate
needs. The Docs/Beats pages are laid out to support writers focused on
specific content. The release notes are laid out for readers.
I would like to rework the layout of the release notes themselves for
test3. This refactoring of files is a step in that direction.
## begin refactoring-notes.txt
Questions? Email to fedora-docs-list(a)redhat.com.
0. Make a back-up of the *-en.xml files, if you need them for
reference. The content is all present in the new files, but it may
be easier for you to have the old files for reference.
1. Be sure to have newest files in the release-notes and docs-common
module. 'cvs up -d' can help to make sure you get new files.
2. All languages except en have been removed from the Makefile target:
LANGUAGES = en #it ja_JP ru zh_CN
# uncomment languages when you have all the same
# fies localized as are listed in XMLEXTRAFILES
As the comments say, when you are ready to test the build for your
language, move the language code to the left of the #comment mark
and run 'make html'.
3. Old files are left in place for you to use. You can take the
existing translation and move it to the new location. When you are
done, or let us know on fedora-docs-list(a)redhat.com and the old
files will get cleaned up.
4. Some of the old language specific files have been renamed. In the
cases where content has been split into multiple files or the file
is new, a blank file has been created. You need to move content
from the old file into the new file, as per the table below.
5. This table shows the name of the old file and the name of the new
file. This conversion has been done for -en only. Three old files
on the left have been split into two or more files on the right.
They are development-tools*xml, security*xml, and splash*xml.
Old filename New filename
=============================================================
[New File] ArchSpecific-en.xml
[New File] ArchSpecificPPC-en.xml
[New File] ArchSpecificx86-en.xml
[New File] ArchSpecificx86_64-en.xml
[New File] BackwardsCompatibility-en.xml
colophon-relnotes-en.xml Colophon-en.xml
daemons-en.xml SystemDaemons-en.xml
database-servers-en.xml DatabaseServers-en.xml
desktop-en.xml Desktop-en.xml
development-tools-en.xml DevelopmentTools-en.xml
DevelopmentToolsGCC-en.xml
DevelopmentToolsJava-en.xml
entertainment-en.xml Entertainment-en.xml
file-servers-en.xml FileServers-en.xml
file-systems-en.xml FileSystems-en.xml
hardware-reqs-en.xml [Deleted]
i18n-en.xml I18n-en.xml
install-notes-en.xml Installer-en.xml
intro-en.xml Introduction-en.xml
java-package-en.xml PackageNotesJava-en.xml
kernel-en.xm Kernel-en.xml
legacy-en.xml Legacy-en.xml
misc-server-en.xml [Deleted]
multimedia-en.xml Multimedia-en.xml
networking-en.xml Networking-en.xml
overview-en.xml OverView-en.xml
package-movement-en.xml PackageChanges-en.xml
package-notes-en.xml PackageNotes-en.xml
printing-en.xml Printing-en.xml
project-overview-en.xml ProjectOverview-en.xml
README-en.xml [Ignore]
RELEASE-NOTES-en.xml [Same]
RELEASE-NOTES-master-en.xml [Deleted]
samba-en.xml Samba-en.xml
security-en.xml Security-en.xml
SecuritySELinux-en.xml
server-tools-en.xml ServerTools-en.xml
splash-en.xml Welcome-en.xml
(content split into:) OverView-en.xml
web-servers-en.xml WebServers-en.xml
xorg-en.xml Xorg-en.xml
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Content Services Fedora Documentation Project
http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject
18 years, 3 months
Watch out with system-config-netboot
by Josep Puigdemont
Hi!
You'll notice that system-config-netboot is set to QA by a commit from
yesterday (21st December). The commit comment is:
"note to translators: system-config-netboot.desktop.in msgstrs appended
to .po files: please translate"
Unfortunately the translation of these new strings are set back to the
English text, for instance:
#: system-config-netboot.desktop.in:5
msgid "Configure network boot server."
msgstr "Configure network boot server."
This affects the last three strings in the file.
Regards!
/Josep
--
"Any society that would give up a litte liberty to gain a little
security will deserve neither and lose both."
--- Benjamin Franklin
18 years, 3 months
