From: "Ineiev via RT" <web-translators@gnu.org>
To: john@darrington.wattle.id.au, karl@freefriends.org, ludo@gnu.org
Cc: guix-devel@gnu.org, bug-womb@gnu.org
Subject: Re: [gnu.org #881181] Re: [gnu.org #881518] Re: Package synopses and blurbs translation
Date: Fri, 10 Jan 2014 00:44:25 -0500 [thread overview]
Message-ID: <rt-3.4.5-22704-1389332664-1203.881181-5-0@rt.gnu.org> (raw)
In-Reply-To: <52CF88ED.7040805@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]
On 01/10/2014 03:12 AM, Ludovic Courtès via RT wrote:
>>
>> (0) when a new (or corrected) translation is committed to www, www
>> translators send updates to TP, and they merge it to their PO files;
>>
>> (1) when a new translation is submitted to TP, the translators send
>> a copy to the respective www.gnu.org translation team (or
>> web-translators@gnu.org if that team doesn't maintain blurb
>> translation for some reason); of course, TP translators should know
>> what strings are blurbs.
>
> Sounds good.
>
> What would it take exactly to inform the TP folks of the process?
Discuss with coordinator@translationproject.org, I think; they may add
their own adjustments to the procedure before actually announcing it
to the translators.
>> However, there is a technical problem: www translations are in HTML,
>> while guix uses plain text. it's easy to transform plain text to HTML;
>> the reverse conversion seems missing.
>
> Seems to me that the only difference in the translated strings is that
> the www ones have something like this at the end:
>
> <small>(<a href="/manual/manual.html#pkg_3dldf\">doc</a>)</small>
>
> Would it be possible somehow to remote that link from the translatable
> strings?
But they are translatable; what may make sense is separating them
to their own msgids (also, "This package is looking for a maintainer.").
GNUN has a means to do it when the strings can't come, say, in separate
paragraphs, <span class="gnun-split"></span>, like on the home page [0],
so this could be implemented like in the attachment.
Then, there are also <tt>s (which may "translate" into something
different, like <code> or <em>) and a few other substitutions [1].
I wonder whether it would be easier if guix used HTML in PO files and
converted it to plain text when needed; this way, no exact reverse
conversion would be necessary.
[0] https://www.gnu.org/home.en.html
[1] http://cvs.savannah.gnu.org/viewvc/gnumaint/gm-generate.pl?root=womb&view=markup
[-- Attachment #2: gm-generate.pl.diff --]
[-- Type: text/x-patch, Size: 895 bytes --]
Index: gm-generate.pl
===================================================================
RCS file: /sources/womb/gnumaint/gm-generate.pl,v
retrieving revision 1.15
diff -U 2 -r1.15 gm-generate.pl
--- gm-generate.pl 5 Nov 2013 14:41:52 -0000 1.15
+++ gm-generate.pl 10 Jan 2014 05:25:43 -0000
@@ -411,9 +411,11 @@
# let's advertise if the package is looking for a maintainer. maybe
# we'll find someone.
- push (@ret, "This package is looking for a maintainer.")
+ push (@ret, qq!<span class="gnun-split"></span>!
+ . "This package is looking for a maintainer.")
if $activity =~ /^nomaint/;
my $doc_links = "/manual/manual.html#$xhtml_id";
- push (@ret, qq!<small>(<a href="$doc_links">doc</a>)!
+ push (@ret, qq!<span class="gnun-split"></span>!
+ . qq!<small>(<a href="$doc_links">doc</a>)!
. qq!</small></p>!);
next prev parent reply other threads:[~2014-01-10 5:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-881181@rt.gnu.org>
[not found] ` <RT-Ticket-881518@rt.gnu.org>
2014-01-06 17:41 ` Package synopses and blurbs translation Ludovic Courtès
2014-01-06 21:52 ` [bug-womb] " Karl Berry
2014-01-07 8:57 ` John Darrington
2014-01-07 10:17 ` Ludovic Courtès
2014-01-07 10:31 ` John Darrington
2014-01-07 23:00 ` Ludovic Courtès
[not found] ` <rt-3.4.5-19728-1389135974-1094.881518-21-0@rt.gnu.org>
[not found] ` <52CE264A.8010501@gmail.com>
2014-01-09 4:31 ` [gnu.org #881181] Re: [gnu.org #881518] " Ineiev via RT
2014-01-09 10:51 ` Ludovic Courtès
2014-01-09 10:57 ` Ludovic Courtès via RT
[not found] ` <rt-3.4.5-21633-1389265036-650.881181-75-0@rt.gnu.org>
[not found] ` <52CE8766.4080501@gmail.com>
2014-01-09 11:25 ` Ineiev via RT
2014-01-09 11:33 ` John Darrington
2014-01-09 11:33 ` John Darrington via RT
2014-01-09 13:24 ` Ludovic Courtès
2014-01-09 13:29 ` Ludovic Courtès via RT
[not found] ` <rt-3.4.5-11749-1389274177-1282.881181-75-0@rt.gnu.org>
[not found] ` <52CEB6A9.2000105@gmail.com>
2014-01-09 14:48 ` Ineiev via RT
2014-01-09 23:06 ` Ludovic Courtès
2014-01-09 23:12 ` Ludovic Courtès via RT
[not found] ` <rt-3.4.5-23172-1389309154-685.881181-75-0@rt.gnu.org>
[not found] ` <52CF88ED.7040805@gmail.com>
2014-01-10 5:44 ` Ineiev via RT [this message]
2014-01-10 13:11 ` Ludovic Courtès
2014-01-10 13:17 ` Ludovic Courtès via RT
[not found] ` <rt-3.4.5-26448-1389359836-1535.881181-75-0@rt.gnu.org>
[not found] ` <52D005CA.8020601@gmail.com>
2014-01-10 14:38 ` Ineiev via RT
2014-01-10 22:25 ` Karl Berry
2014-01-10 22:25 ` Karl Berry via RT
2014-01-11 10:16 ` Ludovic Courtès
2014-01-11 10:21 ` Ludovic Courtès via RT
[not found] ` <rt-3.4.5-20502-1389435706-1287.881181-75-0@rt.gnu.org>
[not found] ` <52D1231B.2090304@gmail.com>
2014-01-11 10:55 ` Ineiev via RT
2014-01-11 23:34 ` [bug-womb] " Karl Berry
2014-01-11 23:34 ` Karl Berry via RT
2014-01-12 6:38 ` John Darrington
2014-01-12 6:39 ` John Darrington via RT
2014-02-14 6:24 ` [gnu.org #881181] " Ineiev via RT
2014-02-14 11:02 ` Ludovic Courtès
2014-02-14 11:03 ` Ludovic Courtès via RT
2014-02-15 11:50 ` Ineiev via RT
2014-02-15 21:04 ` Ludovic Courtès
2014-02-15 21:05 ` Ludovic Courtès via RT
2014-02-14 22:46 ` [bug-womb] " Karl Berry
2014-02-14 22:46 ` Karl Berry via RT
2014-01-10 13:20 ` [gnu.org #881181] Re: [gnu.org #881518] " John Darrington
2014-01-10 13:20 ` John Darrington via RT
[not found] ` <rt-3.4.5-26199-1389360045-1423.881181-75-0@rt.gnu.org>
[not found] ` <52D004D8.4090005@gmail.com>
2014-01-10 14:34 ` Ineiev via RT
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rt-3.4.5-22704-1389332664-1203.881181-5-0@rt.gnu.org \
--to=web-translators@gnu.org \
--cc=bug-womb@gnu.org \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
--cc=karl@freefriends.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.