emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-orgmode@gnu.org, po4a-devel@lists.alioth.debian.org,
	emacs-devel@gnu.org
Subject: Re: 3 manuals fail to export to PO (gnus, idlwave, org)
Date: Mon, 16 Apr 2018 07:27:40 +0900	[thread overview]
Message-ID: <9A7EF7FE-BCA2-424E-ADC9-63FD0688E452@gmail.com> (raw)
In-Reply-To: <83a7u44iqd.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 3176 bytes --]



> On Apr 16, 2018, at 0:00, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> 3 manuals distributed with emacs fail to export to po format when using the following command:
>> 
>> po4a-gettextize -f texinfo -M utf8 -m name.texi -p name.texi.fr.po
>> 
>> gnus.texi
>> 
>> Use of uninitialized value $newfilepath in string eq at /opt/local/lib/perl5/5.24/Locale/Po4a/TeX.pm line 961.
>> po4a::tex: Can't find gnus.texi with kpsewhich
> 
> I don't understand what this error message means, in terms of the
> Texinfo sources.  Can you explain, please?  Taken at face value, it
> looks like a bug in TeX.pm, whereby a variable is not initialized.

I just sent the report, my idea is that it's po4a issues but the po4a-devel list doesn't respond.

Jean-Christophe 

> 
>> idlwave.texi
>> 
>> idlwave.texi:370: (po4a::tex)
>> unmatched end of environment 'html'
>> idlwave.texi:1242: (po4a::tex)
>> unmatched end of environment 'html'
>> idlwave.texi:2964: (po4a::tex)
>> unmatched end of environment 'html'
>> idlwave.texi:3101: (po4a::tex)
>> unmatched end of environment 'html'
>> idlwave.texi:3497: (po4a::tex)
>> unmatched end of environment 'html'
>> idlwave.texi:3559: (po4a::tex)
>> unmatched end of environment 'html'
>> idlwave.texi:4021: (po4a::tex)
>> unmatched end of environment 'html'
>> idlwave.texi:4078: (po4a::tex)
>> unmatched end of environment 'html'
> 
> These all seem bogus, because the source looks correct to me.  Here's
> the first instance:
> 
>  @html
>  <A NAME="TUTORIAL"></A>
>  @end html
> 
> I see nothing wrong here; do you?
> 
> (Maybe you are using an old version of the manual; I looked in what's
> currently on the emacs-26 branch of the Emacs Git repository.)
> 
>> idlwave.texi:4088: (po4a::tex)
>> un-balanced { in 'Whenever an IDL error occurs or a breakpoint is hit, I get'
> 
> Nothing wrong here, either:
> 
>  @enumerate
> 
>  @item @strong{Whenever an IDL error occurs or a breakpoint is hit, I get
>  errors or strange behavior when I try to type anything into some of my
>  IDLWAVE buffers.}
> 
> The Texinfo manual says it's okay to have multi-line text after @item:
> 
>     Write the text of the enumerated list in the same way as an itemized
>  list: write a line starting with '@item' at the beginning of each item
>  in the enumeration.  It is ok to have text following the '@item', and
>  the text for an item can continue for several paragraphs.
> 
> Looks like po4a doesn't support this feature of the Texinfo language?
> 
>> org.texi
>> 
>> perl just keeps churning data without outputting anything.
> 
> Hard to do anything with this, without more diagnostic data.
> 
>> A number of other manuals output errors but are properly exported to po:
> 
> These looks bogus as well.  E.g.:
> 
>> cmdargs.texi:726: (po4a::tex)
>> unmatched end of environment 'vtable'
> 
> There's a matching "@vtable @env" on line 674.
> 
> So I submit these problems are bugs in po4a, and the Emacs manuals are
> OK.
> 
> Thanks.

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune



[-- Attachment #2: Type: text/html, Size: 34595 bytes --]

      reply	other threads:[~2018-04-15 22:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-15 12:33 3 manuals fail to export to PO (gnus, idlwave, org) Jean-Christophe Helary
2018-04-15 15:00 ` Eli Zaretskii
2018-04-15 22:27   ` Jean-Christophe Helary [this message]

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9A7EF7FE-BCA2-424E-ADC9-63FD0688E452@gmail.com \
    --to=jean.christophe.helary@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=po4a-devel@lists.alioth.debian.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).