10:07 p.m.
The work on the Release Notes so far has been posted to
http://fedorapeople.org/groups/docs/release-notes/ for review. If you
have a chance, please look it over for technical errors and grammatical
flops.
Thanks,
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
4:15 p.m.
2013/5/14 Pete Travis <me(a)petetravis.com>:
The work on the Release Notes so far has been posted to
http://fedorapeople.org/groups/docs/release-notes/ for review. If you
have a chance, please look it over for technical errors and grammatical
flops.
Hi,
Spotted typos during translation to French:
In database_servers:
- Apache <package>Derby</package>, an open source relational database
**impelmented** entirely
--> implemented
- If required, the original MySQL packages are still available as
<filename>community-mysql</filename>.
--> should the tag be <filename> or <package>?
Multimedia:
To comply with XDG Base ***Direcotry*** specifications...
Productivity:
<function>xargs</function>, <function>printf</function> and regex
functions.
--> <function>xargs</function>, <function>printf</function>
and
<function>regex</function> functions.
sed... to separate lines by **ACII** NULL characters
--> ASCII NUL (both terms to modify)?
Virtualization:
Changes with <productname>OpenShift Grizzly</productname>
--> Should be Openstack...
Ceilomeer
--> Ceilometer
Snapshots can done to block devices as well as
--> can *be* done
That a first review of what is currently being translated in French
for the release notes. Expect more to come.
Regards,
J.
4:21 p.m.
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)
Regards
Leslie
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
alternative: leslie.satenstein(a)gmail.com
SENT FROM MY OPEN SOURCE LINUX SYSTEM.
________________________________
From: Jérôme Fenal <jfenal(a)gmail.com>
To: immanetize(a)fedoraproject.org; For participants of the Documentation Project
<docs(a)lists.fedoraproject.org>
Sent: Tuesday, May 14, 2013 5:15 PM
Subject: Re: Release Notes available for Review
2013/5/14 Pete Travis <me(a)petetravis.com>:
> The work on the Release Notes so far has been posted to
> http://fedorapeople.org/groups/docs/release-notes/ for review. If you
> have a chance, please look it over for technical errors and grammatical
> flops.
Hi,
Spotted typos during translation to French:
In database_servers:
- Apache <package>Derby</package>, an open source relational database
**impelmented** entirely
--> implemented
- If required, the original MySQL packages are still available as
<filename>community-mysql</filename>.
--> should the tag be <filename> or <package>?
Multimedia:
To comply with XDG Base ***Direcotry*** specifications...
Productivity:
<function>xargs</function>, <function>printf</function> and regex
functions.
--> <function>xargs</function>, <function>printf</function>
and
<function>regex</function> functions.
sed... to separate lines by **ACII** NULL characters
--> ASCII NUL (both terms to modify)?
Virtualization:
Changes with <productname>OpenShift Grizzly</productname>
--> Should be Openstack...
Ceilomeer
--> Ceilometer
Snapshots can done to block devices as well as
--> can *be* done
That a first review of what is currently being translated in French
for the release notes. Expect more to come.
Regards,
J.
--
docs mailing list
docs(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/docs
7:05 p.m.
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)
Regards
*
Leslie
*
Thanks for reviewing, Leslie. I've looked over your attachment to
https://bugzilla.redhat.com/show_bug.cgi?id=962869 and made changes
accordingly. I'm assuming the attachments you've been emailing are the
same as those posted to bugzilla; it's much easier to keep track of there.
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
2:26 p.m.
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.
Feedback
========
* A list of commonly reported bugs and known issues for this release
is available from <ulink
url="http://fedoraproject.org/wiki/Common_F18_bugs">
--> URL to set at http://fedoraproject.org/wiki/Common_F19_bugs, the
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 "%"
handling,
and to avoid issues in Transifex.
Overview
========
Double slash in URL:
http://fedoraproject.org/wiki/Releases//FeatureList
RelNotesDirChange
===============
Beginning with Fedora 18, the Release Notes are stored in
<filename>/usr/share/doc/fedora-release-notes-18.0/</filename>.
--> Use &PRODVER; in the URL.
Desktop
=======
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
blocks
--> s/asychronous/asynchronous/
That's all for now.
More to come as we continue proofreading already translated strings,
and translate new strings.
Regards,
J.
--
Jérôme Fenal
3:09 p.m.
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.
Feedback
========
* A list of commonly reported bugs and known issues for this release
is available from <ulink
url="http://fedoraproject.org/wiki/Common_F18_bugs">
--> URL to set at http://fedoraproject.org/wiki/Common_F19_bugs, the
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 "%"
handling,
and to avoid issues in Transifex.
Overview
========
Double slash in URL:
http://fedoraproject.org/wiki/Releases//FeatureList
RelNotesDirChange
===============
Beginning with Fedora 18, the Release Notes are stored in
<filename>/usr/share/doc/fedora-release-notes-18.0/</filename>.
--> Use &PRODVER; in the URL.
Desktop
=======
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
blocks
--> s/asychronous/asynchronous/
That's all for now.
More to come as we continue proofreading already translated strings,
and translate new strings.
Regards,
J.
--
Jérôme Fenal
Hey Jerome,
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 for translators.
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!
-- Pete
3:39 p.m.
2013/5/18 Pete Travis <me(a)petetravis.com>:
Hey Jerome,
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 for translators.
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!
Hi Pete,
In my view, as we translators usually either use Transifex's online
interface or advanced tools such as Lokalize which maintain a
translation memory, you should push modifications as soon as possible.
Release early, release often. Or said otherwise: the earlier, the better.
That way, unstranslated strings would be spotted early, and we could
easily reuse previously translated strings using the translation
memory.
So go for it as they come. That's my own view, others may have a different PoV.
Maybe you'd want to ask on trans(a)gp.o ?
Or just proceed, as only one or two languages seem to go fast here.
Regards,
J.
--
Jérôme Fenal
4:12 p.m.
Virtualization
==========
* <productname>OpenShift Origin</productname>, the open source version of...
--> OpenShift Enterprise is also open source. Use "community version"
instead of open source to designate community versions (that should be
part of the general documentation recommendations).
* Changes with <productname>OpenShift Grizzly</productname>
--> s/OpenShift/OpenStack/ (already said, I guess, good illustration
of the release early/release often since I'm now translating it, and
will have to change it again after source update).
* Unified config has been implemented to simplify administration, visit<ulink
--> add a space before <ulink /> tag
4:24 p.m.
On May 18, 2013 3:12 PM, "Jérôme Fenal" <jfenal(a)gmail.com> wrote:
Virtualization
==========
* <productname>OpenShift Origin</productname>, the open source version
of...
--> OpenShift Enterprise is also open source. Use "community
version"
instead of open source to designate community versions (that should be
part of the general documentation recommendations).
* Changes with <productname>OpenShift Grizzly</productname>
--> s/OpenShift/OpenStack/ (already said, I guess, good illustration
of the release early/release often since I'm now translating it, and
will have to change it again after source update).
This is the point I worry about - frustrating translators with
retranslating. I tend to agree with you, since fixes pushed sooner will
affect fewer languages. I think our existing model of pushing POTs only at
release stages - Alpha, Beta, Final - bears reevaluation. I'll bring it up
at Monday's docs meeting, you're welcome to attend.
* Unified config has been implemented to simplify administration,
visit<ulink
--> add a space before <ulink /> tag
I'll take care of the rest and push POTs later today, thanks again.
--Pete
4:31 p.m.
2013/5/18 Pete Travis <me(a)petetravis.com>:
On May 18, 2013 3:12 PM, "Jérôme Fenal" <jfenal(a)gmail.com> wrote:
>
> Virtualization
> ==========
> * <productname>OpenShift Origin</productname>, the open source version
> of...
> --> OpenShift Enterprise is also open source. Use "community version"
> instead of open source to designate community versions (that should be
> part of the general documentation recommendations).
>
> * Changes with <productname>OpenShift Grizzly</productname>
> --> s/OpenShift/OpenStack/ (already said, I guess, good illustration
> of the release early/release often since I'm now translating it, and
> will have to change it again after source update).
>
This is the point I worry about - frustrating translators with
retranslating. I tend to agree with you, since fixes pushed sooner will
affect fewer languages. I think our existing model of pushing POTs only at
release stages - Alpha, Beta, Final - bears reevaluation. I'll bring it up
at Monday's docs meeting, you're welcome to attend.
Next Monday is mostly off in France (Whitmonday), will see if I can
attend. I just hope we won't have the netsplits we had last week,
which seem to have killed the meeting (I was mostly on time, but day
job grabbed my attention quickly between the netsplits).
> * Unified config has been implemented to simplify
administration,
> visit<ulink
> --> add a space before <ulink /> tag
I'll take care of the rest and push POTs later today, thanks again.
Thanks.
J.
--
Jérôme Fenal
5:02 p.m.
Network
=======
* Federated VOIP
--> s/VOIP/VoIP/
* Dynamic firewall configuration by applications can now be locked down
completely, or limited to a whitelist. The whitelist can contain commands,
users, UIDs, and selinux contexts.
--> s/selinux/SELinux/ ?
* command name="/usr/bin/python /bin/firewall-cmd*"
--> Shouldn't the * (joker) be separated from firewall-cmd, as it
would allow any command named /bin/firewall-cmdsomething to be
allowed?
* The <application>BIND10</application> is now shipped in the Fedora
--> Maybe the application word outside the tags is missing there. Such
as: The <application>BIND10</application> [suite|application] is
now...
Or remove the leading article "The".
Enough for tonight.
Cheers,
J.
--
Jérôme Fenal
3:49 a.m.
Thanks for the updates, I've re-applied the previous translations or
provided translations for the new strings.
Still a few fixes to apply
Cloud
=====
* <primary>OpenStack</primary><secondary>Origin</secondary>
That should really be:
<primary>OpenShift</primary><secondary>Origin</secondary>
Really.
* s/Ceiliometer/Ceilometer/ somewhere in the section:
OpenStack is upgraded to the latest stable release, code named
"Grizzly". OpenStack Grizzly includes the Incubation projects Heat and
***Ceiliometer***, [...]
Regards,
J.
--
Jérôme Fenal
6:46 a.m.
On Mon, May 20, 2013 at 4:49 AM, Jérôme Fenal <jfenal(a)gmail.com> wrote:
*
<primary>OpenStack</primary><secondary>Origin</secondary>
That should really be:
<primary>OpenShift</primary><secondary>Origin</secondary>
* s/Ceiliometer/Ceilometer/ somewhere in the section:
OpenStack is upgraded to the latest stable release, code named
"Grizzly". OpenStack Grizzly includes the Incubation projects Heat and
***Ceiliometer***, [...]
Fixed.
--
Ben Cotton
9:08 a.m.
2013/5/20 Ben Cotton <bcotton(a)fedoraproject.org>:
On Mon, May 20, 2013 at 4:49 AM, Jérôme Fenal
<jfenal(a)gmail.com> wrote:
> * <primary>OpenStack</primary><secondary>Origin</secondary>
> That should really be:
> <primary>OpenShift</primary><secondary>Origin</secondary>
OK
> * s/Ceiliometer/Ceilometer/ somewhere in the section:
> OpenStack is upgraded to the latest stable release, code named
> "Grizzly". OpenStack Grizzly includes the Incubation projects Heat and
> ***Ceiliometer***, [...]
Hmm, I still see "Ceiliometer" and not "Ceilometer".
--
Jérôme Fenal
4:35 p.m.
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
did.
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
Linux......".
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
pedantic.
I need a mentor. I can do translation to/from French, and can translate from Spanish to
French or English.
Regards
Leslie
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
alternative: leslie.satenstein(a)gmail.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;
immanetize(a)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.
>
> Feedback
> ========
> * A list of commonly reported bugs and known issues for this release
> is available from <ulink
> url="http://fedoraproject.org/wiki/Common_F18_bugs">
> --> URL to set at http://fedoraproject.org/wiki/Common_F19_bugs, the
> 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 "%"
handling,
> and to avoid issues in Transifex.
>
> Overview
> ========
> Double slash in URL:
> http://fedoraproject.org/wiki/Releases//FeatureList
>
> RelNotesDirChange
> ===============
> Beginning with Fedora 18, the Release Notes are stored in
> <filename>/usr/share/doc/fedora-release-notes-18.0/</filename>.
> --> Use &PRODVER; in the URL.
>
> Desktop
> =======
> 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
> blocks
> --> s/asychronous/asynchronous/
>
> That's all for now.
> More to come as we continue proofreading already translated strings,
> and translate new strings.
>
> Regards,
>
> J.
> --
> Jérôme Fenal
Hey Jerome,
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
for translators.
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!
-- Pete
3857
days inactive
3863
days old
15 comments
4 participants
participants (4)
-
Ben Cotton -
Jérôme Fenal -
Leslie S Satenstein -
Pete Travis