Xhtml: SSI comment included in translations
by poy
hi,
i've been playing with the "includessi" option from the Xhtml module
recently, and it's working very well!
between <body> and </body>, i add:
<!--#include virtual="commands_user.inc" -->
and the contents of that file are correctly translated and included.
the tag is changed into a simple comment:
<!-- SSI included by po4a: virtual="commands_user.inc" -->
followed by the translated contents of the included file.
all good, but i have one little (non-)issue; in the translation template,
the following translation is added:
#. type: Content of: <html><body>
#: help/commands_user.html:15 help/window_hub.html:45
msgid "<!-- SSI included by po4a: virtual=\"commands_user.inc\" -->"
msgstr ""
obviously this is not to be translatable; when i add a comment between
<body> and </body>, eg:
<!-- blah -->
the comment is ignored by po4a and doesn't end up in the translation file.
so it's a little odd that the SSI comment does end up in there...
could this be checked please?
thanks,
poy
15 years, 9 months
po4a with markdown
by Dongsheng Song
Here is the source:
## Glossary ##
Here we have the meanings of some terms used into Git context.
These terms were entirely copied from
[Git Glossary](http://www.kernel.org/pub/software/scm/git/docs/gitglossary.html).
After I run 'po4a-updatepo -M UTF-8 -f text -o markdown -m
../text/55_Glossary/0_Glossary.markdown -p test.po',
generate a po file with '\r' and extra space:
#. type: Plain text
#: ../text/55_Glossary/0_Glossary.markdown:1
#, no-wrap
msgid "## Glossary ##\r\n"
msgstr ""
#. type: Plain text
#: ../text/55_Glossary/0_Glossary.markdown:6
msgid ""
"Here we have the meanings of some terms used into Git context. \r These "
"terms were entirely copied from \r [Git Glossary](http://www.kernel.org/pub/"
"software/scm/git/docs/gitglossary.html). \r"
msgstr ""
Why po4a generate '\r' instead of '\n', and add extra space ?
---
Dongsheng Song
15 years, 10 months
Mailing List of Hospitals, emergency medicine physicians, Medical Equipment Suppliers and much more
by Milligan 6 Louella
Practicing Physicians in the United States
Doctor in over 38 specialties
Can easily be sorted by 16 different fields
Reduced to only: $398
=== Buy this week and get these bonus information directories: ()()()
>> Chiropractors
+ Physical Therapists
++ Massage Therapists
++> Acupuncturists
reply by email:: Enriquez(a)maximumlist.com
only during this week ============== to terminate please send a blank message to rem6(a)maximumlist.com
15 years, 10 months
allow TransTractor to pass PO options
by poy
attached patch allows TransTractor to pass "package-name" and similar
PO-related options (parsed by the Po module) when calling po4a-gettextize.
otherwise, it's impossible to define these options because the first module
loaded by TransTractor (eg, Xml) will deem these options as invalid.
i simply duplicated what was already being done for the "porefs" option.
poy
15 years, 10 months
XML: prevent some attributes from being translated
by poy
hi,
i am using the XHTML module from po4a, and i would like to specify
attributes that i don't want to be translated.
i do know about the "untranslated" option, which i already use in some
places, but that option only applies to tags. here i would like to ignore
modifications done by translators on attributes of an inline tag.
example: the text "abc <a href=\"file.html\" target=\"_blank\"
title=\"link-name\"> def". as of now, the text appears as is in the .pot
file, and if a translator mistakenly translates \"file.html\" into
\"translated_name.html\", then the link will point to a non-existing page.
when a translator translates that text to "abc_translated <a
href=\"file_translated.html\" target=\"wrong_target\"
title=\"link-name_translated\"> def_translated", i would like modifications
to the "href" and "target" attributes to be ignored. or as an alternative
solution, simply exit po4a with an error stating that the translation file
is incorrect.
i assume there is no current way of doing it; i could try, but i don't know
Perl much and even less po4a. i have noticed the recent work on the XHTML
module (thanks for <br> and <u>, much appreciated!), so i was hoping a po4a
maintainer could give this a try.
otherwise, i would like pointers on where to start...
thanks,
poy
15 years, 10 months
medical industry email lists
by Goodson N Colin
These are mixed general email lists perfect for bulk email campaigns. There are doctors, dentists, treatment centers, clinics, billers, coders etc.. It's a nice mix of everything but there are no names or any other fields other than emails. Deliverability is high (80%) since these are very fresh emails.
1,000,000 emails - only $150.00
contact: Roe(a)statlists.com
have a look at this if you don't like to recieve these kinds of emails please email delete9(a)statlists.com
15 years, 10 months
Bad string location in po files
by Dongsheng Song
For example, we put source in 'en', po files in 'po':
% cd en && po4a-updatepo -o includeexternal -m book.xml -p ../po/zh.po
The string location in zh.po is not correct:
#: ch05-repository-admin.xml:2705
msgid "svnsync Bookkeeping"
The po tools, like Poedit, can not display source reference.
It should be:
#: ../en/ch05-repository-admin.xml:2705
msgid "svnsync Bookkeeping"
Then the po tools, like Poedit, can display source reference
correctly.
PS: Resolve external in book.xml, the path should relative to book.xml,
not current directory.
---
Dongsheng Song
15 years, 10 months
Re: [Po4a-devel] Preparation of the next po4a 0.36 release
by Nicolas François
On Thu, Mar 05, 2009 at 09:38:53AM +0900, fusion(a)mx6.tiki.ne.jp wrote:
>
> On jeudi 05 mars 09, at 09:13, Nicolas François wrote:
>
>> Hello,
>>
>> On Wed, Mar 04, 2009 at 11:49:55PM +0100,
>> nicolas.francois(a)centraliens.net wrote:
>>>
>>> Last version (0.35) was released less than one month ago, but there
>>> has
>>> been lots of changes and bugfixes that would need to go in the wild.
>>>
>>> I intend to release po4a 0.36 in about 10 days (March 15, 22:00 UTC).
>>
>> Only the mail Subject was wrong. The next release will be numbered
>> 0.36.
>
> Did you have time to see the installation problem on OSX 10.5.6 ?
This is still unsure. As I do not have such platform.
My old iBook had no problems with the installation.
I will re-contact you this weekend to check how I could install some newer
Perl on OSX (maybe with mac port) and check if I can reproduce the issue.
If a Perl developer on the list has an OSX, please raise your hand.
Best Regards,
--
Nekral
15 years, 10 months
