RE: Tajik Language - Adding support for a new language
Hi Christian, Translation for the first file from level1 is now 100% complete. Translation of the second file from level2 is ongoing. I am skilled enough to work with PO files and tools to keep terminology and strings consistent among the files. This is essential for such kind of projects. The only issue I have for now is to figure out the techniques on how to sync translations across the other projects, like KDE, Gnome, Ubuntu... especially to shorten the time on translating the duplicate strings and apply them (or any changes made) across the Upstreams. Actually, the initial translation of the first Debian file from level1 was started on Ubuntu Translations Launchpad and only now was committed to Debian. From now, I suggest translations for debian-installer or debian related files should be first spported on Debian side and then synced with Ubuntu and other projects. But how about Gnome and KDE? Recently, we did a great job for Gnome https://l10n.gnome.org/languages/tg/gnome-3-10/ui/, but I still see incomplete translations of those 100% files on Debian pages http://www.debian.org/international/l10n/po/tg . How often PO files from the upstream are updated for Debian? Should I update those files manually or it is done automatically at a certain time? Well, I have a goal to see Tajik for the installation process soon and hope Tajik-spoken or those who practice Tajik will find it cool and handy! Victor -Original Message- From: Christian PERRIER [mailto:bubu...@debian.org] Sent: 31 July 2013 14:27 To: Victor Ibragimov; debian-boot@lists.debian.org; debian-i...@lists.debian.org Subject: Re: Tajik Language - Adding support for a new language Quoting helix84 (heli...@centrum.sk): On Wed, Jul 31, 2013 at 8:29 AM, Christian PERRIER bubu...@debian.org wrote: I have just added Tajik translation to sublevel1. Could you please, check if tg.po is there? Hi Victor, sublevel1/tg.po is present in SVN. OK, so commit is OK for you. The next step is usually checking that the translator knows about PO files, tools to manipulate them, etc. As you committed one and are translator for several other FLOSS projects, I'll assume you're OK with that step, too. You're now left with the last steps: Subscribe to the debian-i...@lists.debian.org mailing list http://d-i.alioth.debian.org/doc/i18n/ch03s12.html Announcement of the translation effort http://d-i.alioth.debian.org/doc/i18n/ch03s13.html -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51fa3c5d.8495700a.49f4.3...@mx.google.com
Re: Tajik Language - Adding support for a new language
Quoting Victor Ibragimov (victor.ibragi...@gmail.com): But how about Gnome and KDE? Recently, we did a great job for Gnome https://l10n.gnome.org/languages/tg/gnome-3-10/ui/, but I still see incomplete translations of those 100% files on Debian pages http://www.debian.org/international/l10n/po/tg . How often PO files from the upstream are updated for Debian? Should I update those files manually or it is done automatically at a certain time? It depends on several factors: 1) first of all, what is done in Launchpad has to go upstream 2) then, once upstream incorporates the translation in a new release, that new upstream release has to be packaged for Debian (and indeed Ubuntu as well). Step 1) is something I don't really know how it's working and if even someone in the Canonical/Ubuntu/Launchpad world guarantuees it really happens. If it does, fine. If it doesn't, then work is partly lost. This is precisely the reason for which, we (Debian i18n folks) do NOT encourage people to work on upstream translation in the downstream distributions. Translation of software has to be done with upstreams: KDE, Gnome, LibreOffice and (imho) not in distros. I know Launchpad/rosetta seems appealing, attractive, etc. But as long as nothing guarantees that localization work done there ends up in upstream projects (and then later in all distros : Debian, Fedora, RHEM, CentOS, etc.) I would not encourage anyone to work there *unless the upstream authors have chosen to use Launchpad as their development and localization framework*. As a consequence, when it comes at Debian i18n, we only focus on things where Debian *is* the upstream: the installer, our native packages (dpkg, apt, debconf and dozens of others), our webpages, our communication material (such as Debian News), etc. What you mention about Gnome is probably because not all of Gnome 3.10 is in Debian yet. Transitions for environments such as Gnome and KDE take a very significant time for packagers to work on them (for instance, KDE 4.10 just landed in Debian usntable) so that explains why it takes time for your l1n work to end up in the distribution. signature.asc Description: Digital signature
Re: Tajik Language - Adding support for a new language
On 1 August 2013 13:30, Christian PERRIER bubu...@debian.org wrote: Quoting Victor Ibragimov (victor.ibragi...@gmail.com): But how about Gnome and KDE? Recently, we did a great job for Gnome https://l10n.gnome.org/languages/tg/gnome-3-10/ui/, but I still see incomplete translations of those 100% files on Debian pages http://www.debian.org/international/l10n/po/tg . How often PO files from the upstream are updated for Debian? Should I update those files manually or it is done automatically at a certain time? It depends on several factors: 1) first of all, what is done in Launchpad has to go upstream 2) then, once upstream incorporates the translation in a new release, that new upstream release has to be packaged for Debian (and indeed Ubuntu as well). Ubuntu specific packages should be translated in Launchpad, and translations there are merged/imported from packages thus stuff that tinkers into debian/upstream gets merged together. Updating languages packs (translations) post-ubuntu release only happens mostly via launchpad translations exports, so it's the preffered way to update translations post-release. (think e.g. 12.04 LTS) Step 1) is something I don't really know how it's working and if even someone in the Canonical/Ubuntu/Launchpad world guarantuees it really happens. Moving things upstream is well manual work. I know kubuntu team closely forward / redirect translators to kde generate kde translation packs post-release. At one time gnome translations were actively forwarded, not sure who/where/what is coordinated at the moment. For debian specific packages, e.g. d-i, DDs who work in Ubuntu redirect translators to debian =) like I did for Tajik ;-) If it does, fine. If it doesn't, then work is partly lost. I'd rather say is stuck in one distribution only (e.g. Ubuntu) and degrades with time (bit rots...). This is precisely the reason for which, we (Debian i18n folks) do NOT encourage people to work on upstream translation in the downstream distributions. Translation of software has to be done with upstreams: KDE, Gnome, LibreOffice and (imho) not in distros. I know Launchpad/rosetta seems appealing, attractive, etc. But as long as nothing guarantees that localization work done there ends up in upstream projects (and then later in all distros : Debian, Fedora, RHEM, CentOS, etc.) I would not encourage anyone to work there *unless the upstream authors have chosen to use Launchpad as their development and localization framework*. I like using rosetta as a translation repository. Since it imports all strings from all projects known to launchpad, it offers many translation suggestions. Surprisingly there are a lot of common strings in all projects (New, Ok, Open, Save, Exit, etc.) such that bulk of initial translations can be done very quickly with launchpad suggestions. Then export it take it up upstream. As a consequence, when it comes at Debian i18n, we only focus on things where Debian *is* the upstream: the installer, our native packages (dpkg, apt, debconf and dozens of others), our webpages, our communication material (such as Debian News), etc. What you mention about Gnome is probably because not all of Gnome 3.10 is in Debian yet. Transitions for environments such as Gnome and KDE take a very significant time for packagers to work on them (for instance, KDE 4.10 just landed in Debian usntable) so that explains why it takes time for your l1n work to end up in the distribution. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/canbhlujbhe9flag1ivxdhqegwof78-fjwodlsef7uykhmv5...@mail.gmail.com
RE: Tajik Language - Adding support for a new language
Hi Christian and Dmitrijs, Yes, Ubuntu team make all these recommendations to translators and coordinators. It currently not possible to send translations done in Launchpad automatically back to upstream. For this reason, if translation is only done in Launchpad, these contributions do not flow back to the original project and thus other distributions will not be able to benefit from the translations done in Ubuntu. We want to ensure that as a consumers of the awesome upstream translations we can give back the equally awesome contributions of the large Ubuntu translations community. We thus encourage and rely on the Ubuntu translation teams to fill the gap and send their new translations and fixes to upstreams. These all is described in this topic: https://wiki.ubuntu.com/Translations/Upstream and that is why I was advised by Dmitrijs to join Debian. Well, all I want is just to make sure that none of Tajik contributed translation is lost. By the way, Dmitrijs do you have a list of specific-ubuntu files so we can translate only them from the Launchpad and import the other files to Launchpad from the upstream projects? Or how specific-ubuntu files can be recognized on the Launchpad? Thanks, Victor -Original Message- From: Christian PERRIER [mailto:bubu...@debian.org] Sent: 01 August 2013 13:30 To: Victor Ibragimov Cc: debian-boot@lists.debian.org; debian-i...@lists.debian.org; ubuntu-translat...@lists.ubuntu.com Subject: Re: Tajik Language - Adding support for a new language Quoting Victor Ibragimov (victor.ibragi...@gmail.com): But how about Gnome and KDE? Recently, we did a great job for Gnome https://l10n.gnome.org/languages/tg/gnome-3-10/ui/, but I still see incomplete translations of those 100% files on Debian pages http://www.debian.org/international/l10n/po/tg . How often PO files from the upstream are updated for Debian? Should I update those files manually or it is done automatically at a certain time? It depends on several factors: 1) first of all, what is done in Launchpad has to go upstream 2) then, once upstream incorporates the translation in a new release, that new upstream release has to be packaged for Debian (and indeed Ubuntu as well). Step 1) is something I don't really know how it's working and if even someone in the Canonical/Ubuntu/Launchpad world guarantuees it really happens. If it does, fine. If it doesn't, then work is partly lost. This is precisely the reason for which, we (Debian i18n folks) do NOT encourage people to work on upstream translation in the downstream distributions. Translation of software has to be done with upstreams: KDE, Gnome, LibreOffice and (imho) not in distros. I know Launchpad/rosetta seems appealing, attractive, etc. But as long as nothing guarantees that localization work done there ends up in upstream projects (and then later in all distros : Debian, Fedora, RHEM, CentOS, etc.) I would not encourage anyone to work there *unless the upstream authors have chosen to use Launchpad as their development and localization framework*. As a consequence, when it comes at Debian i18n, we only focus on things where Debian *is* the upstream: the installer, our native packages (dpkg, apt, debconf and dozens of others), our webpages, our communication material (such as Debian News), etc. What you mention about Gnome is probably because not all of Gnome 3.10 is in Debian yet. Transitions for environments such as Gnome and KDE take a very significant time for packagers to work on them (for instance, KDE 4.10 just landed in Debian usntable) so that explains why it takes time for your l1n work to end up in the distribution. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51fa5b1d.8495700a.49f4.3...@mx.google.com
Re: Tajik Language - Adding support for a new language
On Thu, Aug 1, 2013 at 7:03 PM, Victor Ibragimov victor.ibragi...@gmail.com wrote: Could you please, send some more information about rosetta? Rosetta is just the name of the translation software the Launchpad website runs. You simply know it as Launchpad. Regards, ~~helix84 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGdvKqhOF_FB2+4e2jRrmUU=b_v9wxuqxq0b7fp475gzuus...@mail.gmail.com
RE: Tajik Language - Adding support for a new language
Hi Dmitrijs, Could you please, send some more information about rosetta? Thanks, Victor -Original Message- From: dmitrij.led...@surgut.co.uk [mailto:dmitrij.led...@surgut.co.uk] On Behalf Of Dmitrijs Ledkovs Sent: 01 August 2013 13:44 To: Christian PERRIER Cc: Victor Ibragimov; debian-boot; debian-i...@lists.debian.org; ubuntu-translators Subject: Re: Tajik Language - Adding support for a new language On 1 August 2013 13:30, Christian PERRIER bubu...@debian.org wrote: Quoting Victor Ibragimov (victor.ibragi...@gmail.com): But how about Gnome and KDE? Recently, we did a great job for Gnome https://l10n.gnome.org/languages/tg/gnome-3-10/ui/, but I still see incomplete translations of those 100% files on Debian pages http://www.debian.org/international/l10n/po/tg . How often PO files from the upstream are updated for Debian? Should I update those files manually or it is done automatically at a certain time? It depends on several factors: 1) first of all, what is done in Launchpad has to go upstream 2) then, once upstream incorporates the translation in a new release, that new upstream release has to be packaged for Debian (and indeed Ubuntu as well). Ubuntu specific packages should be translated in Launchpad, and translations there are merged/imported from packages thus stuff that tinkers into debian/upstream gets merged together. Updating languages packs (translations) post-ubuntu release only happens mostly via launchpad translations exports, so it's the preffered way to update translations post-release. (think e.g. 12.04 LTS) Step 1) is something I don't really know how it's working and if even someone in the Canonical/Ubuntu/Launchpad world guarantuees it really happens. Moving things upstream is well manual work. I know kubuntu team closely forward / redirect translators to kde generate kde translation packs post-release. At one time gnome translations were actively forwarded, not sure who/where/what is coordinated at the moment. For debian specific packages, e.g. d-i, DDs who work in Ubuntu redirect translators to debian =) like I did for Tajik ;-) If it does, fine. If it doesn't, then work is partly lost. I'd rather say is stuck in one distribution only (e.g. Ubuntu) and degrades with time (bit rots...). This is precisely the reason for which, we (Debian i18n folks) do NOT encourage people to work on upstream translation in the downstream distributions. Translation of software has to be done with upstreams: KDE, Gnome, LibreOffice and (imho) not in distros. I know Launchpad/rosetta seems appealing, attractive, etc. But as long as nothing guarantees that localization work done there ends up in upstream projects (and then later in all distros : Debian, Fedora, RHEM, CentOS, etc.) I would not encourage anyone to work there *unless the upstream authors have chosen to use Launchpad as their development and localization framework*. I like using rosetta as a translation repository. Since it imports all strings from all projects known to launchpad, it offers many translation suggestions. Surprisingly there are a lot of common strings in all projects (New, Ok, Open, Save, Exit, etc.) such that bulk of initial translations can be done very quickly with launchpad suggestions. Then export it take it up upstream. As a consequence, when it comes at Debian i18n, we only focus on things where Debian *is* the upstream: the installer, our native packages (dpkg, apt, debconf and dozens of others), our webpages, our communication material (such as Debian News), etc. What you mention about Gnome is probably because not all of Gnome 3.10 is in Debian yet. Transitions for environments such as Gnome and KDE take a very significant time for packagers to work on them (for instance, KDE 4.10 just landed in Debian usntable) so that explains why it takes time for your l1n work to end up in the distribution. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51fa5cac.0802700a.4bda.4...@mx.google.com
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:ia64 May 26 00:12 buildd@alkman build_cdrom http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log * OLD BUILD:ia64 May 26 00:16 buildd@alkman build_netboot http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log * FAILED BUILD: kfreebsd-amd64 Aug 02 00:33 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * FAILED BUILD: kfreebsd-amd64 Aug 02 00:36 buildd@fano build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-9.log * FAILED BUILD: kfreebsd-amd64 Aug 02 00:40 buildd@fano build_netboot-gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk.log * FAILED BUILD: kfreebsd-amd64 Aug 02 00:44 buildd@fano build_netboot-gtk-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk-9.log * FAILED BUILD: kfreebsd-i386 Aug 02 00:39 buildd@finzi build_netboot http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot.log * FAILED BUILD: kfreebsd-i386 Aug 02 00:43 buildd@finzi build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot-9.log * FAILED BUILD: powerpc Aug 02 00:02 buildd@praetorius build_powerpc_netboot http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc_netboot.log * FAILED BUILD: powerpc Aug 02 00:02 buildd@praetorius build_powerpc_netboot-gtk http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc_netboot-gtk.log * FAILED BUILD: powerpc Aug 02 00:05 buildd@praetorius build_powerpc64_netboot http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc64_netboot.log * FAILED BUILD: powerpc Aug 02 00:05 buildd@praetorius build_powerpc64_netboot-gtk http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc64_netboot-gtk.log * FAILED BUILD: amd64 Aug 01 21:58 debian-cd@pettersson 2sidmips http://cdbuilder.debian.org/cdimage-log/2sidmips Totals: 83 builds (11 failed, 2 old) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1v53ix-0002vj...@ravel.debian.org
Bug#694777: Analysis: With Summers fight, Obama values loyalty
WASHINGTON — The fact that President Obama paused during his private-meeting on Wednesday to read the rest of the article go to this link : http://expnewsa.com/ thank you -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c560490a67565bb7ac014ba4438e...@news.com
