April 2007 - docs - Fedora Mailing-Lists

Re: DocsProject common entities -- problem with translations?

by Igor Miletic

On Thu, 2007-04-05 at 15:22 -0400, Paul W. Frields wrote: > So it sounds like we will have annoyances no matter which choice we > make: > > 1. Using "xml2po -k" and keeping entities intact like &NAME; there are > translators who will be inconvenienced. They can still substitute > translations for the entity -- using the right form of "SomeName," > instead of the exact string "&NAME;" -- but there will be no benefit to > them in the event the entity changes. They may not even notice that it > *has* changed unless they are watching the > docs-common/common/entities/po/entities.pot file, and making the mental > connection. > > 2. Using "xml2po -e" and transforming the entities into strings in the > POT file, so "&NAME;" becomes "SomeName," it will be painful to change > single strings in a minor way, since *many* fuzzy entries potentially > result from trivial changes. > > We can revert to behavior #2, and I can get this into the POTs for > important modules now. I would like opinions within the next 24 hours. Vote for "-e" here, if entities are left "as is". However, if entities are only version numbers, files and possibly trademarks ("Fedora" and "Red Hat Inc."), I could support "-k" as well (as long it does not include name of projects). Regards, Igor

17 years

1
0
0 / 0

Re: homepage/devel/po el.po, 1.4, 1.5 es.po, 1.4, 1.5 homepage.pot, 1.6, 1.7 it.po, 1.6, 1.7 pl.po, 1.9, 1.10 pt.po, 1.7, 1.8 pt_BR.po, 1.6, 1.7 ru.po, 1.3, 1.4 sr.po, 1.1, 1.2 sv.po, 1.4, 1.5 uk.po, 1.3, 1.4 zh_CN.po, 1.4, 1.5

by Igor Miletic

On Wed, 2007-04-04 at 16:38 -0400, Paul W. Frields wrote: > Author: pfrields > > Update of /cvs/docs/homepage/devel/po > In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3652/po > > Modified Files: > el.po es.po homepage.pot it.po pl.po pt.po pt_BR.po ru.po > sr.po sv.po uk.po zh_CN.po > Log Message: > Update POT and PO adding franais to the locales > > #. Next para does not need to be translated. > #: en_US/homepage.xml:20(para) > +#, fuzzy > msgid "" > "<ulink url=\"index-pt_BR.html\">portugus brasileiro</ulink>, <ulink > url=" > -"\"index-el.html\"></ulink>, <ulink url=\"index-it.html\">italiano</" > -"ulink>, <ulink url=\"index-pl.html\">Polski</ulink>, <ulink url= > \"index-pt." > -"html\">portugus</ulink>, <ulink url=\"index-ru.html\">Pycc</ulink>, > " > -"<ulink url=\"index-zh_CN.html\"></ulink>, <ulink url= > \"index-es.html" > -"\">Espaol</ulink>, <ulink url=\"index-sv.html\">svenska</ulink>, and > <ulink " > -"url=\"index-en_US.html\">US English</ulink>." > +"\"index-el.html\"></ulink>, <ulink url=\"index-fr.html\">franais</" > +"ulink>, <ulink url=\"index-it.html\">italiano</ulink>, <ulink url= > \"index-pl." > +"html\">polski</ulink>, <ulink url=\"index-pt.html > \">portugus</ulink>, " > +"<ulink url=\"index-ru.html\">Pycc</ulink>, <ulink url= > \"index-zh_CN.html" > +"\"></ulink>, <ulink url=\"index-es.html\">Espaol</ulink>, <ulink " > +"url=\"index-sv.html\">svenska</ulink>, and <ulink url= > \"index-en_US.html" > +"\">US English</ulink>." > msgstr "" > "<ulink url=\"index-pt_BR.html\">portugus brasileiro</ulink>, <ulink > url=" > "\"index-el.html\"></ulink>, <ulink url=\"index-it.html\">italiano</" > @@ -98,37 +104,47 @@ > "\">Espaol</ulink>, <ulink url=\"index-sv.html\">svenska</ulink>, > <ulink " > "url=\"index-en_US.html\">US English</ulink>." > Can you add Serbian too: <ulink url=\"index-sr.html\">српски</ulink> ? Regards, Igor

