Re: Release-note is long and hard for translating
by Ankit Patel
Kris Thomsen wrote:
> Maybe the question really is: "Who are our users?"
> Which audience is Fedora targeted to?
>
> Beginners = short, beautiful, easy eatable (is that a word? ;) )
> Hardcore "haX0rs" = long, detailed - kind of what we do now.
>
> For me is Fedora for beginners - and of cause also for advanced users,
> but they would be able to read a detailed _english_ releasenote.
Yes. I think,
English users are => both Beginners + Advanced users
And
Most of the non-english users are => Beginners, while very few are
Advanced in my opinion
So, if we could have two different sections for Advanced (with detailed
information) and Beginner (with minimal end user oriented information)
users in the Release notes than end users will have the alternatives to
read. This will probably help the localizers too, to decide which
sections to translate.
>
> // Kris
>
> 2009/5/6 Dimitris Glezos <dimitris(a)glezos.com
> <mailto:dimitris@glezos.com>>
>
> 2009/5/6 Ruediger Landmann <r.landmann(a)redhat.com
> <mailto:r.landmann@redhat.com>>:
> > Noriko Mizumoto wrote:
> >> During today's FLP meeting, another idea came up to address
> this issue
> >> from l10n team side that is to break the file in small chunks.
> >> Could you kindly assess the feasibility and the scope of this idea?
> >>
> > As some of you know, Publican works with multiple small po files
> rather
> > than the one big po file that you're seeing at the moment. In
> fact, to
> > build the documents, the docs team has to break up the po files that
> > translators are contributing so that we can feed the multiple small
> > files back into Publican.
> >
> > On 29 April, Dimitris announced that Transifex 0.6 has support for
> > multiple po files in the same component and that Fedora's Transifex
> > instance will be updated to this version after Fedora 11 is out.
> You can
> > see a screenshot of this feature on the Transifex page here:
> > http://docs.transifex.org/releases/0.6.html (scroll down to
> "Multiple
> > files per language").
>
> Rudi, I think the translators are mostly worried that the document as
> a whole is large, not that the PO files themselves are large.
>
> The Q I have is: Should we continue pushing the big release notes, or
> should we consider either reducing their size or producing a compact
> version which will be more easy to translate and probably more
> compelling to our users as well, similar to eg. GNOME release notes?
>
> -d
>
>
> --
> Dimitris Glezos
> Jabber ID: glezos(a)jabber.org <mailto:glezos@jabber.org>, GPG:
> 0xA5A04C3B
> http://dimitris.glezos.com/
>
> "He who gives up functionality for ease of use
> loses both and deserves neither." (Anonymous)
> --
>
--
Regards,
Ankit Patel
http://www.indianoss.org/
14 years, 11 months
Pictures in the Installation Guide
by John J. McDonough
Volume 3 Number 2 of Linux+ magazine included Fedora 10 DVDs and an article
on installing Fedora. What was especially interesting about that article
was that it was mostly screenshots.
Of course, we all understand what a huge maintenance burden those
screenshots become for a product produced in umpteen languages. But for
some things, and I would argue especially the IG, they are a huge win.
The average person sees Linux as something kind of scary. It is too
complicated for "someone like me", especially the installation. I have
spoken to many people over the past year who would like to try Linux, but
are basically afraid.
Having all the installation steps laid out in front of you in living color
dramatically lowers that barrier. You can see every question, and you can
see that is isn't something you can't answer.
Perhaps it is biting off more than we can chew, but it seems like it has
great potential. One approach would be to somehow encourage magazines like
Linux+ to keep doing this, but that particular magazine is in English, and I
don't see any evidence it is produced in other languages. A lot of the
market is in places that don't speak English, so it would seem to be very
valuable to have the IG in particular full of pictures in the local
language.
Is this really nuts? Is there a lower priced way to approach this?
--McD
14 years, 11 months
Re: Release-note is long and hard for translating
by Ruediger Landmann
Dimitris Glezos wrote:
> 2009/5/6 Ruediger Landmann <r.landmann(a)redhat.com>:
>
>> Noriko Mizumoto wrote:
>>
>>> During today's FLP meeting, another idea came up to address this issue
>>> from l10n team side that is to break the file in small chunks.
>>> Could you kindly assess the feasibility and the scope of this idea?
>>>
>>>
>> As some of you know, Publican works with multiple small po files rather
>> than the one big po file that you're seeing at the moment. In fact, to
>> build the documents, the docs team has to break up the po files that
>> translators are contributing so that we can feed the multiple small
>> files back into Publican.
>>
>> On 29 April, Dimitris announced that Transifex 0.6 has support for
>> multiple po files in the same component and that Fedora's Transifex
>> instance will be updated to this version after Fedora 11 is out. You can
>> see a screenshot of this feature on the Transifex page here:
>> http://docs.transifex.org/releases/0.6.html (scroll down to "Multiple
>> files per language").
>>
>
> Rudi, I think the translators are mostly worried that the document as
> a whole is large, not that the PO files themselves are large.
>
Yes, I know that there's an issue there (although there are fewer new
strings in the F11 Release Notes than there were in the F10 Release
Notes), but the specific question here was about the possibility of
working with multiple small .po files rather than one gigantic one.
I can see that this question came up in the recent FLP meeting:
----
<tombolinux> huge docs make the translation impossible for little teams.
my team internally break big .pos in chunks...
<noriko> let's see anyway to break it into small chunks.
----
Am I right in thinking that Transifex 0.6 makes this possible? If so,
translators will be able to work with Publican's multiple small .po
files, and writers won't have to be merging these files together and
separating them again after translation... which should be good news for
everybody :)
> The Q I have is: Should we continue pushing the big release notes, or
> should we consider either reducing their size or producing a compact
> version which will be more easy to translate and probably more
> compelling to our users as well, similar to eg. GNOME release notes?
>
>
Discussion is already underway in docs about what form the Release Notes
should take for Fedora 12; you can see it on the agenda for this week's
meeting here:
http://fedoraproject.org/wiki/Docs_Project_meetings#Thursday_Apr_30_2009_...
as "Docs decisions for F12". Release Notes are the #1 issue amongst
these - see http://fedoraproject.org/wiki/Docs_decisions_for_F12
Cheers
Ruediger
14 years, 11 months
Guides Page
by Eric Christensen
I've created a guide page[1] on the wiki that shows all the guides
that we are currently supporting. My plan is to include a list of all
the guides, a brief introduction paragraph, a sentence that tells
people how they can become involved, and where they can find the guide
(html, pdf, RPM, etc).
Please visit the page and provide that information on your guide.
[1] https://fedoraproject.org/wiki/Docs_Project_guides
Thanks,
Eric
14 years, 11 months
Re: Docs focus after F11 release
by Zach Oglesby
I think this is also a topic for this weeks docs meeting. This is my first
release with docs but it would seem normal to have a big amount of resources
taken as we near release.
Zach Oglesby
GPG Key - 1378F79F
http://fedoraproject.org/wiki/User:Zoglesby
On May 3, 2009 6:39 PM, "David Nalley" <david.nalley(a)fedoraproject.org>
wrote:
On Sun, May 3, 2009 at 12:13 PM, Karsten Wade <kwade(a)redhat.com> wrote: >
Paul and I were talking th...
I think this hit the mailing list, as I think I replied to it trying
to encourage a docs FAD at SELF on June 14th.
--
fedora-docs-list mailing list
fedora-docs-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-docs-list
14 years, 11 months
Docs focus after F11 release
by Karsten Wade
Paul and I were talking the other day, very impressed with the quality
and quantity of people focused on producing so much good content for
F11. Our only concern was the risk of myopia, that is, too near of a
focus on F11 and losing site of what comes afterward. We've
experienced this, where after a release we drift like sand on the
boardwalk.
Then I saw this link on IRC:
https://fedoraproject.org/wiki/Docs_decisions_for_F12
I didn't see anything in the mailing list discussing this, so I wanted
to start the thread. :)
That page has a bunch of good stuff on it. Anything missing? Any
ideas about the topics there?
- Karsten
--
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
14 years, 11 months
Re: Pictures in the Installation Guide
by A. Mani
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ruediger Landmann <r.landmann(a)redhat.com> wrote:
>
> The bad news is that there's no easy way to maintain these. Every time
> L10N volunteers add another language, screenshots must be taken anew;
> and every time an installation step changes, we need new screenshots in
> 36 languages. Also, the screens contain version-specific artwork,
> meaning that in a perfect world we would have to create a whole new set
> with every Fedora release. I wasn't planning to do that though; and was
> only planning to revise "version-obvious" screenshots like the Welcome
> screen between versions. Note too that the Installation screen artwork
> for F11 is not present in the PR and that we might need to talk to the
> artwork team to get this moved up in the schedule in future versions.
>
I think instead of actual screen shots, we should consider high
quality mock ups using
latex + ps/pdf tricks or just *xml or some other mark up. This way
localisation would not be a problem.
Chapter 9 on Boot Options can as well include the table of options
supported by Anaconda.
Best
A. Mani
--
A. Mani
ASL, CLC, AMS, CMS
http://amani.topcities.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkn82QgACgkQunMISzvdfU6wdQCgsx/pEiyPhRNvZHttMOaBTPa5
US4An0A2rgp2oXdoXPw+YR6a+FYHN3yl
=ouLk
-----END PGP SIGNATURE-----
14 years, 11 months
Re: #1: Make builds work
by Fedora Release Notes
#1: Make builds work
-----------------------+----------------------------------------------------
Reporter: pfrields | Owner: pfrields
Type: task | Status: closed
Priority: major | Milestone: publican-ready
Component: General | Version: 9.91
Resolution: fixed | Keywords:
-----------------------+----------------------------------------------------
Changes (by pfrields):
* status: assigned => closed
* resolution: => fixed
Comment:
I believe the master branch works fine with Publican now, thanks to the
efforts of rlandmann, jjmcd, and others.
--
Ticket URL: <https://fedorahosted.org/release-notes/ticket/1#comment:3>
Fedora Release Notes <https://fedorahosted.org/release-notes/>
Fedora Release Notes
14 years, 11 months
[Fedora Release Notes] #29: Remove whitespace trigger ugly PDF formatting
by fedora-badges
#29: Remove whitespace trigger ugly PDF formatting
---------------------+------------------------------------------------------
Reporter: quaid | Owner: quaid
Type: task | Status: new
Priority: major | Milestone: RC-ready
Component: Content | Version: 10
Keywords: |
---------------------+------------------------------------------------------
Just in case we cannot get this fixed in the PDF toolchain, we need to
remove all the leading whitespace for tags that display CDATA or other
content verbatim.
This could be done as part of a general run of a tool such as docbook-lint
or xmlformat. Before doing that, we need to assess the risk of the tool
chaining line numbers and causing translation stats to go fuzzy.
--
Ticket URL: <https://fedorahosted.org/release-notes/ticket/29>
Fedora Release Notes <https://fedorahosted.org/release-notes/>
Fedora Release Notes
14 years, 11 months