-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Guys, Our Anaconda Slide rendering environment is near to be functional, so I'm wondering if you'd like to add new slides and if translators could take a look at the translations we have now ? Actually we have two Slide designs to choose from: 1. The common Title, Content slides [1]. 2. The common Title, Content slides plus related icon [2]. Both Slides use the same translation files. Anaconda translation files are organized by CentOS versions. This way we could have different slides, with probably different texts (due specific version technical characteristics) for each CentOS major version/release. All Anaconda translation files[3] are in our subversion artwork repository, available for you to checkout. Translators wanting to help should download a working copy of the language directory they want to update and then commit the changes back into the subversion repository (remember to do a svn update before committing changes). Slides images will be built using those translations. [1] https://projects.centos.org/trac/artwork/browser/trunk/Themes/TreeFlower/Anaconda/Progress/Slides-1/img/en/anaconda-01-welcome.png [2] https://projects.centos.org/trac/artwork/browser/trunk/Themes/TreeFlower/Anaconda/Progress/Slides-2/img/en/anaconda-01-welcome.png [3] For CentOS-6: https://projects.centos.org/trac/artwork/browser/trunk/Translations/6/Themes/Anaconda/Progress For CentOS-5: https://projects.centos.org/trac/artwork/browser/trunk/Translations/5/Themes/Anaconda/Progress Best Regards, - -- Alain Reguera Delgado <al at ciget.cienfuegos.cu> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFJY8uayXxCQEoXDZARAs/xAJ4iybMrkIqckKgNV+TNc4G7j2tcrQCgr2O/ liTTvbiYyoIyvwaCvdDn8sw=D7+v -----END PGP SIGNATURE-----
On 01/06/2009 11:22 PM, Alain Reguera Delgado wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Guys, > > Our Anaconda Slide rendering environment is near to be functional, so > I'm wondering if you'd like to add new slides and if translators could > take a look at the translations we have now ? > >yummy...> For CentOS-5: > https://projects.centos.org/trac/artwork/browser/trunk/Translations/5/Themes/Anaconda/Progress > >https://projects.centos.org/trac/artwork/browser/trunk/Translations/5/Themes/Anaconda/Progress returns Internal Error No node /trunk/Translations/5/Themes/Anaconda/Progress at revision 443 You can search <https://projects.centos.org/trac/artwork/log/trunk/Translations/5/Themes/Anaconda/Progress?rev=443&mode=path_history> in the repository history to see if that path existed but was later removed. TracGuide <https://projects.centos.org/trac/artwork/wiki/TracGuide> ? The Trac User and Administration Guide
bulmoji-centos at yahoo.com
2009-Jan-07 01:52 UTC
[CentOS-docs] 답장: Anaconda Slides Translations
> Translators wanting to help should download a working copy > of the > language directory they want to update and then commit the > changes back > into the subversion repository (remember to do a svn update > before > committing changes). Slides images will be built using > those translations.Hello, I want to help making Korean translation but it seems there is no Korean directory. Would tell me how to? Truly, YoungHoon Park ________________________________________________________ 180? ??? ??! ?? - ??? ??! ??? ??! ??? 10?? ?? ??? ? ???? ??????. http://kr.content.mail.yahoo.com/cgland
Hello
While playing around I have noticed that both files below
https://projects.centos.org/trac/artwork/browser/trunk/Translations/5/Themes/Anaconda/Progress/First/
include the following line:
s!=VERSION=!6!
Is it intended ? Shouldn't there be a 5 instead of 6?
> [...] > [3] > For CentOS-6: > https://projects.centos.org/trac/artwork/browser/trunk/Translations/6/Themes/Anaconda/Progress > For CentOS-5: > https://projects.centos.org/trac/artwork/browser/trunk/Translations/5/Themes/Anaconda/Progress > >Hello. I guess I need a bit of help again: Updating the C5 tree worked the other day, but I cannot do it in the C6 tree: [wolfy at wolfy 6]$ pwd /tmp/anaconda-slides/6 [wolfy at wolfy 6]$ ls en ro [wolfy at wolfy 6]$ svn commit ro -m 'Initial Romanian Translation' Sending ro/anaconda-04-repos.sed svn: Commit failed (details follow): svn: CHECKOUT of '/svn/artwork/!svn/ver/499/trunk/Translations/6/Themes/Anaconda/Progress/Slides-1/ro/anaconda-04-repos.sed': 403 Forbidden (https://projects.centos.org) Did I miss something ? (I did try to specify explicitely the user and password, but the error message was identical)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 bulmoji-centos at yahoo.com wrote:> Hello, > > Would somebody tell me what encoding shoud be used for Korean translation file? > > Is UTF-8 encoding acceptable?I think it is. Could you try it to see how they look after rendering ? Cheers, - -- Alain Reguera Delgado <al at ciget.cienfuegos.cu> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFJa0nzyXxCQEoXDZARAj+bAJ96lOoNM345tNbBlFOGj8RyHqKlpgCgvlbT p0LtQxa1jMs5tosesZt1Eq4=wKe1 -----END PGP SIGNATURE-----
I tried to update the files in https://projects.centos.org/svn/artwork/trunk/Translations/6/Themes/Anaconda/Progress/Slides-1/pt/ and got no access. How could I update these files? Thanks, On Mon, Jan 12, 2009 at 11:47 AM, Alain Reguera Delgado <al at ciget.cienfuegos.cu> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > bulmoji-centos at yahoo.com wrote: >> Hello, >> >> Would somebody tell me what encoding shoud be used for Korean translation file? >> >> Is UTF-8 encoding acceptable? > > I think it is. Could you try it to see how they look after rendering ? > > Cheers, > - -- > Alain Reguera Delgado <al at ciget.cienfuegos.cu> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org > > iD8DBQFJa0nzyXxCQEoXDZARAj+bAJ96lOoNM345tNbBlFOGj8RyHqKlpgCgvlbT > p0LtQxa1jMs5tosesZt1Eq4> =wKe1 > -----END PGP SIGNATURE----- > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs >-- Cleber Paiva de Souza
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Akemi Yagi wrote:> Alain, > > I have done the ja translation. When I tested rendering locally, they > looked ok. Could you try commiting them so that I can confirm the > images are fine there as well?Well, ja translations are not well interpreted in my terminal either. Something similar to Korean language is happening. Surely if you commit them directly from your system they will look correctly. Best Regards, - -- Alain Reguera Delgado <al at ciget.cienfuegos.cu> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFJde0zyXxCQEoXDZARAuTxAKDfAbYUSNZA2wJspiVvvEYMjIshqQCfcTOL D3jQXZZirMSufD+gaDqiGHM=rgc5 -----END PGP SIGNATURE-----
On Tue, Jan 20, 2009 at 7:26 AM, Alain Reguera Delgado <al at ciget.cienfuegos.cu> wrote:> Akemi Yagi wrote: >> Alain, >> >> I have done the ja translation. When I tested rendering locally, they >> looked ok. Could you try commiting them so that I can confirm the >> images are fine there as well? > > Well, ja translations are not well interpreted in my terminal either. > Something similar to Korean language is happening. Surely if you commit > them directly from your system they will look correctly.Am I supposed to be able to do it myself (commit them directly from my system) ? I will try it again later today. Akemi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Akemi Yagi wrote: ...> Am I supposed to be able to do it myself (commit them directly from my > system) ?Yes, why not ? :) I would like to promote the following idea: - --- Text translations, and image rendering for CentOS Slides is something that everybody can do in its own system (in a not so difficult way). Just 3 steps: 1. Get your working copy from our svn artwork repository [1]. 2. Do your changes ( Translations / Rendering [2] ) 3. Commit your changes to make them available. - --- To get commit access an account in https://projects.centos.org/trac/artwork/ is needed. After that, show your trac user and request the commit access in this mailing list. [1] https://projects.centos.org/svn/artwork/ [2] needs to have Inkscape already installed in the system. Best Regards, - -- Alain Reguera Delgado <al at ciget.cienfuegos.cu> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFJdjs1yXxCQEoXDZARAtiuAKDEz/xJEEQpf9aE2jeddTIEiv5gwACg0pJG 7LI7Kdqx3TgjomzEgGMWrUI=HeBI -----END PGP SIGNATURE-----
On Tue, Jan 20, 2009 at 12:59 PM, Alain Reguera Delgado <al at ciget.cienfuegos.cu> wrote:> Akemi Yagi wrote: > ... >> Am I supposed to be able to do it myself (commit them directly from my >> system) ? > > Yes, why not ? :)Let me explain in more details the "problem" I am having because I failed to do so in my original message. I edited the .sed files and committed them without any issue. I presume you have seen them on the server. By the way, they do not display correctly even in my browser. I also rendered images locally and confirmed that the *text* in the rendered images looked just fine. However, the problem I have is that those images did not have the background image. The error I got during the rendering was: ** (inkscape:8096): WARNING **: <image xlink:href="/home/al/Desktop/CentOS/artwork/trunk/Themes/TreeFlower/Wallpapers/img/wallpaper-fog.png"> did not resolve to a valid image file (base dir is /home/yagi2/centos/slides/Slides-1), now trying sodipodi:absref="/home/al/Desktop/CentOS/artwork/trunk/Themes/TreeFlower/Wallpapers/img/wallpaper-fog.png" ** (inkscape:8096): WARNING **: Unable to open linked file: /home/al/Desktop/CentOS/artwork/trunk/Themes/TreeFlower/Wallpapers/img/wallpaper-fog.png At that point I thought I should ask you to do the rendering step because the .sed files on the server are correct even if they do not display in the browser. I would like to be able to render locally. I must be missing something simple. Could you help? Akemi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Akemi Yagi wrote: ...> After some trial and error sessions, I now know that the "/" on the > TEXT line causes the rendering to fail (this is ja). Only slide 06 > has them, which is why this one did not render. > > Is there any known workaround? Some way to escape?Try it with another separator: s!=TEXT1=!wiki url: http://wiki.centos.org/! s#=TEXT2=#<flowSpan style="font-weight:bold">Bold Text</flowSpan># s/=TEXT3=/Simple text. No slashes here in/ Best Regards, - -- Alain Reguera Delgado <al at ciget.cienfuegos.cu> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFJeNavyXxCQEoXDZARAjLZAJ9iDFE72jpP3hbzPCTJEY8uCjb8CgCfT7nT TAjWF9B3skVYErc1MMZ/SgY=aO1S -----END PGP SIGNATURE-----
On Thu, Jan 22, 2009 at 12:27 PM, Alain Reguera Delgado <al at ciget.cienfuegos.cu> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Akemi Yagi wrote: > ... >> After some trial and error sessions, I now know that the "/" on the >> TEXT line causes the rendering to fail (this is ja). Only slide 06 >> has them, which is why this one did not render. >> >> Is there any known workaround? Some way to escape? > > Try it with another separator: > > s!=TEXT1=!wiki url: http://wiki.centos.org/! > > s#=TEXT2=#<flowSpan style="font-weight:bold">Bold Text</flowSpan># > > s/=TEXT3=/Simple text. No slashes here in/I tried the first one (!) and it worked. The rendering is complete. Akemi