17 years

1
0
0 / 0

Re: homepage/devel/en_US homepage.xml,1.8,1.9

by "Piotr \"Raven\" Drąg"

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul W. Frields (pfrields) napisał(a): >  > <para><ulink url="index-pt_BR.html">portuguÃªs brasileiro</ulink>, > <ulink url="index-el.html">Î•Î»Î»Î·Î½Î¹ÎºÎ¬</ulink>, <ulink > - url="index-fr.html">French</ulink>, <ulink > + url="index-fr.html">franÃ§ais</ulink>, <ulink > url="index-it.html">italiano</ulink>, <ulink > url="index-pl.html">polski</ulink>, <ulink > url="index-pt.html">portuguÃªs</ulink>, <ulink > @@ -46,6 +46,7 @@ > <para><ulink url="RELEASE-NOTES-pt_BR.html">portuguÃªs > brasileiro</ulink>, <ulink > url="RELEASE-NOTES-el.html">Î•Î»Î»Î·Î½Î¹ÎºÎ¬</ulink>, <ulink > + url="RELEASE-NOTES-fr.html">franÃ§ais</ulink>, <ulink > url="RELEASE-NOTES-it.html">italiano</ulink>, <ulink > url="RELEASE-NOTES-pl.html">Polski</ulink>, <ulink ^^^^^^ It looks like it's not only in one place... :( - -- Piotr "Raven" Drąg http://raven.pmail.pl/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGFA1bjBBsaE0M6qkRAufcAJoCju3OTV9sB0luzuQZXl0eriiBSgCgtNTj 7mo7bxpF1S1UO70XhGh0iG4= =24W/ -----END PGP SIGNATURE-----

17 years

1
0
0 / 0

Wiki work needed

by Paul W. Frields

Can anyone accept the following mission: 11:12:01 < f13> stickster_work: I'm going to be lame and point out a wiki page that needs editing, but without doing it myself or providing content for you :/ 11:12:54 < f13> stickster_work: http://fedoraproject.org/wiki/HelpWanted this page doesn't seem to reflect the core/extras merger stuff, nor the wiki changes mether did around organizing Fedora Packagers and such at http://fedoraproject.org/wiki/PackageMaintainers Would someone like to take the task of fixing the HelpWanted page to agree with Rahul's recent edits at PackageMaintainers? The objective is to properly portray the package collection as being unified rather than split into Core and Extras. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Project: http://fedoraproject.org/wiki/PaulWFrields irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

17 years

3
3
0 / 0

Re: homepage/devel/en_US homepage.xml,1.6,1.7

by "Piotr \"Raven\" Drąg"

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Karsten Wade (kwade) napisał(a): > <para>This page is available in the following languages:</para> >  > <para><ulink url="index-pt_BR.html">portuguÃªs brasileiro</ulink>, > - <ulink url="index-el.html">Î•Î»Î»Î·Î½Î¹ÎºÎ¬</ulink>, <ulink > + <ulink url="index-el.html">Î•Î»Î»Î·Î½Î¹ÎºÎ¬</ulink>, <ulink > + url="index-fr.html">French</ulink>, <ulink > url="index-it.html">italiano</ulink>, <ulink > url="index-pl.html">Polski</ulink>, <ulink > It should be "polski", not "Polski" (like "italiano" above). - -- Piotr Drąg http://raven.pmail.pl/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGE+RtjBBsaE0M6qkRAo5HAJ9OnRvYFU0GIYb0UuswdrC+IR+woQCfZPmR vVd34Upw0Qn5dlq/suV9M3c= =EpOt -----END PGP SIGNATURE-----

17 years

2
1
0 / 0

Release Notes for F7test4 - POT available

by Paul W. Frields

