#32: Probable typos in the F10 preview release notes
---------------------+------------------------------------------------------
Reporter: runab | Owner: quaid
Type: defect | Status: new
Priority: minor | Milestone:
Component: Content | Version: 10
Keywords: |
---------------------+------------------------------------------------------
The following strings probably contain some minor typos:
string # 43:
"All of the packages from a DVD install can occupy over 9 GB of disk
space.
The final install size is determined by the installing spin and the
packages
selected during installation. Additional disk space is required during
installation to support the installation environment. The additional disk
space corresponds to the size of /Fedora/base/stage2.img plus the size of
the files in /var/lib/rpm on the installed system."
probable correction:
"filename" tags missing for "/Fedora/base/stage2.img" and "/var/lib/rpm".
Ref: string 32 and 321
string # 437:
"There is no support for Xen or kdump for the PowerPC architecture in
Fedora.
32-bit PowerPC does still have a separate SMP kernel."
probable correction:
"32-bit PowerPC does still have a separate SMP kernel." => "32-bit PowerPC
still has a separate SMP kernel."
string # 581:
"indhi" => should be "Sindhi"
string # 993:
"<ulink url=\"http://fedoraproject.org/wiki/ThomasCanniot\">
ThomasCanniot</
ulink> (translator - French)"
correction: A space missing between "Thomas" and "Canniot"
Thanks
Runa
--
Ticket URL: <https://fedorahosted.org/release-notes/ticket/32>
Fedora Release Notes <https://fedorahosted.org/release-notes/>
Fedora Release Notes
#31: Internal communication included in the notes released for translation
---------------------+------------------------------------------------------
Reporter: runab | Owner: quaid
Type: defect | Status: new
Priority: minor | Milestone:
Component: Content | Version: 10
Keywords: |
---------------------+------------------------------------------------------
The following messages in the release notes look like internal
communication between writers:
string # 286:
"Content pulled from wiki; changes to match Publican; cruft removed"
string # 292:
"Content changes for Publican 0.37 compatibility"
string # 296:
"Revised for Publican compatibility"
string # 297:
"These Notes are Placeholders"
string # 365:
"This list is automatically generated. It is not a good choice for
translation."
string # 932:
"This content not updated until after Preview Release occurs."
string # 933:
"We need to finish writing and translating the notes to know who has
worked
on them."
Thanks
Runa
--
Ticket URL: <https://fedorahosted.org/release-notes/ticket/31>
Fedora Release Notes <https://fedorahosted.org/release-notes/>
Fedora Release Notes
In the spirit of Elizabeth West's recent tips for better writing,
here's one to consider:
Avoid the gerund wherever possible.
Gerunds are those words in English that end in "-ing." Sentences that
use them tend to feature awkward construction, passive voice, and lack
of conciseness. Gerunds also translate awkwardly in many languages.
Check out this example:
"Installing the foobar package is the only way of making it easy to
change baz configuration."
This is a bit unfair, because I've also mixed in a style problem that
I see many times in gerund-infested material, some of which I've
created myself. Now look at a reconstruction of the sentence:
"To change the configuration of baz, install the foobar package."
What are some of the effects of the rewrite?
* Drops sentence from 16 words to 10
* Increases clarity
* Provides a neutral tone of confident instruction instead of arrogance
* Puts the important material at the end of the sentence, which in
English is the position of emphasis
* Avoids personalizing the instructions too much.
* Avoids making qualitative judgments ("easy")
I always tend to look at gerunds I've written very critically. Far
more often than not, I find they pop up when I lack confidence in an
assertion. Technical documentation should be confident so users feel
they can trust the material.
Hope this helps!
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
Forwarding to -docs-list, as the folks here are more likely to give a
better answer.
-δ
---------- Forwarded message ----------
From: Domingo Becker <domingobecker(a)gmail.com>
Date: 2008/11/2
Subject: appliance in release-notes
To: Fedora Translation Project List <fedora-trans-list(a)redhat.com>
What is the meaning of appliance in the context of release-notes ?
release-notes mentions an appliance creation tool, a tool to create
appliance images from a kickstart file.
In this context, it is an installer for me. But, what would be the
right meaning of it?
What is an appliance image used for?
regards
Domingo Becker (es)
--
Fedora-trans-list mailing list
Fedora-trans-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-trans-list
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
#24: Decide what titles/roles to apply to workers for IG and add that to
rpminfo.xml
---------------------+------------------------------------------------------
Reporter: ke4qqq | Owner: quaid
Type: task | Status: new
Priority: trivial | Milestone: RC-ready
Component: Content | Version: 10.0.0
Keywords: |
---------------------+------------------------------------------------------
So since Paul and Stuart originally wrote the content for IG - and largely
the update for F10 was fact checking, editing with snippets of writing and
wordsmithing I don't know how comfortable I feel declaring everyone an
'author'. I've added all the details for $uscguys, eawest and myself; I
noticed that jsmith did the same thing. Thus I appoint quaid to make the
decision :)
--
Ticket URL: <https://fedorahosted.org/install-guide/ticket/24>
Fedora Installation Guide <https://fedorahosted.org/install-guide/>
Fedora Documentation - Installation Guide
Hi,
So, for every release, for the past several releases, I keep a note on
the ongoing development changes so that I can expand on them for the
release notes. I haven't spend enough time on the docs for this release
however so if anybody wants to go through these and make sure all of the
details are documented properly, it would be excellent.
---
* glitch free pulseaudio
* augeus conf
* upstart changes
* fedora nightlife
* live-creator runs in selinux enforcing mode
* http://fitzsim.org/blog/?p=27
* http://cyberelk.net/tim/2008/05/29/version-100/
* plymouth replaces rhgb
* IPA
* codeina replaced
* packagekit changes
* gdm doesnt allow root password
* https://fedorahosted.org/amber/
* http://blogs.gnome.org/cneumair/2008/07/08/its-done/
* getting rid of artistic 1.0 licensed software
* http://hehe2.net/linux-general/openofficeorg-30-what-to-expect/
* uvc and gspcav2 got merged in 2.6.26 and 2.6.27 respectively
* Hooking up PackageKit with preupgrade
* mail replaced with mailx
* xenner
* portreserve
--
Rahul
A couple bite-sized tips for writing as we collaborate on the wiki:
* Avoid dangling prepositions.
"Note the version you are upgrading from." <-- Incorrect
"Note the version from which you are upgrading." <-- Correct
* Avoid personalization ("you," "he," "she") where doing so doesn't
cause unnecessary awkwardness.
"Note the version from which you are upgrading." <-- Not as good
"Note the currently installed version." <-- Better
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
The Release Notes titles are cute and all, but in a couple cases may
be a little arch ("Are There Hideous Bugs and Terrible Tigers") for
final release. Can we change them in those cases to something that's
easier for translators and readers?
Paul
#33: Issues in AGPBeta#Scheduling_Tasks
-------------------------+--------------------------------------------------
Reporter: amani | Owner: quaid
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Content | Version: 10
Keywords: |
-------------------------+--------------------------------------------------
In https://fedoraproject.org/wiki/Docs/Drafts/AGBeta#Scheduling_Tasks and
https://fedoraproject.org/wiki/Docs/Drafts/AGBeta/Cron
no GUI tools are mentioned. Sysadmins need not necessarily use CLI
tools and in actual practice it is compulsory that they know.
So maybe the 'Additional Information' is in need of improvement.. But
the doc seems to be 'ready for editing' (?)
The first line "Fedora provides a cron facility for tasks
scheduling...." sounds odd. 'cron' is installed in the same way as in
many other distros.
Is the cron daemon a 'cron facility'? It should be rectified to
something like "The 'cron' daemon is the default CLI utility for
scheduling tasks".
--
Ticket URL: <https://fedorahosted.org/release-notes/ticket/33>
Fedora Release Notes <https://fedorahosted.org/release-notes/>
Fedora Release Notes