Re: Web interface for translation for GNOME
Re Having developed this functionality in the past (web editor which commits in repo upon save), I highly recommend against it. It's very error-prone, big can of worms. Also what Gil said, it's not worth the time with all those good tools out there. What process do you suggest in between transifex and version control? Axel 2013/9/1 Dimitris Glezos > > On 31 August 2013 15:46, Gil Forcada wrote: > >> [...] a team that >> >> decides that it would be useful for them to have an online translation >> tool could create a project on Launchpad or Transifex, do the >> translations there and then just commit the translations to >> git.gnome.org. Is that even possible? >> > > This is correct. It could be as easy as: > > Push English strings from git to Tx: > > $ git pull > $ tx push --source > > Push translations from Tx to git: > > $ tx pull --lang pt_BR > $ git commit > > If someone is coding it *right now*, sure, I will gladly review the >> patches, try to understand them and push them, but if that's just a wish >> list, the wish will probably have to wait... >> > > Having developed this functionality in the past (web editor which commits > in repo upon save), I highly recommend against it. It's very error-prone, > big can of worms. Also what Gil said, it's not worth the time with all > those good tools out there. > > For what it's worth, the way we worked around it is to actually treat > Transifex as the canonical place where translations leave instead of git. > Like a VCS for translations on a string-level with many additional metadata > Gettext does not support. Git just mirrors this (with automated commit > scripts etc). This is also one of the biggest differences with the current > GNOME workflow/setup. But, Gil is right, it is possible for specific teams > which choose it. > > Hope this helps. > > -d > > > > -- > Dimitris Glezos > > Transifex: The Multilingual Publishing Revolution > https://www.transifex.com/ > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n > > ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Damned Lies website language - «Norwegian»?
I only see "no" and not "nn" in my local django install. Looks like Gil nailed it. http://docs.djangoproject.com/en/dev/internals/contributing/#contributing-translationshas more info on how to contribute l10n to django. Axel 2009/1/15 Gil Forcada > Hi Åsmund, > > Seems a bug in damned-lies because there's a translation for both nn and > no but it justs allows you to select no. > > It's a bit odd, Norwegian in Catalan is not capitalized though in > damned-lies both version (nn and no) are capitalized. > > Maybe this translations come from DJango? Claude? > > If that's the case you will have to translate DJango. > > Cheers, > > El dj 15 de 01 de 2009 a les 11:52 +0100, en/na Åsmund Skjæveland va > escriure: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Jorge González skreiv, den 15. jan. 2009 11:50: > > > Hi Åsmund, > > > > > > On Thu, Jan 15, 2009 at 11:47, Åsmund Skjæveland > > > wrote: > > > Among the list of site languages offered on Damned-Lies is «Norwegian». > > > A quick inspection shows that this is «Norwegian Bokmål» (code nb). Can > > > this be corrected? > > > > > > Also, how are new languages added? Will Norwegian Nynorsk (code nn) > > > appear automatically if I submit a translation? > > >> Norwegian Nynorsk already exists, check > > >> http://l10n.gnome.org/teams/no > > >> (i.e. http://l10n.gnome.org/languages/nn/gnome-2-26/ui/) > > Sorry, what I mean is: > > > > I log in, and go to my profile page. > > There's a combo box labelled 'site language', where I can choose what > > language the website itself uses. > > > > > > > > - -- > > Åsmund Skjæveland > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v1.4.9 (GNU/Linux) > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > > > iEYEARECAAYFAklvFWoACgkQKeJUaVS5dc5XfACePWBgWqxo1sS10S2VAjYvrMb9 > > E7MAnilcjT9wKV0mFdkhSpKkcyQh7AW6 > > =RE+I > > -END PGP SIGNATURE- > > ___ > > gnome-i18n mailing list > > gnome-i18n@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-i18n > -- > gil forcada > > [ca] guifi.net - una xarxa lliure que no para de créixer > [en] guifi.net - a non-stopping free network > bloc: http://gil.badall.net > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: What can Git do for translators?
Jumping in in the middle again, with some experience from Mozilla after our switch to hg: One of they key questions when moving to a dvcs is what goes into which repo. This isn't really a requirement of a dvcs, but seems to come with the design of at least hg, and from glancing at it, git, too. DVCSes are bad at partial clones. In hg it's straight out impossible, and I haven't seen an obvious way in git. From my understanding, this comes from having a unique identifier for a repo so that you know where local commits would go when you push back upstream or round-robin or in circles and whatnot. What we do in Mozilla is: - one repo for Firefox and Toolkit - one repo for Thunderbird and Calendar and most parts of SeaMonkey - helluva more repos on hg or cvs for SeaMonkey - one repo for each localization for all three products The rationale for using a single repo per locale, and to not mirror the split in the en-US products was to optimize for smaller teams, where it's mostly one person working on everything anyway, and to not have them go through 5 repos for one locale. The downside is that for bigger teams with more than one committer, each contributor ends up having to pull and merge other apps and contributions before being able to push their own changes. In particular as we only allow one head per named branch on the repos. (User repos don't have that constraint, though.) There has been a rather lengthy discussion in our community if that's the right choice, both on the en-US side and the l10n side. The benefits of a DVCS just ask for a different set of compromises, sadly. I can't really tell which setup would be right for GNOME, as I don't know the community nor the module structure well enough, but if you have concrete questions, I'll try to come up with concrete answers. Another thing, release tags are a common source of grief, as that's a given landing on the l10n repos that are not done by the localization teams, and thus require them to pull and merge, or not, depending on their local status. HTH Axel 2009/1/8 Gabor Kelemen > Thomas Thurman írta: > > 2009/1/7 Sharuzzaman Ahmat Raslan : > >> What I care is my language po file. Maybe around 15KB. > >> > >> Why should I download the whole bunch of data while the one that I need > is > >> just a small fraction of it. > > > > Indeed, why should you? You can get it from Damned Lies, can't you? > > > > Because I want/have to do > > $ git push > > Or can git check out only a single directory or file? I seriously don't > know, so don't take it as an offence. > > I'm asking this because checking out anything other than $LANG.po and > Changelog, optionally LINGUAS is not really necessary for doing > translations. (CVS could do this! ;)) > > With SVN, we have to check out at least the po directory - not much more > data, but still worse than CVS wrt to saving badwidth. Taking one more > step backwards and having to download an entire repo would be quite bad > in this regard - at least for those with limited bandwidth and until > Transifex saves them. > > Regards > Gabor Kelemen > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: What can Git do for translators?
Jumping in to this discussion at some random point: I think that DVCSes can add value to localizers. In particular for projects that have in-development l10n, but probably for other projects, too. The main value a DVCS gives to localizers is coming from exposing the history of the original language, though. I can see good value in exposing localizable strings to the localizer in changesets as they were added to the original language, as they're likely going to belong to the same context. So while going through a file of localizable strings from top to bottom, you would have to go through several context switches, going through the localizable strings patch-wise might come with less contex switches. That of course is more of a job and an opportunity for translation tools than anything else. Axel 2009/1/7 Leonardo F. Fontenelle > Em Ter, 2009-01-06 às 15:24 +, Simos Xenitellis escreveu: > > Hi All, > > > > There is a discussion on the gnome developer mailing lists regarding a > > possible move from Subversion (SVN) to a Distributed Version Control > > System (DVCS) such as git, which is already used for the Linux kernel, > > Perl, some libraries such as clutter. This post is to help contribute > > to the discussion. > > > > [...] > > > > As a translator I can't see any benefit in a distributed VCS. We work > with _the_ version with _the_ strings; heck, we have even string > freezes! > > Regular translators shouldn't use svn already, because damned lies realy > adds value to the repository (updated message catalogs, alerts, > statistics etc.). But someone must commit the translations, and that > would be the team leaders and a few more translators. > > If damned-lies ever learns to commit translations and "translated" and > other stuff, then translators shouldn't have to care about the VCS. > Otherwise, I wouldn't like to have to learn git or bzr. > > -- > Leonardo Fontenelle > http://leonardof.org > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating Gnome with launchpad.net
2008/12/31 Danilo Šegan <...> > Actually, using Launchpad as a tool (even working on Ubuntu), and then > submitting upstream might give one the best of both worlds. I.e. one > can think of Launchpad as a replacement for KBabel/Gtranslator/Emacs > po-mode, which means that you still have to commit to GNOME SVN once > you are done. Launchpad is a great tool which allows much better > workflow than any other tool out there (that I know of). And it's > soon going to become free software (July 2009). We have a date! That's great news for all looking into l10n tools. Axel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Localizing the firefox extension
Yikes, contents.rdf in the locales files. Did someone try to just remove that file alltogether? Should just work. Axel 2008/11/23 Leonardo F. Fontenelle <[EMAIL PROTECTED]> > I believe I can contribute with instructions for translators on how to > localize (translate) Beagle's Firefox extension in a more familiar way > (from .dtd/.properties to .po and back). > > Where should I place this instructions: in GNOME's wiki, in Beagle's > wiki, or in firefox-extension/chrome/locale/? > > > http://svn.gnome.org/viewvc/beagle/trunk/beagle/firefox-extension/chrome/locale/ > > -- > Leonardo Fontenelle > http://leonardof.org > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Cultural Issue with the Foot Logo
To put in the information of somebody that has nothing to do with gnome, but with brands a bit as part of my work for Firefox. I expect your chances of getting the foot changed to be slim. I just looked over planet.gnome.org, and it's full of foots. The recognition and value of that logo are probably outweighing your problems by an order of magnitude. I didn't see a single post syndicated to planet that would raise wider awareness of your thinking either. I kinda miss a real description of the impact, too. Like, how many users are you really talking about? To give an example of where Firefox is hitting a brick wall in terms of spreading the word. In Korea, nobody is using https to do safe web. There's an architecture built upon active-x controls and IE instead, due to export regulations in the past. So basically, using firefox in Korea, you can't do online shopping or banking or nothing. And yet, we're not shipping active-x. In our global world, there's always a counter example for good decisions, and in those regions, you have to work around it and try to get as good as it gets. That might be lower than in the rest of the world, it might make your evangelism efforts harder, but that's the way it is. In the end, I'd expect someone proposing a change like this to come up with a much more analytical dataset, a few alternative approaches (like a special theme like Petr suggested, for example), and a widely open discussion. Then I'd expect a lot of heat, and finally a decision made by a few brand csars. Take this with a mountain of salt, I really don't know jack about how the gnome project works. I just figured that giving you some preview of the inertia to brand changes would be appropriate. Axel 2008/10/31 Theppitak Karoonboonyanan <[EMAIL PROTECTED]>: > On Fri, Oct 31, 2008 at 6:17 PM, Petr Kovar <[EMAIL PROTECTED]> wrote: > >> What about not using the foot logo, or introducing a new logo, if desirable, >> in Thai (and Lao, and perhaps some others) locale only? Would the logo >> change be sufficient solely as a part of your l10n processes? > > I think it's better not to make it look like a fork. For example, without > appropriate communication, one may think it's like the Firefox/Iceweasel > rebranding case. It would be more seamless if people see the new logo > somewhere at GNOME site as a sign of acceptance so that the logo > can equally, or at least unofficially, represent GNOME, just like how > the Debian project has two versions of logos. > > Then, we can add icon themes using the new logo, and let people > choose or even make appropriate defaults based on locale. This will > also allow people in other locales to choose the logo, although the foot > is no issue for them. > > What do you think? > > Regards, > -- > Theppitak Karoonboonyanan > http://linux.thai.net/~thep/ > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Cultural Issue with the Foot Logo
2008/10/30 F Wolff <[EMAIL PROTECTED]>: <...> > I think I know of at least one team that doesn't translate and promote > Firefox under that brand, since the fox is considered negative in their > culture - I guess for Mozilla there is too much in that brand to dilute > it, but they lost that team (in as far as I know). I see there is a beta > translation of Firefox 3 into Thai - I don't know if it is similar for > you perhaps. Hi Friedel, I don't rule out that I forgot, do you recall which locale that was, and when? Axel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Licenses of .po files, and translations
FWIW, in the Mozilla project, we consider translations to be derivative work. Which is what we consider, I wouldn't know that any lawyer looked at it for us. Axel 2008/9/21 Anna Jonna Armannsdottir <[EMAIL PROTECTED]>: > On fös, 2008-09-12 at 22:26 +0530, Gora Mohanty wrote: >> Thus, as I see it, for an application licensed under >> the GPL, the .pot files, and the .po files are also >> GPL-licensed. > Your argument seems to be that the source of those files > is the GPL ed source. This only holds for th pot file and > the untranslated .po file. > The work of the translators are completely independent of > the source. > Also copyright owners may change their minds and change > license and or terms. Thus translators that were translating > free software may find that their work is being used in > non-free software as well. > Because of this, I would like to explicitly specify GPL as > the license of the .po files I translate. > If other translators would like to translate the same software > under a different license, they are free to do that, because > the .pot file and the .po files are just a template to be > filled out with translations of sentences into a > particular language. Copyright would only hold for the work > as a whole, and as long as there is a difference in the > in the translation as a whole, they would have to be considered > as two separate works, with the similarity beign the template > dot po file. > > This is my personal view on this. > > -- > Anna Jonna Ármannsdóttir coordinator > The Icelandic GNOME Localisation team > http://l10n.gnome.org/teams/is was 11% translated > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Python library for reading and writing OP files
You don't need all of pootle, just the translate toolkit, http://translate.sourceforge.net/wiki/, which pootle is built upon. That's still more than you need, but at least it's there. Axel 2008/7/23 Åsmund Skjæveland <[EMAIL PROTECTED]>: > Is there a Python library for reading and writing PO files? I'm looking for > something that will give me something like an object containing (msgids, > msgstrs, isFuzzy, isObsolete) for each msgid (with plural support), and will > write such strings to a PO file. As far as Google will tell me[1] there's > not too much around, but I think what I'm looking for is hidden inside > Pootle. Basically, is what I'm looking for available as a standalone module, > or will I have to disassemble Pootle? > > -- > Åsmund Skjæveland > > [1] "google:python po file parser" and similar queries was remarkably > unhelpful. > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [EMAIL PROTECTED] vs [EMAIL PROTECTED]
I personally consider this a glibc bug. From the comments I read, it seems that Danilo thinks so, too, but doesn't care enough to block on it. FWIW, if this would bubble up to Mozilla, I'd wontfix it. Not that I see any likelyhood for something with '_' and '@' to do that, but still, just as a datapoint. Disclaimer, I don't have anything to say about or for Gnome, or Serbian, though, someone who does should step up. Axel 2008/4/17, Matthias Clasen <[EMAIL PROTECTED]>: > On Thu, Apr 17, 2008 at 10:21 AM, Axel Hecht <[EMAIL PROTECTED]> wrote: > > 2008/4/17, Matthias Clasen <[EMAIL PROTECTED]>: > > > > > > > glibc changed from @Latn to @latin some time ago. > > > Can we change the Gnome translations to go the same way ? > > > > > > Using different locale labels in different parts of the OS is certainly > > > bad news for Serbian users, and I get bugs filed against GLib and GTK+ > > > in Fedora to change to [EMAIL PROTECTED] > > > > Is there a bug report or some other thing to see the original decision > > on the glibc side? > > > > > Here is some old mailing list discussion, if you enjoy that kind of thing: > http://www.cygwin.com/ml/libc-alpha/2003-09/msg00245.html > > And here are some bugs that touch Latn vs latin: > http://sources.redhat.com/bugzilla/show_bug.cgi?id=38 > http://sources.redhat.com/bugzilla/show_bug.cgi?id=549 > > And some more: > https://bugzilla.redhat.com/buglist.cgi?bug_id=426593,426585,442797,442799 > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [EMAIL PROTECTED] vs [EMAIL PROTECTED]
2008/4/17, Matthias Clasen <[EMAIL PROTECTED]>: > glibc changed from @Latn to @latin some time ago. > Can we change the Gnome translations to go the same way ? > > Using different locale labels in different parts of the OS is certainly > bad news for Serbian users, and I get bugs filed against GLib and GTK+ > in Fedora to change to [EMAIL PROTECTED] Is there a bug report or some other thing to see the original decision on the glibc side? Axel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Import from Launchpad
Hi all, just hooking this up somewhere in this thread. I've been watching this thread with interest, as I see that discussion coming at me at Mozilla (hi Danilo :-)) My thoughts are somewhat assumption-heavy, so bear with me when I'm wrong. I think that a good deal of the web translation tools actually offer multiple values for each translatable string, not sure about launchpad here in particular, but it may not matter. Here's my picture: After a piece of software went through a webtool, at least through one with a low barrier of entry, you end up with something that I call a translation cloud. In this picture, I'm mostly dropping the change-pattern, and simply look at the result. Each particle in this cloud has various meta data, like, author, date of creation, possibly "imported from upstream". The task seems to be to me to extract a localization from this translation cloud. Where I use "localization" here in contrast to "translation" to mean something that satisfies certain software engineering principles, like consistency, correctness, testings passed, etc. That seems to be a data mining thing. Democracy on individual entries might be something to bootstrap with, but I would hope that there is way more structure hidden in that data. Like, if you'd pick a set of the N entries with the most participation, and you'd pick a winner localization for each, then you could take the set of authors that got M% of those strings right. And then you take all the strings where, say K% of those authors agree. Sounds complicated, but really isn't, if you drop the numbers to tune. For the 10 most debated strings, pick a winning localization. Pick all localized strings that are the same from all the authors that had all winners right, and you get a possibly good data set. In the context of this discussion, one valuable form of meta data would be "imported from upstream" and to grant a significant trust-value to those 'particles' in the translation cloud. That keeps random changes out without ruling out improvements. A different approach would be to not look at the end particles, but rather to look at changes. Like, each 'edit' would be a branch, and it might be interesting to look at what the version control system authors know about their algebras and merging to come up with valuable output from low-barrier systems. The fact that we're really dealing with a huge amount of not so structured branches makes me favour the data mining idea, but then again, what do I know about the algebras that the distributed version control system folks have. And what do I know if I'd understand what they saying when they talked about it. Anyway, I think it's worthwhile to focus on how to gain output out of low-barrier systems and create measures of confidence for translated strings from them. I guess most of the folks that are actually hacking on the tools side will be at fosdem, so if this makes sense to you, you might want to spoil a beer or two with chatting about this. Sadly, I won't be able to join. I'll try next time. Axel PS: If I CCed someone not reading the original thread, sorry. http://mail.gnome.org/archives/gnome-i18n/2008-January/thread.html#00227 has the context. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Blog about l10n
Hi Leonardo, I read the interview with Dijhed, pretty interesting. Dijhed, if you happen to read this, I'd like to have a few with you about how you guys do the technical dictionary. Then I hit reload, stupid me,Fatal error: Call to a member function on a non-object in /home/telurion/public_html/wp-includes/classes.php on line 33 is all I get now :-/ Axel 2007/5/14, Leonardo Fontenelle <[EMAIL PROTECTED]>: > I've being blogging about free software l10n for a few weeks now, and > though you might be interested. I am focusing on increasing the > communication between the Brazilian translation teams, but I translate > the most relevant articles to English. Djihed Afifi, from the Arabic > localization team, was the first interview I published, and you'll > also find the name of those who contributed to the first complete > GNOME interface translation to pt_BR I've ever heard of. > > The layout is a little buggy, because Gengo [1] doesn't play well wit > WordPress widgets [2] and I don't know/want to edit PHP files. > Hopefully this will be fixed with WP 2.2. [3] > > Leonardo F. Fontenelle > http://leonardof.org > > 1. http://jamietalbot.com/wp-hacks/gengo/ > 2. http://automattic.com/code/widgets/ > 3. http://jamietalbot.com/wp-hacks/forum/comments.php?DiscussionID=59 > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Batch-checkout SVN po folders
You want ssh-agent, with ssh-add. http://www.mozilla.org/cvs-ssh-faq.html#s4 for written docs. Axel 2007/5/8, Yannig MARCHEGAY <[EMAIL PROTECTED]>: > Thanks a lot. I don't need a lot a disk-space: I've edited your script by > adding /po at the end of the address. > Another thing: any way not to have to type my .ssh/id_rsa password 300 > times? ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
l10n/i18n architecture proposal, RFC, presentation at FOSDEM
Hi all, first of all, sorry for cross-posting, I guess some of you will get this message two or three times. Short introduction of myself, my name is Axel Hecht, and I'm coordinating the localizations for Firefox and Thunderbird. While looking at our status quo at Mozilla, and looking at other attempts, I'm seeing limitations in both what we can do and what others can do, and came up with an alternative proposal which I'm now opening up for a broader community feedback. I am proposing a solution for plain strings of course, but plurals and declensions, too. Declensions are new, and, sadly, not backwards compatible in any way. I also made a move on parameter substitution in localized strings. All of this is new enough to take Localization from version 1.0 to 2.0 (yeah, I'm all web 2.0), so I took the freedom to codename this l20n. Pronounced l-twenty, I drop the 'n'. This proposal is done with Mozilla on my mind, but it is in no way limited to Mozilla, thus I'm seeking wider feedback and cooperation on this. There are some documents on l20n on the mozilla wiki, if you're interested, please check out http://wiki.mozilla.org/L20n, I have a proof-of-concept implementation with some basic examples implemented in ajax (you'll see I'm no web designer) on http://people.mozilla.com/~axel/l20n/js-l20n/. I will give a presentation at FOSDEM this weekend, too, http://fosdem.org/2007/schedule/events/mozilla_l20n, that's Sunday at 2pm. I'll give some introduction on where l20n is supposed to go, and I do hope to have a good deal of discussion there. Feel free to grab me anywhere close to the Mozilla developers room, if you wish. Online feedback is of course welcome, either to me, or put challenges up on the wiki (add your pages to the L20n category, please). Discussion threads are likely best suited for the mozilla.dev.i18n newsgroup, which you can find on google groups, too, in addition to news.mozilla.org. That's close topic-wise and really low bandwidth, so your signal-to-noise ratio should be fine. There are very few things set in stone, so I'll be happy to see a wider community participate. Thanks and sorry for the wide-spread noise, I'll only do that once. Axel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