The POT for Release Notes for F7test4 is now available for translators in the Fedora Docs CVS. For instructions, please refer to the Translation Quick Start Guide¹, Chapter 4, "Translating Documentation." Please make sure you apply for cvsdocs access to be able to commit your translations! ** The deadline for PO files is 2359 UTC, April 14th 2007.² ** The module is available here: $ cvs -d :ext:<username>@cvs.fedoraproject.org:/cvs/docs co release-notes-devel Please test your translations for validity by running "make validate-xml-<LANG>" when finished. If you have specific problems with the output, you can get help from the Fedora Documentation Project either on fedora-docs-list(a)redhat.com or on IRC Freenode in channel #fedora-docs. The following PO files have been created so far³: ca cs da de el es fi fr gu hr it ja ml ms nb nl pa pl pt_BR pt ru sr@Latn sr sv ta uk zh_CN zh_TW If you translate another language, you can follow the instructions in the document above to add a new language to the list. Thank you for your time and efforts! = = = = = ¹ http://docs.fedoraproject.org/translation-quick-start-guide/ ² http://fedoraproject.org/wiki/DocsProject/Schedule ³ The following languages need to have common entity PO files created before any documents can be built in those languages: ca cs fi gu hr ml ms nb sr@Latn ta zh_TW -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Project: http://fedoraproject.org/wiki/PaulWFrields irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

17 years

1
0
0 / 0

Heading styles

by Jonathan Roberts

Hi, sorry I'm sending *so* many mails to the list! Possible addition to the style guidelines would be that headings/titles should either be *all* capitalized, i.e. Cool Things To Do With Fedora, or first capital and then all lower case, i.e. Cool things to do with Fedora. Some documents currently have headings which look like "Cool Things To Do with Fedora" - the random use of capitals/lowercase is ugly, imho! Yours, Jon

17 years

3
4
0 / 0

Question about the translation process of fedora 7 relnotes

by Yuan Yijun

Hi, I have some question about translation process. Vmlinuz may going to translate it. * What is the CVS url for fedora 7 relnotes? * What group should translator have in the fedora account system? * How to begin translation, I cannot find RELEASE-NOTES on fedora i18n status page, so how can I "TAKE" it? I rememberred for fc6 relnotes it was here: http://i18n.redhat.com/cgi-bin/i18n-status?page=status&branch=HEAD&locale... * How to notify the others that I'm translating it? * When will POT file get ready, will there be any email notifications? * Do I need to modify "Makefile" and run "make xxxxx" to generate zh_CN.po as before? Thanks! -- bbbush ^_^

17 years

2
1
0 / 0

readme-burning-isos - suggested changes

by Development discussions related to Fedora

Hi, Had a look over the above document on the F7t3 dvd iso, and felt it could use some additions {other than FC6 -> F7} which seems to be handled by some macros. http://cvs.fedora.redhat.com/viewcvs/ readme-burning-isos/devel/en_US/README-BURNING-ISOS.xml?root=docs&rev=1.3&view=markup I'm not part of the cvsl10n group so if the cvs tree is still open before translation begins perhaps someone can check and commit ;) {I couldn't find the doc anywhere on the wiki, so assuming it's a cvs thing}. DaveT.

17 years

1
0
0 / 0

want to mentor a GSoC project?

by Karsten Wade

We have several projects that have proposals in the Google Summer of Code. Right now, it looks as if we'll get three projects working this summer. Maybe four. Obviously that's too many for just one person to mentor. So this is your lucky chance! Aside from helping make a project happen, mentors get a GSoC t-shirt, and a chance at other goodies. Last year, I got to attend the Mentors Summit with mentors from all over the world, and we met at the famous Google campus in Mountain View. If you are interested, contact myself and Patrick Barnes. You'll also need to apply to be a mentor for The Fedora Project via: http://code.google.com/soc/mentor_home.html You need to do this right away, so you can help with the proposal selection process. During this process, mentors work with students on their active proposals, to work out which ones are accepted. cheers - Karsten -- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

17 years

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs April 2007