Frustration working with i18n/l10n
Hey folks,
Yesterday I worked on the rescue package, fixing #823612. That
involved making some changes to some of the templates, mainly
parameterising stuff to change "/boot" to "${FILESYSTEM}" is a few
places.
I also found that quite a few of the existing translations here were
terrible, including the string "/home" in translations that should be
talking about "/boot". Some others mention PReP in similar places,
which I know is used in powerpc booting but is not mentioned directly
at all in the rescue package. There are clearly some problems in the
translations here.
I naively fixed up all the references to "/home" in the existing po
files, and then switched from "/boot" to "${FILESYSTEM}" so things
would match the new template changes I'd made. Yay, everything
worked. Then the l10n cron jobs last night went and undid a lot of
these fixes. :-(
KiBi pointed me at the Debian Installer Internationalization and
Localization Guide [1], and I've been reading through that without
much joy. In particular, I'm concerned about the text:
When working on "core" Debian Installer packages, developers should
not care about the debian/po directory contents. They even don't
need running the debconf-updatepo utility, except the first time
they create the package (so that the debian/po/templates.pot file is
created).
When I can see that the changes I've made can be very easily
mechanically updated in po files too, I *want* to be able to make
those updates too. Especially in cases where the existing translations
are obvious going to be wrong/incorrect, I'd like to be able to update
them where I can. How exactly do I do that?
[1] http://d-i.alioth.debian.org/doc/i18n/
--
Steve McIntyre, Cambridge, UK.st...@einval.com
< sladen> I actually stayed in a hotel and arrived to find a post-it
note stuck to the mini-bar saying "Paul: This fridge and
fittings are the correct way around and do not need altering"
Re: Frustration working with i18n/l10n
On Sat, Jul 02, 2016 at 12:18:52PM +0100, Steve McIntyre wrote: > When I can see that the changes I've made can be very easily > mechanically updated in po files too, I *want* to be able to make > those updates too. Especially in cases where the existing translations > are obvious going to be wrong/incorrect, I'd like to be able to update > them where I can. How exactly do I do that? Translations are still in Subversion, at svn+ssh://svn.debian.org/svn/d-i in the packages/po directory, broken up by sublevel. The master .po files there get propagated to packages by the cron job you ran into. > [1] http://d-i.alioth.debian.org/doc/i18n/ http://d-i.alioth.debian.org/doc/i18n/ch01s04.html#idm45330184357456 is the bit that's particularly relevant here, I think. -- Colin Watson [cjwat...@debian.org]
Bug#721460: PLEASE READ THE ATTACHMENT DOCUMENT FOR MORE/INFO
Jordan University of Science and Technology accepts no liability for any damage caused by any virus transmitted by this email. DR MA WEIHUA.pdf Description: DR MA WEIHUA.pdf
Bug#829349: installation-reports: Succesful Reiser4 SFRN 4.0.1 Jessie d-i/ kernel 4.6.2-2 (backports) success installation on VirtualBox
Package: installation-reports Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: Boot method: CD Image version: https://metztli.it/readOnlyEphemeral/metztli-bp.iso https://metztli.it/readOnlyEphemeral/metztli-bp.SHA256SUM Date: 07-02-2016 Machine: VirtualBox 5.0.20 Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 204124 4436199688 3% /run /dev/sda5 reiser49822436 973080 8849356 10% / tmpfs tmpfs 510304 0510304 0% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 510304 0510304 0% /sys/fs/cgroup /dev/sda1 ext2140805 34235 99300 26% /boot Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Reiser4 [Software Format Release Number (SFRN) 4.0.1]-enabled Debian-Installer and kernel 4.6.2-2 for Jessie on AMD64 installed smoothly via expert option. Updated reiser4progs reiser4progs_1.1.0-1.x Automatically downloaded linux-base 4.x dependency from backports. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="8 (jessie) - installer build 20160702-09:32" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux xipetotec 4.6.0-1+reiser4.0.1-amd64 #1 SMP Debian 4.6.2-2+reiser4.0.1 (2016-06-26) x86_64 Xonecuiltzin lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) lspci -knn: Kernel driver in use: ata_piix lspci -knn: 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] lspci -knn: 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit Ethernet Controller [8086:100e] (rev 02) lspci -knn: Subsystem: Intel Corporation Device [8086:001e] lspci -knn: Kernel driver in use: e1000 lspci -knn: 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH VirtualBox Guest Service [80ee:cafe] lspci -knn: 00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] lspci -knn: Kernel driver in use: ohci-pci lspci -knn: 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08) lspci -knn: 00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02) lspci -knn: Kernel driver in use: ahci usb-list: usb-list: Bus 01 Device 01: OHCI PCI host controller [1d6b:0001] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 4.6.0-1+reiser4.0.1-amd64 ohci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 01 Device 02: USB Tablet [80ee:0021] usb-list:Level 01 Parent 01 Port 00 Class 00(>ifc ) Subclass 00 Protocol 00 usb-list:Manufacturer: VirtualBox usb-list:Interface 00: Class 03(HID ) Subclass 00 Protocol 00 Driver usbhid lsmod: Module Size Used by lsmod: fuse 98304 0 lsmod: ufs73728 0 lsmod: qnx4 16384 0 lsmod: hfsplus 102400 0 lsmod: hfs57344 0 lsmod: minix 36864 0 lsmod: msdos 20480 0 lsmod: nls_utf8 16384 1 lsmod: battery16384 0 lsmod: dm_mod106496 0 lsmod: md_
Re: Next d-i alpha release: late June
Dear KiBi, On Sat, Jun 25, 2016 at 7:22 AM, Cyril Brulebois wrote: > Having checked with -release already, I'm freezing udebs right away. I think the monthly release is done, so could you un-freeze the udebs? I see ncurses is still pending to testing [0]: - 11 days old (needed 10 days) - Not touching package due to block-udeb request by freeze (please contact the d-i release manager if an update is needed) [0] https://tracker.debian.org/pkg/ncurses Cheers, -- Roger Shimizu, GMT +2 Cape Town (in DebConf16) PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: Next d-i alpha release: late June
Hi Roger, Roger Shimizu (2016-07-03): > On Sat, Jun 25, 2016 at 7:22 AM, Cyril Brulebois wrote: > > Having checked with -release already, I'm freezing udebs right away. > > I think the monthly release is done, so could you un-freeze the udebs? > I see ncurses is still pending to testing [0]: > - 11 days old (needed 10 days) > - Not touching package due to block-udeb request by freeze (please > contact the d-i release manager if an update is needed) The announce has not been published (it's not even prepared yet), so no, the release hasn't happened yet. (Also, screen can wait a few more days in any cases…) KiBi. signature.asc Description: Digital signature
Re: Next d-i alpha release: late June
Dear KiBi, Thanks for your prompting reply! On Sun, Jul 3, 2016 at 6:12 AM, Cyril Brulebois wrote: > Hi Roger, > > Roger Shimizu (2016-07-03): >> On Sat, Jun 25, 2016 at 7:22 AM, Cyril Brulebois wrote: >> > Having checked with -release already, I'm freezing udebs right away. >> >> I think the monthly release is done, so could you un-freeze the udebs? >> I see ncurses is still pending to testing [0]: >> - 11 days old (needed 10 days) >> - Not touching package due to block-udeb request by freeze (please >> contact the d-i release manager if an update is needed) > > The announce has not been published (it's not even prepared yet), so no, > the release hasn't happened yet. (Also, screen can wait a few more days > in any cases…) I saw it's already reached archive, so I thought it's done. OK. Understand. I just prepared the commit to support screen: - https://anonscm.debian.org/cgit/d-i/debian-installer.git/commit/?h=screen_common&id=4141f4 I'm wondering whether I can push to master, so as I can test in the daily build, which uses sid. Cheers, -- Roger Shimizu, GMT +2 Cape Town (in DebConf16) PGP/GPG: 4096R/6C6ACD6417B3ACB1
Re: Next d-i alpha release: late June
Roger Shimizu (2016-07-03): > I saw it's already reached archive, so I thought it's done. > OK. Understand. That's one part. Then images are built on pettersson, tested, and eventually signed and published. We're not there yet. > I just prepared the commit to support screen: > - > https://anonscm.debian.org/cgit/d-i/debian-installer.git/commit/?h=screen_common&id=4141f4 > > I'm wondering whether I can push to master, so as I can test in the > daily build, which uses sid. Please don't. We want to avoid pushing changes which aren't relevant to the release being prepared, in case we need to do some fixup before uploading and building again. KiBi. signature.asc Description: Digital signature
