May I write about my experience. Perhaps it would help to avoid confusion for me, and for
you. I don't want to cause extra work for anyone.
I was directed to the website where I found the draft to Fedora 19 release notes. I worked
for a technical publishing company that reviewed software, and published in multiple
langauges. I learned the embarassing way, that my writing skills were horrid. But they
trained me to do corrections and I applied those lessons to the document. This is what I
I went through each paragraph with care, insuring that when a followup sentence indicated
or started with "This", that there was only one topic in the preceding
sentence. I applied other rules, that would help with automated (Google style)
translation. Some of those editing actions I took were to insure that nouns were not
omitted, (this was referring to a previous sentence with two subjects. I added a noun to
point to the subject of the follow up sentence. If there was a runon sentence, I split
them in two. (runon = "While running down the stairs, the firebell rang). Finally,
to correct the use of "on". As I mentioned in earlier emails, one can be on
topic or off topic, but one is on the podium giving a talk. If you use on, I try to see
if it means on the desk, on the floor, etc. I cannot write to you on Linux, but I can
write to you about Linux. If there was a lot of stuff, it would be "On the topic of
I tried to use "refer to", "visit", "consult" and see as
follows. Refer to link xyzabc.zzz. I may appear redundant, but my view is that Fedora
is a quality product, and deserves a quality accompanying document. It is not necessary
to use words that make the author appear pedantic.
If there are already guidelines for authors, I apologize for being redundant and
I need a mentor. I can do translation to/from French, and can translate from Spanish to
French or English.
Mr. Leslie Satenstein
An experienced Information Technology specialist.
Yesterday was a good day, today is a better day,
and tomorrow will be even better.lsatenstein(a)yahoo.com
SENT FROM MY OPEN SOURCE LINUX SYSTEM.
From: Pete Travis <me(a)petetravis.com>
To: Jérôme Fenal <jfenal(a)gmail.com>
Cc: Leslie S Satenstein <lsatenstein(a)yahoo.com>; docs(a)lists.fedoraproject.org;
Sent: Saturday, May 18, 2013 4:09 PM
Subject: Re: Release Notes available for Review
On May 18, 2013 1:26 PM, "Jérôme Fenal" <jfenal(a)gmail.com> wrote:
> 2013/5/15 Pete Travis <me(a)petetravis.com>:
> > On 05/14/2013 03:21 PM, Leslie S Satenstein wrote:
> > I have corrected and revised the English F19 release notes. Up to the end of
> > section 3. There is an attachment to Bugzilla. which is the new text
> > following corrections.
> > The original is still on the website in English
> > Here is what I have modified. (refer to attachment)
> Hi all,
> Don't know if modifications were applied to Transifex, here's a bunch
> of updates while I proofread content already translated to French,
> including old content.
> * A list of commonly reported bugs and known issues for this release
> is available from <ulink
> --> URL to set at http://fedoraproject.org/wiki/Common_F19_bugs
> page does indeed exist. Any mean to make a redirection in the wiki
> (Current_Fcurrent_bugs page for instance) to avoid modifying doc again
> and again the same it's done with &FPRODVER; entities?
> Hardware overview
> * Additional space is also required for any user data, and at least 5%
> free space should be maintained for proper system operation.
> Use "5%" or double % (5%%) to comply with gettext "%"
> and to avoid issues in Transifex.
> Double slash in URL:
> Beginning with Fedora 18, the Release Notes are stored in
> --> Use &PRODVER; in the URL.
> Fedora PRODVER; includes the latest version of the
> <application>GNOME</application> desktop, 3.8.
> --> missing "&" in &PRODVER;
> Amateur Radio
> Addition of the ability to add and connect formally defined
> asychronous message ports to signal processing blocks and hierarchical
> --> s/asychronous/asynchronous/
> That's all for now.
> More to come as we continue proofreading already translated strings,
> and translate new strings.
> Jérôme Fenal
There are some changes I've applied, and some I need to catch up on. Is it better to
push these changes to Transifex as they happen? I've been holding back for
proofreading and feature changes, with the impression that it would make less overall work
In the next week, my plan is to review for feature changes and suggested fixes so
there's something to publish for the Beta release, including updated translations.
Thanks for your help in doing double duty as both translator and proofreader!