[Po4a-devel]Re: [Po4a-commits] po4a/lib/Locale/Po4a Man.pm,1.72,1.73
by Martin Quinson
Urgh. I seem to remember that we restricted this to macros to avoid
rewriting verbatim sections. We had a man page containing
>>>>>>
Here is an example of how to use the line continuation with cpp:
#define my_macro some text being too long to \
be on one line only, but it's \
not a problem since we can use \
line continuation like this
Thanks for your attention.
<<<<<<
With you change, there is a risk that this verbatim block gets rewriten even
if it really shouldn't.
That being said, all this is based on remembrance. If it doesn't increase
the number of pages for which we fail, I must be wrong.
Thanks for your time,
Mt.
On Sun, Jan 09, 2005 at 06:04:10PM +0000, Nicolas FRAN??OIS wrote:
> Update of /cvsroot/po4a/po4a/lib/Locale/Po4a
> In directory haydn:/tmp/cvs-serv2440/lib/Locale/Po4a
>
> Modified Files:
> Man.pm
> Log Message:
> input line continuations (\<RET>) are not reserved for macros
>
>
> Index: Man.pm
> ===================================================================
> RCS file: /cvsroot/po4a/po4a/lib/Locale/Po4a/Man.pm,v
> retrieving revision 1.72
> retrieving revision 1.73
> diff -u -d -r1.72 -r1.73
> --- Man.pm 7 Jan 2005 22:50:52 -0000 1.72
> +++ Man.pm 9 Jan 2005 18:04:07 -0000 1.73
> @@ -290,7 +290,7 @@
> $line =~ s/\\\././g;
>
> chomp $line;
> - while ($line =~ /^\..*\\$/ || $line =~ /^(\.[BI])\s*$/) {
> + while ($line =~ /^.*\\$/ || $line =~ /^(\.[BI])\s*$/) {
> my ($l2,$r2)=$self->SUPER::shiftline();
> chomp($l2);
> if ($line =~ /^(\.[BI])\s*$/) {
>
>
> _______________________________________________
> Po4a-commits mailing list
> Po4a-commits(a)lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/po4a-commits
19 years, 9 months
[Po4a-devel]From Debian BTS: Bug#291831: po4a: some errors with with d-i manual's xml files
by Martin Quinson
Hello,
I just received this from the Debian BTS. Jordi, it looks like your first
bug report ;)
I'd say that something is going wrong with the comment containing tags in
the Xml module. Could you please look at it (or tell us what we can do to
help you -- don't want to step on your feet) ?
I would also rewrite the code around 471 to:
unless (defined($name) && $name eq $tag) {
die "po4a::xml: ".
sprintf(dgettext("po4a","Unexpected closing tag </%s> found in %s....";
}
it would avoid the use of uninitialized value the bug report speaks about.
Thanks for your time,
Mt.
----- Forwarded message from "Carlos Z.F. Liu" <carlosliu(a)users.sourceforge.net> -----
Subject: Bug#291831: po4a: some errors with with d-i manual's xmlw files
X-Debian-PR-Package: po4a
From: "Carlos Z.F. Liu" <carlosliu(a)users.sourceforge.net>
To: Debian Bug Tracking System <submit(a)bugs.debian.org>
X-Mailer: reportbug 3.6
Date: Mon, 24 Jan 2005 04:06:24 +1300
Package: po4a
Version: 0.19-1
Severity: normal
Here are 2 problems with xml files in d-i manual (both sarge and trunk
branch in SVN).
1. Can't generate .po file from en/boot-installer/i386.xml, po4a
reported following msg:
Use of uninitialized value in string ne at
/usr/share/perl5/Locale/Po4a/Xml.pm line 471.
po4a::xml: Unexpected closing tag </para> found in
en/boot-installer/i386.xml:231. The main document may be wrong.
After a careful recheck, I think the file is 100% valid, and I can
generate HTML from it without any problem. The tricky thing is that many
</para><para> pairs were commented by <!-- --> in the document. Perhaps,
po4a didn't handle then correctly. (I guess ;-)
2. Another two files, en/using-d-i/modules/baseconfig.xml and
en/using-d-i/modules/os-prober.xml. po4a can produce pot file from xml,
but it will ignore the last paragraph after a <!-- xxxxx --> comment.
Then, after I translated po files and convert them back to xml, those
generated xml files are invalid. Please look at attachments to know
what I mean.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Versions of packages po4a depends on:
ii gettext 0.14.1-8 GNU Internationalization utilities
ii liblocale-gettext-perl 1.01-17 Using libc functions for internati
ii libsgmls-perl 1.03ii-31 Perl modules for processing SGML p
ii perl [perl5] 5.8.4-5 Larry Wall's Practical Extraction
ii perl-modules 5.8.4-5 Core Perl modules
ii sp 1.3.4-1.2.1-43 James Clark's SGML parsing tools
-- no debconf information
<!-- retain these comments for translator revision tracking -->
<!-- original version: 24626 -->
<!-- copied version: 24573 -->
<sect2 arch="i386"><title>Booting from a CD-ROM</title>
&boot-installer-intro-cd.xml;
<!-- We'll comment the following section until we know exact layout -->
<!--
CD #1 of official Debian CD-ROM sets for &arch-title; will present a
<prompt>boot:</prompt> prompt on most hardware. Press
<keycap>F3</keycap> to see the list of kernel options available
from which to boot. Just type your chosen flavor name (idepci,
vanilla, compact, bf24) at the <prompt>boot:</prompt> prompt
followed by &enterkey;.
</para><para>
If your hardware doesn't support booting of multiple images, put one
of the other CDs in the drive. It appears that most SCSI CD-ROM drives
do not support <command>isolinux</command> multiple image booting, so users
with SCSI CD-ROMs should try either CD2 (vanilla) or CD3 (compact),
or CD5 (bf2.4).
</para><para>
CD's 2 through 5 will each boot a
different ``flavor'' depending on which CD-ROM is
inserted. See <xref linkend="kernel-choice"/> for a discussion of the
different flavors. Here's how the flavors are laid out on the
different CD-ROMs:
<variablelist>
<varlistentry>
<term>CD 1</term><listitem><para>
Allows a selection of kernel images to boot from (the idepci flavor is
the default if no selection is made).
</para></listitem></varlistentry>
<varlistentry>
<term>CD 2</term><listitem><para>
Boots the `vanilla' flavor.
</para></listitem></varlistentry>
<varlistentry>
<term>CD 3</term><listitem><para>
Boots the `compact' flavor.
</para></listitem></varlistentry>
<varlistentry>
<term>CD 4</term><listitem><para>
Boots the `idepci' flavor.
</para></listitem></varlistentry>
<varlistentry>
<term>CD 5</term><listitem><para>
Boots the `bf2.4' flavor.
</para></listitem></varlistentry>
</variablelist>
</para><para>
-->
</sect2>
<!-- FIXME the documented procedure does not exactly work, commented out
until fixes
<sect2 arch="i386" id="install-from-dos">
<title>Booting from a DOS partition</title>
&boot-installer-intro-hd.xml;
<para>
Boot into DOS (not Windows) without any drivers being loaded. To do
this, you have to press <keycap>F8</keycap> at exactly the right
moment (and optionally select the `safe mode command prompt only'
option). Enter the subdirectory for the flavor you chose, e.g.,
<informalexample><screen>
cd c:\install
</screen></informalexample>.
Next, execute <command>install.bat</command>.
The kernel will load and launch the installer system.
</para><para>
Please note, there is currently a loadlin problem (#142421) which
precludes <filename>install.bat</filename> from being used with the
bf2.4 flavor. The symptom of the problem is an
<computeroutput>invalid compressed format</computeroutput> error.
</para>
</sect2>
END FIXME -->
<sect2 arch="i386" id="boot-initrd">
<title>Booting from linux using <command>LILO</command> or
<command>GRUB</command></title>
<para>
To boot the installer from hard disk, you must first download
and place the needed files as described in <xref linkend="boot-drive-files"/>.
</para>
<para>
If you intend to use the hard drive only for booting and then
download everything over the network, you should download the
<filename>netboot/debian-installer/i386/initrd.gz</filename> file and its corresponding kernel.
This will allow you
to repartition the hard disk from which you boot the installer, although
you should do so with care.
</para>
<para>
Alternatively, if you intend to keep an existing partition on the hard
drive unchanged during the install, you can download the
<filename>hd-media/initrd.gz</filename>
file and its kernel, as well as copy a CD iso to the drive (make sure the
file is named ending in ".iso". The installer can then boot from the drive
and install from the CD image, without needing the network.
</para>
<para>
For <command>LILO</command>, you will need to configure two
essential things in <filename>/etc/lilo.conf</filename>:
<itemizedlist>
<listitem><para>
to load the <filename>initrd.gz</filename> installer at boot time;
</para></listitem>
<listitem><para>
have the <filename>vmlinuz</filename> kernel use a RAM disk as
its root partition.
</para></listitem>
</itemizedlist>
Here is a <filename>/etc/lilo.conf</filename> example:
</para><para>
<informalexample><screen>
image=/boot/newinstall/vmlinuz
label=newinstall
initrd=/boot/newinstall/initrd.gz
root=/dev/ram0
append="devfs=mount,dall ramdisk_size=17000"
</screen></informalexample>
For more details, refer to the
<citerefentry><refentrytitle>initrd</refentrytitle>
<manvolnum>4</manvolnum></citerefentry> and
<citerefentry><refentrytitle>lilo.conf</refentrytitle>
<manvolnum>5</manvolnum></citerefentry> man pages. Now run
<userinput>lilo</userinput> and reboot.
</para><para>
The procedure for <command>GRUB</command> is quite similar. Locate your
<filename>menu.lst</filename> in the <filename>/boot/grub/</filename>
directory (sometimes in the <filename>/boot/boot/grub/</filename>),
add the following lines:
<informalexample><screen>
title New Install
kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 devfs=mount,dall ramdisk_size=17000
initrd (hd0,0)/boot/newinstall/initrd.gz
</screen></informalexample>
and reboot. Note that the value of the <userinput>ramdisksize</userinput>
may need to be adjusted for the size of the initrd image.
>From now on, there should be no difference between <command>GRUB</command>
or <command>LILO</command>.
</para>
</sect2>
<sect2 arch="i386" id="usb-boot">
<title>Booting from USB memory stick</title>
<para>
Lets assume you have prepared everything from <xref
linkend="boot-dev-select"/> and <xref linkend="boot-usb-files"/>. Now
just plug your USB stick into some free USB connector and reboot the
computer. The system should boot up, and you should be presented with
the <prompt>boot:</prompt> prompt. Here you can enter optional boot
arguments, or just hit &enterkey;.
</para><para>
In case your computer doesn't support booting from USB memory devices,
you can still use a single floppy to do the initial boot and then
switch to USB. Boot your system as described in <xref linkend="floppy-boot"/>;
the kernel on the boot floppy should detect your USB stick automatically.
When it asks for the root floppy, simply press &enterkey;. You should see
&d-i; starting.
</para>
</sect2>
<sect2 arch="i386" id="floppy-boot">
<title>Booting from Floppies</title>
<para>
You will have already downloaded the floppy images you needed and
created floppies from the images in <xref linkend="create-floppy"/>.
<!-- missing-doc FIXME If you need to, you can also modify the boot floppy; see
<xref linkend="rescue-replace-kernel"/>. -->
</para><para>
To boot from the installer boot floppy, place it in the primary floppy
drive, shut down the system as you normally would, then turn it back
on.
</para><para>
For installing from a LS-120 drive (ATAPI version) with a set of
floppies, you need to specify the virtual location for the floppy
device. This is done with the <emphasis>root=</emphasis> boot
argument, giving the device that the ide-floppy driver maps the device
to. For example, if your LS-120 drive is connected as the first IDE
device (master) on the second cable, you enter
<userinput>linux root=/dev/hdc</userinput> at the boot prompt.
Installation from LS-120 is only supported by 2.4 and later kernels.
</para><para>
Note that on some machines, <keycombo><keycap>Control</keycap>
<keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not
properly reset the machine, so a ``hard'' reboot is recommended. If
you are installing from an existing operating system (e.g., from a DOS
box) you don't have a choice. Otherwise, please do a hard reboot when
booting.
</para><para>
The floppy disk will be accessed, and you should then see a screen
that introduces the boot floppy and ends with the <prompt>boot:</prompt>
prompt.
</para><para>
Once you press &enterkey;, you should see the message
<computeroutput>Loading...</computeroutput>, followed by
<computeroutput>Uncompressing Linux...</computeroutput>, and
then a screenfull or so of information about the hardware in your
system. More information on this phase of the boot process can be
found below in <xref linkend="kernel-msgs"/>.
</para><para>
After booting from the boot floppy, the root floppy is
requested. Insert the root floppy and press &enterkey;, and the
contents are loaded into memory. The installer program
<command>debian-installer</command> is automatically launched.
</para>
</sect2>
<sect2 arch="i386" id="boot-tftp"><title>Booting with TFTP</title>
&boot-installer-intro-net.xml;
<para>
There are various ways to do a TFTP boot on i386.
</para>
<sect3><title>NIC or Motherboard that support PXE</title>
<para>
It could be that your Network Interface Card or Motherboard provides
PXE boot functionality.
This is a <trademark class="trade">Intel</trademark> re-implemention
of TFTP boot. If so you may be able to configure your BIOS to boot from the
network.
</para>
</sect3>
<sect3><title>NIC with network bootROM</title>
<para>
It could be that your Network Interface Card provides
TFTP boot functionality.
</para><para condition="FIXME">
Let us (<email>&email-debian-boot-list;</email>) know how did you manage it.
Please refer to this document.
</para>
</sect3>
<sect3><title>Etherboot</title>
<para>
The <ulink url="http://www.etherboot.org">etherboot project</ulink>
provides bootdiskettes and even bootroms that do a TFTPboot.
</para>
</sect3>
</sect2>
<sect2 arch="i386"><title>i386 Boot Parameters</title>
<para>
When the installer boots, you will be presented with the boot prompt,
<prompt>boot:</prompt>. You can do two things at the <prompt>boot:</prompt>
prompt. You can press the function keys <keycap>F1</keycap> through
<keycap>F10</keycap> to view a few pages of helpful information, or
you can press <keycap>Enter</keycap> to boot the system.
</para><para>
Information on boot parameters which might be useful can be found by
pressing <keycap>F3</keycap> through <keycap>F7</keycap>. If you add any
parameters to
the boot command line, be sure to type the boot method (the default is
<userinput>linux</userinput>) and a space before the first parameter (e.g.,
<userinput>linux floppy=thinkpad</userinput>). If you simply press &enterkey;,
that's the same as typing <userinput>linux</userinput> without any special
parameters.
</para><para>
Some systems have floppies with ``inverted DCLs''. If you receive
errors reading from the floppy, even when you know the floppy is good,
try the parameter <userinput>floppy=thinkpad</userinput>.
</para><para>
On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506
disk drivers), the IDE drive may not be properly recognized. Again,
try it first without the parameters and see if the IDE drive is
recognized properly. If not, determine your drive geometry
(cylinders, heads, and sectors), and use the parameter
<userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>.
</para><para>
If you have a very old machine, and the kernel hangs after saying
<computeroutput>Checking 'hlt' instruction...</computeroutput>, then
you should try the <userinput>no-hlt</userinput> boot argument, which
disables this test.
</para><para>
If your screen begins to show a weird picture while the kernel boots,
eg. pure white, pure black or colored pixel garbage, your system may
contain a problematic video card which does not switch to the
framebuffer mode properly. Then you can use the boot parameter
<userinput>debian-installer/framebuffer=false</userinput> or
<userinput>video=vga16:off</userinput> to disable the framebuffer
console. Only the English
language will be available during the installation due to limited
console features. See <xref linkend="boot-parms"/> for details.
</para>
</sect2>
<sect2 arch="i386">
<title>System freeze during the PCMCIA configuration phase</title>
<para>
Some laptop models produced by Dell are known to crash when PCMCIA device
detection tries to access some hardware addresses. Other laptops may display
similar problems. If you experience such a problem and you don't need PCMCIA
support during the installation, you can disable PCMCIA using the
<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can
then configure PCMCIA after the installation is completed and exclude the
resource range causing the problems.
</para><para>
Alternatively, you can boot the installer in expert mode. You will
then be asked to enter the resource range options your hardware
needs. For example, if you have one of the Dell laptops mentioned
above, you should enter <userinput>exclude port
0x800-0x8ff</userinput> here. There is also a list of some common
resource range options in the <ulink
url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">System
resource settings section of the PCMCIA HOWTO</ulink>. Note that you
have to omit the commas, if any, when you enter this value in the
installer.
</para>
</sect2>
<sect2 arch="i386">
<title>System freeze while loading the USB modules</title>
<para>
The kernel normally tries to install USB modules and the USB keyboard driver
in order to support some non-standard USB keyboards. However, there are some
broken USB systems where the driver hangs on loading. A possible workaround
may be disabling the USB controller in your mainboard BIOS setup. Another option
is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter
at the boot prompt, which will prevent the modules from being loaded.
</para>
</sect2>
<!-- retain these comments for translator revision tracking -->
<!-- original version: 21579 -->
<sect3 id="baseconfig">
<title>Running <command>base-config</command> From Within &d-i;</title>
<para>
It is possible to configure the base system within the first stage
installer (before rebooting from the hard drive), by running
<command>base-config</command> in a <firstterm>chroot</firstterm>
environment. This is mainly useful for testing the installer and a
vast majority of people should avoid it.
<!-- Feel free to prove me I'm wrong -->
</para>
</sect3>
# Debian GNU/Linux Installation Guide
# Original translator szjungle, 2004.
#
msgid ""
msgstr ""
"Project-Id-Version: d-i-manaul\n"
"POT-Creation-Date: 2005-01-21 4:19+1300\n"
"PO-Revision-Date: 2005-01-08 18:51+0800\n"
"Last-Translator: Jungle Ji <jungle(a)soforge.com>\n"
"Language-Team: debian-chinese-gb <debian-chinese-gb(a)lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
# type: Content of: outside any tag (error?)
#: en/using-d-i/modules/baseconfig.xml:1
#, no-wrap
msgid "\n"
msgstr "\n"
# type: Content of: outside any tag (error?)
#: en/using-d-i/modules/baseconfig.xml:2
#, no-wrap
msgid ""
"\n"
"\n"
" "
msgstr ""
"\n"
"\n"
" "
# type: Content of: <sect3>
#: en/using-d-i/modules/baseconfig.xml:4
#, no-wrap
msgid ""
"\n"
" "
msgstr ""
"\n"
" "
# type: Content of: <sect3><title>
#: en/using-d-i/modules/baseconfig.xml:5
#, no-wrap
msgid "Running "
msgstr "??? &d-i; ???????????? "
# type: Content of: <sect3><para><command>
#: en/using-d-i/modules/baseconfig.xml:5
#: en/using-d-i/modules/baseconfig.xml:11
#, no-wrap
msgid "base-config"
msgstr "base-config"
# type: Content of: <sect3><title>
#: en/using-d-i/modules/baseconfig.xml:5
#, no-wrap
msgid " From Within &d-i;"
msgstr " "
# type: Content of: <sect3>
#: en/using-d-i/modules/baseconfig.xml:5
#, no-wrap
msgid ""
"\n"
"\n"
msgstr ""
"\n"
"\n"
# type: Content of: <sect3><para>
#: en/using-d-i/modules/baseconfig.xml:7
#, no-wrap
msgid ""
"\n"
"\n"
"It is possible to configure the base system within the first stage\n"
"installer (before rebooting from the hard drive), by running\n"
msgstr ""
"\n"
"?????????????????????????????????????????????????????????????????? (????????????????????????)???\n"
"??????\n"
# type: Content of: <sect3><para>
#: en/using-d-i/modules/baseconfig.xml:11
#, no-wrap
msgid " in a "
msgstr " ??? "
# type: Content of: <sect3><para><firstterm>
#: en/using-d-i/modules/baseconfig.xml:11
#, no-wrap
msgid "chroot"
msgstr "chroot"
# type: Content of: <sect3><para>
#: en/using-d-i/modules/baseconfig.xml:11
#, fuzzy, no-wrap
msgid ""
"\n"
"environment. This is mainly useful for testing the installer and a\n"
"vast majority of people should avoid it.\n"
msgstr ""
"\n"
"???????????????????????????????????????????????????\n"
"??????????????????????????????????????????\n"
<!-- retain these comments for translator revision tracking -->
<!-- original version: 21579 -->
<sect3 id="baseconfig">
<title>??? &d-i; ???????????? <command>base-config</command> </title>
<para>
?????????????????????????????????????????????????????????????????? (????????????????????????)???
??????
<command>base-config</command> ??? <firstterm>chroot</firstterm>
environment. This is mainly useful for testing the installer and a
vast majority of people should avoid it.
<!-- Feel free to prove me I'm wrong -->
</para>
Feel free to prove me I'm wrong -->
-->
<!-- retain these comments for translator revision tracking -->
<!-- original version: 22664 -->
<sect3 id="os-prober">
<title>Detecting other operating systems</title>
<para>
Before a boot loader is installed, the installer will attempt to probe for
other operating systems which are installed on the machine. If it finds a
supported operating system, you will be informed of this during the boot
loader installation step, and the computer will be configured to boot this
other operating system in addition to Debian.
</para><para>
Note that multiple operating systems booting on a single machine is still
something of a black art. The automatic support for detecting and setting
up boot loaders to boot other operating systems varies by architecture and
even by subarchitecture. If it does not work you should consult your
boot manager's documentation for more information.
<!-- TODO: Maybe include some arch-dependent tables with supported OS'es here -->
</para>
<note><para>
The installer may fail to detect other operating systems if the partitions on
which they reside are mounted when the detection takes place. This may occur if
you select a mountpoint (e.g. /win) for a partition containing another operating
system in <command>partman</command>, or if you have mounted partitions manually
from a console.
</para></note>
</sect3>
<!-- retain these comments for translator revision tracking -->
<!-- original version: 22664 -->
<sect3 id="os-prober">
<title>???????????????????????????</title>
<para>
???????????????????????????????????????????????????????????????????????????????????????????????????????????????
?????????????????????????????????????????????????????????????????????????????????????????????
??? Debian ??????????????????????????????????????????????????????????????????
</para><para>
?????????????????????????????????????????????????????????????????????
???????????????????????????????????????????????????????????????????????????????????????????????????????????????
????????????????????????????????????????????????????????????????????????????????????
<!-- TODO: Maybe include some arch-dependent tables with supported OS'es here -->
</para>
<note><para>
The installer may fail to detect other operating systems if the partitions on
which they reside are mounted when the detection takes place. This may occur if
you select a mountpoint (e.g. /win) for a partition containing another operating
system in <command>partman</command>, or if you have mounted partitions manually
from a console.
</para></note>
TODO: Maybe include some arch-dependent tables with supported OS'es here -->
-->
# SOME DESCRIPTIVE TITLE
# Original translator szjungle, 2004.
#
msgid ""
msgstr ""
"Project-Id-Version: d-i-manual\n"
"POT-Creation-Date: 2005-01-21 5:07+1300\n"
"PO-Revision-Date: 2004-12-09 11:52+0800\n"
"Last-Translator: Jungle Ji <jungle(a)soforge.com>\n"
"Language-Team: debian-chinese-gb <debian-chinese-gb(a)lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
# type: Content of: outside any tag (error?)
#: en/using-d-i/modules/os-prober.xml:1
#, no-wrap
msgid "\n"
msgstr "\n"
# type: Content of: outside any tag (error?)
#: en/using-d-i/modules/os-prober.xml:2
#, no-wrap
msgid ""
"\n"
"\n"
" "
msgstr ""
"\n"
"\n"
" "
# type: Content of: <sect3>
#: en/using-d-i/modules/os-prober.xml:4
#, no-wrap
msgid ""
"\n"
" "
msgstr ""
"\n"
" "
# type: Content of: <sect3><title>
#: en/using-d-i/modules/os-prober.xml:5
#, no-wrap
msgid "Detecting other operating systems"
msgstr "???????????????????????????"
# type: Content of: <sect3>
#: en/using-d-i/modules/os-prober.xml:5
#, no-wrap
msgid ""
"\n"
"\n"
msgstr ""
"\n"
"\n"
# type: Content of: <sect3><para>
#: en/using-d-i/modules/os-prober.xml:7
#, no-wrap
msgid ""
"\n"
"\n"
"Before a boot loader is installed, the installer will attempt to probe for\n"
"other operating systems which are installed on the machine. If it finds a\n"
"supported operating system, you will be informed of this during the boot\n"
"loader installation step, and the computer will be configured to boot this\n"
"other operating system in addition to Debian.\n"
"\n"
msgstr ""
"\n"
"???????????????????????????????????????????????????????????????????????????????????????????????????????????????\n"
"?????????????????????????????????????????????????????????????????????????????????????????????\n"
"??? Debian ??????????????????????????????????????????????????????????????????\n"
# type: Content of: <sect3><para>
#: en/using-d-i/modules/os-prober.xml:15
#, no-wrap
msgid ""
"\n"
"\n"
"Note that multiple operating systems booting on a single machine is still\n"
"something of a black art. The automatic support for detecting and setting\n"
"up boot loaders to boot other operating systems varies by architecture and\n"
"even by subarchitecture. If it does not work you should consult your\n"
"boot manager's documentation for more information.\n"
"\n"
msgstr ""
"\n"
"\n"
"?????????????????????????????????????????????????????????????????????\n"
"???????????????????????????????????????????????????????????????????????????????????????????????????????????????\n"
"????????????????????????????????????????????????????????????????????????????????????\n"
"\n"
# type: Content of: <sect3><note><para>
#~ msgid ""
#~ "\n"
#~ "\n"
#~ "The installer may fail to detect other operating systems if the "
#~ "partitions on\n"
#~ "which they reside are mounted when the detection takes place. This may "
#~ "occur if\n"
#~ "you select a mountpoint (e.g. /win) for a partition containing another "
#~ "operating\n"
#~ "system in "
#~ msgstr ""
#~ "\n"
#~ "????????????????????????????????????????????????????????????????????????????????????????????????\n"
#~ "??????????????????????????? "
# type: Content of: <sect3><note><para><command>
#~ msgid "partman"
#~ msgstr "partman"
# type: Content of: <sect3><note><para>
#~ msgid ""
#~ ", or if you have mounted partitions manually\n"
#~ "from a console.\n"
#~ "\n"
#~ msgstr ""
#~ " ??????????????????(??? /win)???????????????????????????????????????????????????????????????????????????\n"
----- End forwarded message -----
19 years, 9 months
[Po4a-devel]Re: [Po4a-commits] po4a/lib/Locale/Po4a TeX.pm,1.5,1.6
by Martin Quinson
Waa, that's impressive! What are your plan for the future? Did you reach a
releasable state, or do you what to improve furter your code? We're on your
order on this one ;) Could you please update the changelog?
As usual, I'm really impressed here.
Thanks for your time, Mt.
On Sat, Jan 08, 2005 at 10:44:30AM +0000, Nicolas FRAN??OIS wrote:
> Update of /cvsroot/po4a/po4a/lib/Locale/Po4a
> In directory haydn:/tmp/cvs-serv9174/lib/Locale/Po4a
>
> Modified Files:
> TeX.pm
> Log Message:
> Some cleanups and comments.
> New functionnalities:
> * Better handling of the spaces surrounding commands. They are now kept as close to the original as possible.
> * Start using "% po4a: " line for parser personalisation.
> * It is now possible to build a derivated parser.
> * Handle file inclusion (based on Transtractor's read).
19 years, 9 months
[Po4a-devel]Translating NEWS.Debian files: a (crude) first try
by Martin Quinson
Hello,
I just commited two new modules to the cvs of the po4a project (on alioth).
The first one (NewsDebian.pm) is good to extract/translate debian
changelogs. Its main goal is to deal with the "NEWS.Debian" files. They
follow the "debian changelog" format explained in the policy and are where
the developper should put the important news about their package. Such as
"conf file moved" or "semantic changed" or such. They are then parsed by
apt-listchanges before the installation and the user is given the ability to
refuse the upgrade if those news are too bad.
Since a long time, we try to get those files translated, but the way to do
so was not clear.
I decided to distribute a bunch of files in the package, each called
NEWS.Debian.<lang code>. This has the advantage of not breaking the existing
softwares (precious when acting so close from a release). In other words, I
assume that apt-listchanges will choose which file to display depending on
the user's locale.
To generate those files, I naturally decided to use po4a and thus wrote this
module.
The next issue to solve was to that po-debconf uses the debian/po directory,
which I thus have to share with him. I decided not to share anything and
play an embrace&extend game (*). The second module tries to do the
po-debconf work of extraction. It is not really tested, but it's already too
late. Let's assume it works for now and take is as a proof of concept.
(*): remember that po-debconf was done by Denis and that po4a is done by
Denis, Jordi, Nekral and me ;)
Now, we could add po4a.conf files in each package like this:
>>>>>>>
# first explain where are the transaltor input files
[po4a_paths] debian/po/debian.pot fr:debian/po/fr.po \
de:debian/po/de.po \
es:debian/po/es.po
# Then list the document to translate, their format, their translations
[type: debconf] templates
[type: newsdebian] debian/README.Debian fr:tmp/DEBIAN/README.Debian.fr \
de:tmp/DEBIAN/README.Debian.de \
es:tmp/DEBIAN/README.Debian.es
<<<<<<<<
and then add an invocation to po4a -f debian/po4a.conf to debian/rules and
we're set.
At least that's the plan. Some comments before I fall asleep:
* I did almost no testing.
* the Debconf module is unable to generate template files for now.
The core of po4a in unable to put more than one translation in each
produced document, but this is mandatory for debconf.
The way I want to use to solve it is described at the end of the
Locale::Po4a::TransTractor man page. The module already takes this path.
Intead of calling $self->pushline($self->translate()) directly, it put
those calls into a string which could be eval()uated in a loop for each
language. [sorry for the one not knowing the po4a internals, I just
wanted to explain the others]
But we could use po4a for extraction (to get the right content into
debian/po) and po-debconf for template generation (to get the right
content into the package) without problems [that I could predict ;]
* the NewsDebian is not really cleaver and put each entry into one msgid in
no-wrap mode without trying to split each points. Example:
# type: dictd (1.9.11-1) unstable; urgency=low
#
#: dict:20
#, no-wrap
msgid ""
" * dict.conf has moved from /etc to /etc/dictd.\n"
"\n"
" * The plugin shared libraries and example plugins are nolonger\n"
" shipped with the dictd binary. If you wish to experiment with\n"
" plugins see /usr/share/doc/dictd/README.Plugins.gz.\n"
msgstr ""
Well, those files are not supposed to change *at all*, actually. And the
format within each entry is not completely fixed and maintainers sometimes
take some liberty. I wanted to play safe.
That's pretty much it, I guess.
Mt.
19 years, 9 months
[Po4a-devel]Re: [Po4a-commits] po4a/debian changelog,1.133,1.134
by Denis Barbier
On Fri, Jan 28, 2005 at 09:39:04PM +0000, Jordi Vilalta wrote:
> Update of /cvsroot/po4a/po4a/debian
> In directory haydn:/tmp/cvs-serv6115/debian
>
> Modified Files:
> changelog
> Log Message:
> Fix the reported d-i's manual issues in Xml.pm
Many thanks, Jordi, that works!
If you look at the end of the PO file generated with
1_en_boot-installer_i386.xml, you see
"is passing the "
msgstr ""
# type: Content of: <sect2><para><userinput>
#: 1_en_boot-installer_i386.xml:323
#, no-wrap
msgid "debian-installer/probe/usb=false"
msgstr ""
# type: Content of: <sect2><para>
#: 1_en_boot-installer_i386.xml:323
#, no-wrap
msgid ""
" parameter\n"
"at the boot prompt, which will prevent the modules from being loaded.\n"
"\n"
msgstr ""
Obviously the last 3 msgids should be merged into a single one, can you
please explain how to customize the XML module to change how tags are
interpreted? Here I would like to change <userinput> definition to have
it inlined.
Denis
19 years, 10 months
[Po4a-devel]Gettextizing multiple files at a time
by Jordi Vilalta
Hi,
today I've tried to gettextize a collection of files at a time (I didn't
try it before) and I've found that po4a-gettextize only accepts one file
at a time. I think it's an annoying limit, that could be enhanced handling
the input files like po4a-updatepo does.
Martin, you gettextized the Perl documentation... did you use an external
script or am I missing something?
If you think it's a good idea to implement the multiple-files input, I can
do it (now I'll have some semi-vacation days ;)
Regards,
Jordi Vilalta
19 years, 10 months
Re: [Po4a-devel]Documentation review (fwd)
by Jordi Vilalta
Hi,
Today I was updating the catalan documentation and I've found a posible update
in the original:
diff -u -r1.31 po4a.7.pod
--- doc/po4a.7.pod 6 Nov 2004 19:08:01 -0000 1.31
+++ doc/po4a.7.pod 25 Dec 2004 19:26:05 -0000
@@ -872,7 +872,7 @@
Yes, in po4a, each paragraphs are translated separately (in fact, each
module decides this, but all existing modules do so, and yours should also).
-There is two main advantages to this approach:
+There are two main advantages to this approach:
=over 2
This made me remember the documentation review we were talking about one month
ago. Are there any news? Should this patch be added to the complete review? (I
don't remember if it was already there).
Regards,
Jordi Vilalta
19 years, 10 months
