trans October 2008

trans@lists.fedoraproject.org

52 participants
75 discussions

500 error when submitting paprefs
by Miloš Komarčević 08 Oct '08

08 Oct '08

Cannot commit translations for paprefs, just got the good old 500 internal error... Problems with non-ASCII user names again? Miloš

3 7

Fwd: FUEL: An initiative in language standardization via collaboration
by Rajesh Ranjan 08 Oct '08

08 Oct '08

---------- Forwarded message ---------- From: Rahul Sundaram <sundaram(a)fedoraproject.org> Date: 2008/10/7 Subject: FUEL: An initiative in language standardization via collaboration To: For discussions about marketing and expanding the Fedora user base < fedora-marketing-list(a)redhat.com> Hi, http://www.linux.com/feature/149038 "FUEL (Frequently Used Entries for Localization) aims to solve the problem of inconsistency and lack of standardization in computer software translation in a new and unique way. Initiated by Red Hat, the project is trying to give a better experience to end users of a localized desktop by resolving the issues of standardization and inconsistency." "FUEL is an attempt to standardize terms for the whole desktop instead of concentrating on different applications separately. At present, FUEL incorporates representative entries from the GNOME desktop, OpenOffice.org, Firefox browser, Evolution email client, and Pidgin instant messenger, so that it can have at least all the entries that a normal user uses very frequently. Later, on demand from communities, FUEL can incorporate more applications in its list from different projects." Rahul -- Fedora-marketing-list mailing list Fedora-marketing-list(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-marketing-list -- Regards, Rajesh Ranjan www.kramashah.blogspot.com

2 1

Re: F10 Schedule Revised
by Paul W. Frields 07 Oct '08

07 Oct '08

On Tue, 2008-10-07 at 00:06 -0400, Jon Stanley wrote: > On Fri, Oct 3, 2008 at 11:37 AM, Paul W. Frields <stickster(a)gmail.com> wrote: > > > even with only 3 people I think Fedora Talk held us back at times. > > Sorry for the tangent here - but in what way did it hold you back? I'm > really interested, Not for technical reasons -- it was more that conference calls that are essentially, "Let's all do <XXXX>," suffer from everyone talking at once too much. (And I point that finger *firmly* at myself first and foremost.) IRC is lower bandwidth but when everyone is doing something at once, communication is *easier* to interleave that way. For more orderly meetings, IRC can be less effective -- not always, but sometimes. -- Paul W. Frields gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://paul.frields.org/ - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

1 0

[Bug 465695] New: Smolt - web client
by Red Hat Bugzilla 07 Oct '08

07 Oct '08

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Smolt - web client https://bugzilla.redhat.com/show_bug.cgi?id=465695 Summary: Smolt - web client Product: Fedora Localization Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: medium Component: l10n-requests AssignedTo: dimitris(a)glezos.com ReportedBy: loupgaroublond(a)gmail.com QAContact: aalam(a)redhat.com CC: fedora-trans-list(a)redhat.com Classification: Fedora Module smoon Description smoon is the website front end to the smolt data Project webpage http://smolts.org/ http://smolt.fedorahosted.org/ VCS root, module, branch http://git.fedorahosted.org/git/smolt.git File filter (eg. <code>.*/po/.*</code>) /smoon/locales/* Note: we use the split directory folder that is parsable by gettext, not the flat directory for development. This is due to an inherent limitation in Turbogears. If you need this to be in any other format, let me know so I can hack something together. Changelog file (if applicable) Web front-end to VCS http://git.fedorahosted.org/git/smolt.git -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

Where is module virt-manager?
by Xavi Conde 06 Oct '08

06 Oct '08

Hi, I was going to send the translation of virt-manager module when I noticed that it is not listed anymore in https://translate.fedoraproject.org/module/. Do you know how can I commit the translation? Thanks in advance! -- HAL I am putting myself to the fullest possible use, which is all I think that any conscious entity can ever hope to do. + Google talk/Jabber: xavi.conde a gmail.com

4 4

121% translated
by Göran Uddeborg 06 Oct '08

06 Oct '08

At http://translate.fedoraproject.org/languages/sv/fedora-10 the package libuser is currently 121% translated. Anyone can beat that? :-)

3 2

Re: New language codes?
by Asgeir Frimannsson 05 Oct '08

05 Oct '08

