Simplified Chinese translation for po4a
by hottea
hi,
dear all.
I'm not sure if I have join this mail list. I don't know how to join as there isn't a how-to on the website. I hope you can receive my email.
I found po4a when doing some translation, and found that there's not a complete Simplified Chinese translation for po4a, so I do the work. I create a project on transifex, a localization platform, see www.transifex.com/projects/p/po4a-translation. I wonder how could I see the final result? Where are the translation installed?
If you're interested in the Simplified Chinese translation for po4a, please join the language team on transifex.com, you can also request language on transifex.
-----
send from hottea's openSUSE
3 years, 9 months
avis de l0t !!! 150.000
by tumu
Grace a votre adresse
email, vous a été tiré au sort par le logiciel Microsoft Windows pour être heureux(se)
gagnant(e) des 150.000EUROS DE LA WINDOWS PRO.
Votre numero
identifiant gagnant est le suivant 007095M83l
Notre huissier
accrédite superviseur vous indiquera la procedure pour la recuperation du gain,
ainsi priez de le contacter via ses coordonnees ci-dessous :
CABINET LENOIR &
ASSOCIES
Email: cabinet.lenoir(a)outlook.fr
IMPORTANT: Veuillez
imperativement renseigner le formulaire ci-dessous et faites le suivre par
courrier email au cabinet de l'huissier afin d’entamer les formalités relatives
a la recuperation du gain:
Nom.........................
Prenoms
.......................
Adresse:.......................
Tel/Fixe......................
Email........................
Profession....................
Direction des operations Windws Pro 2015
Copyright © 2015 Data Solutions - All Rights Reserved
9 years, 6 months
po4a-gettextize outputs wrong context comment in resulting .po file
by malex
Dear po4a developers,
thanks for your tool!
I am trying to use it to translate some latex files and found the
following problem:
If anybody have multiple master documents and one of them has no EOL
before EOF then
(in case of TeX and LaTeX format) its last paragraph (which had no
finishing EOL) will be merged together with the leading paragraph of
the following master document.
The text and asciidoc formats do NOT display this behavior.
Please find a small test attached.
ps: i currently workaround this problem by adding EOL before EOF to
ALL master documents...
ps2: just in case: EOL=end of line character, EOF=end of file
Sincerely Yours,
Alex
9 years, 6 months
Notice to appear in Court #00000970728
by State Court
Notice to Appear,
You have to appear in the Court on the April 18.
Please, prepare all the documents relating to the case and bring them to Court on the specified date.
Note: The case will be heard by the judge in your absence if you do not come.
You can find the Court Notice is in the attachment.
Kind regards,
Ricky Woodward,
Clerk of Court.
9 years, 6 months
[po4a-Bugs][315040] [patch] fix path to man pages when '--install_path man' is specified
by po4a-bugs＠alioth.debian.org
po4a-Bugs item #315040, was opened at 2015-04-06 14:57 by John Hein
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=315040&gro...
Status: Open
Priority: 3
Submitted By: John Hein (gettowork-guest)
Assigned to: Nobody (None)
Summary: [patch] fix path to man pages when '--install_path man' is specified
Category: None
Group: None
Resolution: None
Initial Comment:
If you call Build.PL with --install_path bindoc=/some/different/path, that path will not be where man pages go when you run 'Build install'. Instead it uses the man page installation directory from the default perl configuration.
'--install_path lib' and '--install_path bin' work as expected. But the bindoc specification is used in Po4aBuilder.pm's ACTION_install to override Module::Build's normal handling for some man pages. However, the man pages do not go to the install_path for bindoc specified by the command line --install_path option.
The attached patch attempts to fix the situation by using the 'install_path' set of directories when processing the mandir location.
To repeat the observed problem, try configuring by using something like the following:
perl Build.PL --destdir=/tmp --install_path lib=/some_nonexistent_temp_dir/lib/perl/site_perl --install_path bin=/some_nonexistent_temp_dir/bin --install_path script=/some_nonexistent_temp_dir/bin --install_path bindoc=/some_nonexistent_temp_dir/man/man1 --install_path libdoc=/some_nonexistent_temp_dir/lib/perl/site_perl/man/man3 --install_path man=/some_nonexistent_temp_dir/lib/perl/site_perl/man
Then install using:
perl Build --destdir=/tmp
Notice that some of the man pages are not installed under /tmp/some_nonexistent_temp_dir
----------------------------------------------------------------------
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=315040&gro...
9 years, 6 months
