Re: release-notes/po RELEASE-NOTES.pot,NONE,1.1
by Yuan Yijun
2006/2/28, jtr Tommy Reynolds <fedora-docs-commits(a)redhat.com>:
> Author: jtr
>
> Update of /cvs/docs/release-notes/po
> In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1722
>
> Added Files:
> RELEASE-NOTES.pot
> Log Message:
> Include ".pot" file into the CVS archive.
>
>
When will there be pot for IG and when can IG be built?
--
bbbush ^_^
17 years, 7 months
Re: docs-common Makefile.common,1.73,1.74
by Paul W. Frields
On Mon, 2006-02-27 at 14:12 -0500, Karsten Wade wrote:
> Author: kwade
>
> Index: Makefile.common
> ===================================================================
> RCS file: /cvs/docs/docs-common/Makefile.common,v
> retrieving revision 1.73
> retrieving revision 1.74
> diff -u -r1.73 -r1.74
> --- Makefile.common 26 Feb 2006 22:40:53 -0000 1.73
> +++ Makefile.common 27 Feb 2006 19:12:12 -0000 1.74
> @@ -756,7 +756,7 @@
> define LOCALE_template
> .PHONY: set-locale-${1}
> set-locale-${1}::
> - ${LN} -f -s ${FDPDIR}/docs-common/common/entities/entities-${1}.ent \
> + ${LN} -f -s ${FDPDIR}/docs-common/common/entities/entities-${1}.xml \
> ${LOCALE_ENTITIES}
Err... doesn't this break stuff? The .ent file is generated from
the .xml, and the LOCALE_ENTITIES is a link to those entities. If you
link to the .xml sources things stop working.
--
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/
17 years, 7 months
[RFC] Towards translatable entities
by Tommy Reynolds
Hi Ya'll
<<<DO NOT CHANGE ANY OF YOUR FILES BASED ON THIS EMAIL!>>>
What follows is an approach to a thorny problem the translators are
encountering. ALL DOCUMENT AUTHORS should read this too, because a
small amount of re-editing will be necessary if this approach is
adopted. I think it will be a one-line change to the
"${PRI_LANG}/${DOCBASE}.xml" file.
Currently, each document hard-codes the filename needed to include
the FDP entities:
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM
"../../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
<!ENTITY DOCNAME "example-tutorial">
<!ENTITY DOCVERSION "0.14.1"> <!-- change version here -->
<!ENTITY DOCDATE "2006-01-21"> <!-- change revision date here -->
<!ENTITY DOCID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)">
<!ENTITY BUG-NUM "000000"> <!-- use this only while in draft stage -->
]>
In addition, several additional entities, such as "&DOCDATE;", must
be manually edited each time the document is rebuilt.
This technique of using entities makes effective translations
difficult because filename paths and entities are outside the scope
of the text addressed by the translation tools. Thus, it is not
currently possible to have completely automated I18N support.
By re-using the same tools and techniques already in place for the
document body translation, it should be possible to:
1) Place all entity definitions for a single locale into an XML file
described by a custom DTD. Utilize .POT and .PO files, in
conjunction with an XSL stylesheet, to automatically derive
non-English, aka ${OTHERS}, XML files. Just like we can do for
the document body files.
2) Instead of referencing a locale-specific href in the <DOCTYPE>
declaration, reference a fixed filename "entities.ent" that will
actually be a symbolic link (or an equivalent method) to the
translated entity file produced above. The building system
"Makefile.common" should be able to do this transparently to
document authors.
3) Dynamic entities like "&DOCDATE;" can easily be implemented by
"Makefile.common" and XSL stylesheet surgery. This will
eliminate the in-document entity definitions in favor of entities
that we can derive from the "rpm-info.xml" file.
So far, I've sketched out a preliminary framework. The DTD, a sample
entity definition XML file, an XSL stylesheet and a Makefile are
available at my ftp://ftp.megacoder.com/pub/entities/ site.
Please take a look at this proof-of-concept and post your comments
and suggestions.
Cheers
--
I'm already an anomaly, I shall soon be an anachronism, and I have
every intention of dying an abuse!
17 years, 7 months
new Editor-in-Chief for release notes
by Karsten Wade
I'm quite pleased to inform you that Robert 'Bob' Jensen is taking over
the Editor-in-Chief role for the release notes.
For the rest of FC5 release, Bob and I are working closely together on
everything from language edits, Wiki2XML, and publication. The goal is
for Bob to be running things by FC6 test1.
Here are some of the tasks of the EiC:
* Watches all commits to Docs/Beats
* Edits content for style, clarity, and markup consistency
* Coordinates the beat writers (project management)
- Updating release note schedules[1]
- Scheduling announcing and enforcing
- Recruiting help
* Ensures content goes:
Wiki -> XML -> PO/POT -> XML -> HTML/TXT -> {ISO, Website}
* Looks for improvements to the release notes
- Automation
- Process changes
- Tool changes
Thanks - Karsten
[1] http://fedoraproject.org/wiki/DocsProject/Schedule
--
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
17 years, 7 months
release-notes.pot
by Francesco Tombolini
Hi all,
today I have seen that ru.po was added in the cvs, I have seen that the
zh_cn.po is present too, but the first is about 548 strings while the second
is 553...
How do we have homogeneous documents without a common .pot file?
Do I have to make one by myself too?
If so, I need help to generate a single .po file with all release-notes
content...
Thank-you
--
Francesco Tombolini <tombo(a)adamantio.net>
17 years, 7 months
changes to legal notice
by Karsten Wade
I've prepared and verified the following changes to our legal notice,
which I am going to put in CVS. I have one question first:
Do we use any Red Hat trademarks in Fedora documentation?
I think we do, we at least refer to Red Hat on occasion. Just want to
be sure I'm not missing something obvious.
This file is docs-common/common/legalnotice-content-en.xml, now tagged
"docs-common-new-canonical-legal-notice-using-OPL".
We'll begin actual usage of this legal notice with each document when we
have relicensing sign-off from each contributor.
## begin new legal notice in entirety
Copyright (c) 2006 by Fedora Foundation and others. This material may be
distributed only subject to the terms and conditions set forth in the
Open Publication License, v1.0, available at
http://www.opencontent.org/openpub/.
Garrett LeSage created the admonition graphics (note, tip, important,
caution, and warning). Tommy Reynolds Tommy.Reynolds(a)MegaCoder.com
created the callout graphics. They all may be freely redistributed
with documentation produced for the Fedora Project.
FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat,
Inc., are registered or pending registration in the U.S. and other
countries, and are used here under license to the Fedora Foundation.
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of
Red Hat, Inc. in the United States and other countries.
All other trademarks and copyrights referred to are the property of
their respective owners.
Documentation, as with software itself, may be subject to export
control. Read about Fedora Project export controls at
http://fedoraproject.org/wiki/Legal/Export
## end new legal notice
--
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
17 years, 7 months
Re: docs-common Makefile.common,1.69,1.70
by Tommy Reynolds
Uttered "Paul W. Frields" (pfrields) <fedora-docs-commits(a)redhat.com>, spake thus:
> Add another phony alias "help" for better across-the-project adherence
> (q.v. Fedora Extras), plus it makes a weird kind of sense.
>
> -targets::
> +help targets::
> @printf ${TFMT} 'targets' 'Outputs target summaries'
> @printf ${TFMT} 'text' 'Same as "txt" target'
Good! I was going to just s/targets/help/ anyway.
--
I'm already an anomaly, I shall soon be an anachronism, and I have
every intention of dying an abuse!
17 years, 7 months
Re: docs-common Makefile.common,1.68,1.69
by Paul W. Frields
On Wed, 2006-02-22 at 20:45 -0500, Tommy Reynolds wrote:
> Author: jtr
>
> Update of /cvs/docs/docs-common
> In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25460
>
> Modified Files:
> Makefile.common
> Log Message:
> Use xml2po(1) for all XML=>PO=>XML conversions; drop dependancy on
> the buggy po2xml(1) from the kdesdk. This allows translators to free
> up potentially 82Mbyte or so of disk space as a bonus.
Bless you, BLESS YOU. Now if we could only get someone to break
"meinproc" free of kdeutils...
/me thinks "Hmm, what a strange and awful lot of KDE lib dependencies
for a console app. Mayhap this needs some exercise of GPL freedom."
--
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/
17 years, 7 months