----- "Asgeir Frimannsson" <asgeirf(a)redhat.com> wrote: > ----- "Piotr Drąg" <piotrdrag(a)gmail.com> wrote: > > > Asgeir Frimannsson pisze: > > > Here are the proposed renames. I'm not an expert, and some codes > > would make more sense without a country-qualifier I guess (country > > qualifier is ISO-wise optional). > > > > > > pl -> pl-PL > > > > > > > Doesn't make ANY sense, because Polish is spoken only in one > country. > > I > > believe there are more situations like this on the list... > > I totally agree :) same for e.g. Norwegian like nb-NO and nn-NO. > > However, until we have a proper fix in publican (or have confirmed > that nothing breaks without country-qualifiers [except translation > statistics]), I think it's better to live with it for now. I am not > proposing this as a permanent solution. Just to clear up any confusion: No, we are not planning on changing the language codes by adding country qualifiers. This was just an attempt to make the documentation build in publican, which seemed to have a rather unjustified 'preference' of LANG-COUNTRY style codes. We have confirmed that simple LANG codes doesn't break anything (except generating translation reports - which is now fixed upstream), and hence any changes as proposed in the earlier emails were never committed. What we *might* do at some point is change the way we represent codes to conform to RFC3066, i.e. en_US -> en-US and sr_Latn to sr-Latn. cheers, asgeir

2 1

New language codes?
by Paul W. Frields 03 Oct '08

03 Oct '08

If the Docs Project is able to complete a transition to Publican for the release notes for Fedora 10, many of our language codes will change to ISO standards. This includes moving from en_US to en-US, as in "Release_Notes-en-US.txt". It would probably be good if any tools used to spin or release the distribution get updated to support both of these options. I would suggest shifting them to use the ISO standard, en-US, first and the try falling back to en_US. That way, if we fail utterly and have to drop back to the old way of doing business, the results will still land properly. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

11 13

FLP Meeting 2008-09-30 IRC Log
by Dimitris Glezos 03 Oct '08

03 Oct '08

