On Tue, Feb 17, 2015 at 6:37 AM, Kornel Benko <kor...@lyx.org> wrote:
> Am Dienstag, 17. Februar 2015 um 09:37:23, schrieb Kornel Benko 
> <kor...@lyx.org>
>> Am Dienstag, 17. Februar 2015 um 01:01:36, schrieb Scott Kostyshak 
>> <skost...@lyx.org>
>> > On Mon, Feb 16, 2015 at 6:44 PM, Uwe Stöhr <uwesto...@lyx.org> wrote:
>> > > commit 4549468dc9811481d379a6b4b9a0852247d3b954
>> > > Author: Uwe Stöhr <uwesto...@lyx.org>
>> > > Date:   Tue Feb 17 00:44:47 2015 +0100
>> > >
>> > >     configure.py: change name of a converter as discussed
>> > >
>> >
>> > I can no longer compile on master. I get the following:
>> > /usr/bin/msguniq: input file
>> > '/home/scott/lyxbuilds/master/CMakeBuild/po/lyx2.2.cat.pot' doesn't
>> > contain a header entry with a charset specification
>> > make[2]: *** [po/lyx2.2.fmt.pot] Error 1
>> >
>> > Scott
>>
>>
>> The offending re at po/lyx_pot.py:549
>>       re.compile(r'.*\\Format\s+\S+\s+\S+\s+"([^"]*)"\s+(\S*)\s+.*', 
>> re.IGNORECASE)
>>
>> The re for line
>>       \Format pdf8       pdf    "PDF (lower resolution)"         "" "%%"     
>> ""      "document,vector"       ""'''])
>> should find
>>
>> \S+                   pdf8
>> \S+           pdf
>> Match1                PDF (lower resolution)
>> Match2                ""
>>
>> Don't understand why it does not work.
>>
>> Nonetheless, since we expect Match2 be not empty, changing the line to
>>       re.compile(r'.*\\Format\s+\S+\s+\S+\s+"([^"]*)"\s+(\S+)\s+.*', 
>> re.IGNORECASE)
>> cures it for me.
>>
>
> Apparently this was not the problem. I also changed the string "PDF (lower 
> resolution)". in 'lower resolution' with ' ')
> The blank in 'lower resolution' was coded as '\302 \240'.
> You can see it with od -c lib/configure.py
>         ...
>         0074100   \   F   o   r   m   a   t       p   d   f   8
>         0074120               p   d   f                   "   P   D   F
>         0074140   l   o   w   e   r 302 240   r   e   s   o   l   u   t   i   
> o
>         0074160   n   )   "                                       "   "       
> "
>         ...
>

Thanks for the fix. It works well now.

Scott

Reply via email to