problem with relnotes build [HELP]
by Karsten Wade
I'm having problems with building the release-notes currently from HEAD
in CVS[1].
The essence of the error from xmlto[2] is:
"I don't like the stuff that comes after the <article> declaration, it's
not the right sort of thing according to the DTD, and here is a list of
what I expect ..."
However, what it expects includes <articleinfo>, which is what
immediately follows!
<article id="index" lang="en">
<articleinfo>
<title>&FC; &LOCALVER; Release Notes</title>
<copyright>
<year>2006</year>
<holder>&FORMAL-RHI;</holder>
</copyright>
&LEGALNOTICE-RELNOTES;
</articleinfo>
I have combed through the entities, the supporting files, such as the
legalnotice pieces, have recreated the entire content block using
automatic tag creation, and looked at the differences between this
current version and many earlier versions.
I cannot find anything that would cause this. I suspect that it is
something wrong or missing in the <DOCTYPE []> header. It could be the
new DOCID structure? Seems OK, though ... Perhaps I'm missing an
ENTITY? I don't see one from previous versions ...
tia - Karsten
[1] viewcvs of content
http://cvs.fedora.redhat.com/viewcvs/release-notes/?root=docs
http://cvs.fedora.redhat.com/viewcvs/release-notes/RELEASE-NOTES-en.xml?r...
[2] xmlto error output
make html
LANG=en.UTF-8 xmlto html -x /home/kwade/Documents/projects/fedora/cvs-
docs/release-notes/../docs-common/xsl/main-html.xsl -o RELEASE-NOTES-en
RELEASE-NOTES-en.xml
xmlto: input does not validate (status 3)
/home/kwade/Documents/projects/fedora/cvs-docs/release-notes/RELEASE-
NOTES-en.xml:67: element article: validity error : Element article
content does not follow the DTD, expecting ((title , subtitle? ,
titleabbrev?)? , articleinfo? , tocchap? , lot* , (((calloutlist |
glosslist | itemizedlist | orderedlist | segmentedlist | simplelist |
variablelist | caution | important | note | tip | warning |
literallayout | programlisting | programlistingco | screen | screenco |
screenshot | synopsis | cmdsynopsis | funcsynopsis | classsynopsis |
fieldsynopsis | constructorsynopsis | destructorsynopsis |
methodsynopsis | formalpara | para | simpara | address | blockquote |
graphic | graphicco | mediaobject | mediaobjectco | informalequation |
informalexample | informalfigure | informaltable | equation | example |
figure | table | msgset | procedure | sidebar | qandaset | anchor |
bridgehead | remark | highlights | abstract | authorblurb | epigraph |
indexterm | beginpage)+ , (sect1* | refentry* | simplesect* | section*))
| sect1+ | refentry+ | simplesect+ | section+) , ((toc | lot | index |
glossary | bibliography) | appendix | ackno)*), got (articleinfo CDATA
CDATA CDATA CDATA CDATA CDATA CDATA CDATA CDATA CDATA CDATA CDATA )
Document /home/kwade/Documents/projects/fedora/cvs-docs/release-
notes/RELEASE-NOTES-en.xml does not validate
make: *** [RELEASE-NOTES-en/index.html] Error 3
--
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
Re: release-notes FileSystems-it.xml, NONE, 1.1 ArchSpecific-it.xml, 1.1, 1.2 ArchSpecificPPC-it.xml, 1.1, 1.2 ArchSpecificx86_64-it.xml, 1.1, 1.2 ArchSpecificx86-it.xml, 1.1, 1.2 BackwardsCompatibility-it.xml, 1.1, 1.2 Colophon-it.xml, 1.1, 1.2 Data
by Yuan Yijun
2006/1/9, tombo Francesco Tombolini <fedora-docs-commits(a)redhat.com>:
> Author: tombo
>
> Update of /cvs/docs/release-notes
> In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15798
>
> Modified Files:
> ArchSpecific-it.xml ArchSpecificPPC-it.xml
> ArchSpecificx86_64-it.xml ArchSpecificx86-it.xml
> BackwardsCompatibility-it.xml Colophon-it.xml
> DatabaseServers-it.xml DevelopmentToolsGCC-it.xml
> DevelopmentToolsJava-it.xml Networking-it.xml
> PackageNotes-it.xml RELEASE-NOTES-it.xml
> SecuritySELinux-it.xml Welcome-it.xml
> Added Files:
> FileSystems-it.xml
> Log Message:
> compile ok - content need check
>
>
Did you find anything strange in the latest -en version? Such as
trademark tags are replaced by trademark characters, and the ulink
"OpenFirmware"? There are a lot of LOCALVER replaced by "Fedora Core 5
test1", too.
--
bbbush ^_^
18 years, 3 months
Separate directories for each Language for Release notes (and other docs)
by A S Alam
Hello,
I am working for Translation (now for Release Notes), I found there is
single Directory as
release-notes/
319 Files are there,
but why not we make Separate Directory for Each Language
-> with this big number of file in a single folder, it is somehow
difficult to only "en" files
->New Translator will find this easy to copy "en" folder as Template to
his/her Language (like "pa")
->Easy to Maintain each language (as I would like to work for Punjabi
and I need to check only "en" and "pa" folder for those)
->If there is any problem with Language, then easy to check a folder and
fix, then searching in big list for files
thanks
regards
A S Alam
Punjabi (Gurmukhi)
18 years, 3 months
Help with migration to bigger hard drive
by Stefan Stefanov
Please,
Help me with exchanging the harddrive of a running server with a bigger one!
It is practically impossible to repeat all tricks and installations again, there fore I want to clone the disk.
I have FC3 on 30 Gb disk and a new 200 Gb IDE disk. What did I do:
I unpluged the original 30Gb disk, pluged the 200 Gb instead and installed the same FC3 - minimal installation on it using anaconda defaults.
Then I put 30Gb as master and 200 as slave. Checked with fsdisk -l and saw the same partitions: 1-13 hda1 - bootable and 14-end hda2 - rest for the 30gb
and 1-13 hdb1 bootable and 14-end the second one for the 200gb
I mounted -t ext3 hdb2 one to /mnt/linux_backup/ and hdb1 to /mnt/linux_backup/boot
I copied with rsync everything except /mnt and /proc to /mnt/linux_backup
Than I umplugged and exchanged slave master - it booted again the small disk although under the name /dev/hdb !
I unlugged the small one and than it didn't boot at all - only GRUB on the black screen.
I plugged back messed up with glub alittle bit and plug the new disk alone again.
This time Fedora starts but it stopps at the very beginning and writes things like:
cannot find Logical volumes
Kernel panic
It has something to do with the Vol00 system that is installed but I do not know what to do!
Please, can somebody help me because this server is important for us - we are biologists.
Thank you,
Stefan
18 years, 3 months
info2rpminfo
by Tommy Reynolds
Paul,
How should info2rpminfo.xsl be used? I've tried it against the
Install Guide and get tons of "Failure to process entity" messages
and no output.
Halp!
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
Comments in configuration files
by Rahul Sundaram
Hi
It seems that several configuration files in Fedora does not include
helpful comments as necessary to guide users on where to look for
information or which formats to follow. The crontab files could have a
initial commented line specifying the format or hosts file could refer
people to its man page for examples. Would the documentation team be
willing to file bug reports with comments/content as appropriate?
Do we need such guidelines as inclusion/release criteria?
18 years, 3 months
DocsRawhide
by Patrick W. Barnes
I've replaced the bulkbuild script from docs-common/bin/bulkbuild with
the build-docs package based upon it. This package is what will power
the webtest server, and you are welcome to add additional scripts as
needed, just make sure to modify the Makefile and .spec file
accordingly. Try to provide an explanation of any structural changes so
we are all on the same page.
--
Patrick "The N-Man" Barnes
nman64(a)n-man.com
http://www.n-man.com/
--
Have I been helpful? Rate my assistance! http://rate.affero.net/nman64/
18 years, 3 months
