James D Holby writes:
> I had a similar test, but I used yours just to validate; however, my
> output is not as expected using v0.18.3.2 from
> http://git.savannah.gnu.org/cgit/gettext.git (Ubuntu 13.10)
Ah, right. I don't quite remember why I didn't include the fix in
v0.18.3.2:
https://savann
Thanks for the reply Daiki:
I had a similar test, but I used yours just to validate; however, my output
is not as expected using v0.18.3.2 from
http://git.savannah.gnu.org/cgit/gettext.git (Ubuntu 13.10)
Is there another release I should be using to get the proper output as
yours?
$ cat test.js
James D Holby writes:
>> Could you elaborate what you mean with "developer comments"?
>
> In the PO files they can contain:
>
> #. Programmer comment
>
> The manual mentions we can add keywords to extract comments to be extracted
> into the PO file so that the developer can give context to the tr
Hey Daiki:
> Could you elaborate what you mean with "developer comments"?
In the PO files they can contain:
#. Programmer comment
The manual mentions we can add keywords to extract comments to be extracted
into the PO file so that the developer can give context to the translator.
However, it d
Hi,
James D Holby writes:
> Does this fall under the realm of partial support or is there some special
> formatting options in order for the parser to extract the .js developer
> comments?
Could you elaborate what you mean with "developer comments"? I didn't
get any useful result from a quick
Hello bug-gettext:
The release notes for v.0.18.3.2 say that there is *partial *support for
JavaScript in the release and I've been successful in generating .po files
using xgettext().
However, it's failing to parse out any developer comment lines that
directly precede the extracted strings into
