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 …
[View More]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
[View Less]
4 years, 2 months
Re: [Po4a-devel] Bug#827936: po4a: please implement support for Ruby document format
by Martin Quinson
Hello,
the truth is that the development of po4a is kinda stopped since a few
years. We do the basic maintainance, like reviewing and applying
proposed patches (with some delays), but I don't manage to devote any
time to the new wanted features myself. I'm sorry about that, but this
is a fact.
As a result, I think that you should develop this module yourself. I
understand that Perl will make your brain burn as a Ruby programmer,
but at the end, developping a new module for po4a is very easy. …
[View More]And I
can guide you in this process if you go that way.
Check the doc on writing a new module, here:
man Locale::Po4a::TransTractor
I think that this is a good idea to keep both the upstream list and
the debian bug in CC while discussing it. It will ensure both a good
diffusion and a good archiving of the discussions.
Good luck, Mt.
On Wed, Jun 22, 2016 at 11:35:21PM +0200, Francesco Poli (wintermute) wrote:
> Package: po4a
> Version: 0.47-2
> Severity: wishlist
>
> Hello and thanks for developing po4a.
>
> As discussed on the po4a-devel mailing list [1], it would be great
> if po4a supported the Ruby document format [2].
>
> [1] https://lists.alioth.debian.org/pipermail/po4a-devel/2016-June/002364.html
> [2] https://en.wikipedia.org/wiki/Ruby_Document_format
>
> Could you please implement support for it in an appropriate module,
> so that I could, for instance, do something like:
>
> $ po4a-gettextize -f rd -m apt-listbugs -p doc-apt-listbugs.pot
>
> The Ruby document format is processed by package rdtool (among other
> possible tools) and is described in its documentation [3].
>
> [3] https://github.com/uwabami/rdtool/blob/master/doc/rd-draft.rd
>
> I hope implementing this additional module is not too hard.
> Please let me know.
>
> Thanks a lot for your time!
> Bye.
>
--
Reject: Figure 3 is unclear. -- Bastard Reviewer From Hell
[View Less]
7 years, 11 months
Fwd: Re: Introduction
by Hannie Dumoleyn
-------- Doorgestuurd bericht --------
Onderwerp: Re: Introduction
Datum: Sat, 22 Oct 2016 13:42:20 +0200
Van: Gunnar Hjalmarsson <gunnarhj(a)ubuntu.com>
Aan: Chris Perry <clissold345(a)googlemail.com>, Ryan Mason
<masetrax1(a)gmail.com>
CC: ubuntu-doc(a)lists.ubuntu.com
On 2016-10-22 10:32, Chris Perry wrote:
> On 2016-10-22 02:31, Ryan Mason wrote:
>> Chris - that sounds like a great place to start and I would
>> certainly appreciate the push in the …
[View More]right direction!
>
> One way to start with the desktop help is to choose a bug from this
> list:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs
>
> The right bug for you depends on various factors such as your
> knowledge of Ubuntu and how big or small a job you want to take on.
> In my (limited) experience the time-consuming part in tackling a
> documentation bug is understanding the problem.
>
> Once you've chosen a bug and you understand the problem and you've
> decided what changes you want to make, you make the changes in a
> local copy of the help and propose a merge of your changes into the
> development branch. (For the changes I've made Gunnar has reviewed
> them and has been very helpful.) Instructions here:
>
> https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuDeskt...
>
> If you have any questions let me know and I'll try to answer.
I addition to Chris' pointers I'd like to add a summary of working areas
as regards the desktop guide, which I posted recently:
https://lists.ubuntu.com/archives/ubuntu-doc/2016-September/020207.html
There is also the server guide, which is different in style and whose
target audience is different compared to the desktop guide, but which -
just like the desktop guide - is always in need of some love:
https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuServe...
--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj
--
ubuntu-doc mailing list
ubuntu-doc(a)lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc
[View Less]
8 years, 5 months