We had a quick meeting the other day, here's the log. <glezos_> Rasther, vpv, marek, rest: Let's have a quick one, I can chair <glezos_> <meeting> <glezos_> Here's the summary from the previous meeting: https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00051.h… <glezos_> Schedule: <glezos_> OK, FLSCo communicated with all the necessary parties and <glezos_> the schedule has been updated to include one week for package rebuilding. <glezos_> I had a meeting with poelcat and we made clear for most schedule tasks what's needed, etc. <glezos_> Soon the Fedora L10n project will have its own schedule, with all the important dates on it. <glezos_> I think it'll be awesome. <glezos_> The mail for the string freeze and deadline move was sent to all related lists. <glezos_> - Haven't heard of any volunteers for the script to check rebuilds. <glezos_> The second TODO has been done too, I have asked Releng to include L10n in their freeze emails, to avoid having another one sent. <glezos_> - Fedora Docs in Rh-internally-supported languages: AFAIK the process continues normally. I hope this project will make it into succession. <glezos_> um <glezos_> *success. <ln-> d'ogh, i tested the F10 Beta Live CD a minute ago, and it seems the keyboard layout selection has no effect. <glezos_> ln-: bug report. <glezos_> Also, the Beta Release Meeting took place last week, and I've notified the rest of the project Leaders for L10n's requirements. <glezos_> Oh, (IMO) Runa (mishti) is doing a great job with FWN. * glezos_ raises a glass <ln-> already kind of reported, it seems: https://bugzilla.redhat.com/show_bug.cgi?id=464825 <glezos_> - Docs move: We're having issues with the Publican format. <glezos_> AFAIK Docs would like to move to publican for F10 <glezos_> I think asgeirf is working on that, which is great, otherwise F10 Docs would have serious (maybe show-stopper) problems in L10n. * glezos_ looking forward to a quick solution to make both Publican and L10n possible. * glezos_ covered most things he'd like <glezos_> in monologue :( <vpv> glezos_: any details about the publican problem, bugzilla or something? <glezos_> vpv: um.. the only 'problem' is that nothing in our toolchain supports it, <Rasther> vpv: https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00108.h… <vpv> ok, thanks <vpv> (haven't been following the mailing list too closely lately) <glezos_> any other comments? (open floor) <zebob> could we talk about cvsl10n sponsoring ? <glezos_> zebob: sure, what's up? <Rasther> We are having other issues with DL, but it was reported already.. <glezos_> Rasther: you're working on fixing stats, right? :P <Rasther> ricky was taking a look early, not sure if it was fixed <zebob> in the french team we've got some people (sponsored of course) who commit translation but we don't know them <zebob> they never show up on the ml for example <glezos_> zebob: what can we do about that? <zebob> maybe this is not the right place to talk aout that <Rasther> glezos_: I'm trying... <Rasther> zebob: why not? go ahead! :) <zebob> the sponsoring process sucks a bit, sponsoring should be under the responsability of team coordinator for a particular lang <ricky> glezos_: I had no luck, feel free to take a stab <zebob> actually we've got people we don't even know making translations (often duplicate of our team work) and this work doesn't follow our QA * glezos_ a bit away <glezos_> zebob: hmm. This is probably a good discussion on the mailing list. <Rasther> ricky: was it not a balance problem? <glezos_> zebob: feel free to provide suggestions on how to <glezos_> on how to fix the process. If it's producing not optimal results, we should fix it. <ricky> Rasther: It might be something wrong with just app1 or app2, but I didn't find anything useful in the traceback or the apache logs <zebob> glezos_, sorry but which ml ? l10n or i18n <glezos_> zebob: I think it's not possible right now with the current FAS. Here's a plan: <glezos_> On TQSG we have mentioned that the new user should put on the ocmment field what lang he'd like to translate to <Rasther> ricky: :( <glezos_> so we could agree among sponsors that if someone is registering for French, leave it to the French coordinator <glezos_> zebob: do you guys have a sponsor? <zebob> me <zebob> well thanks <glezos_> zebob: so the problem is mainly submissions <glezos_> right? <glezos_> commits, I mean <zebob> the problem is we don't know those people <zebob> yes commit by unknow people <zebob> which conflicts with our workflow <glezos_> zebob: ok. Here's a (big) suggestion then: <glezos_> This can be solved in Tx then.. <glezos_> At some point (soon I think) we'll adding workflow support. <glezos_> We can make sure we solve it in a way that will help you guys with this. For example, translation maintainers of certain projects could "allow" transltaions from particular peiple <zebob> I hope so, but Tx dev is far far away from fp.o point of view :) <glezos_> zebob: We're open to any suggestions. <glezos_> Let's take this on list and transifex-devel (or IRC #transifex) * glezos_ needs to go <zebob> glezos_, Asgeir already have all my suggestions:) <zebob> just another quick question : does people from redhat.com have the « right » to supersede ours translations ? <glezos_> zebob: no. <zebob> Can we shout at them then ? :) <zebob> good night, and thanks for answering o/ <glezos_> zebob: Fedora is a community project. Bottom line, the project maintainer has the final say on who is responsible for translations. <zebob> ok <Rasther> for now: I guess we could notify the cvsl10n sponsors for only give access for users that are from their specific lang <glezos_> zebob: if you have an issue with your team, I'd suggest to resolve it internally. I'd suggest not to shout (hehe), but explain why you think your opinion is more correct (or, more aligned with Fedora's goals) <zebob> imho we should have : 1 team coordinator = 1 sponsor <glezos_> zebob: if there's something the team itself can't solve ,the problem _can_ escalate up to FLSCo, if needed to FESCo and eventually the Fedora Board. <zebob> that's what we'll do then <glezos_> zebob: thanks. Each team is responsible for its own workflow. But FLSCo is concerned in having healthy collaboration between all people. <glezos_> Please keep us informed if there are any issues you guys can't solve internally. <zebob> ok no problem <zebob> thanks, good night <Rasther> gn * glezos_ closing in 30 <ln-> https://bugzilla.redhat.com/show_bug.cgi?id=464858 <glezos_> </meeting> <glezos_> thanks folks

2 1

virt-top and virt-ctrl POT files!
by Ankit Patel 03 Oct '08

03 Oct '08

Hi Richard, It looks like both the modules virt-top and virt-ctrl share a common POT file. https://translate.fedoraproject.org/POT/virt-ctrl.tip/virt-top.tip.pot (From https://translate.fedoraproject.org/module/virt-ctrl) https://translate.fedoraproject.org/POT/virt-top.tip/virt-top.tip.pot (From https://translate.fedoraproject.org/module/virt-top) Could you please confirm this please? Btw, the modules are not available for translation submission via Transifex. If you would like to receive translations into various languages for these packages please register your modules on Transifex: https://translate.fedoraproject.org/submit/maintainers/info Thanks a lot! -- Regards, Ankit Patel http://www.indianoss.org/

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

trans October 2008