[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Translation segfaults ( blocker in rc4 ? )

From: Helio Chissini de Castro <helio_at_mandriva.com>
Date: 2005-12-09 14:52:50 CET

Em Friday 09 December 2005 07:01, Peter N. Lundblad escreveu:
> I've been trying to reproduce this with de.mo and latest 1.3 sources. But
> without success.
> Just to make sure, whe testing an uninstalled build, svn picks up
> translations in the installed location. Are you sure you don't have old
> .mo files lying around?
> If this is directly related to a bad translation, maybe you could
> intercept the gettext call to get at the last message translated? You
> could add something to svn_private_config.h. (I could help with this if
> you want to.)

Got it..

First, i assured that have clean .mo.
The _(x) teste wast great, all fails come in this specific string:

#: libsvn_subr/io.c:2221
#: libsvn_subr/io.c:2245
#: libsvn_subr/io.c:2258
#, c-format
msgid "Can't read file '%s'"
msgstr "Kann Datei '%s' nicht lesen"

Is interesting that is same kind of string which i had problem on old version
( Garret, i tested 1.2.1 today and happens too. I started to take care of
subversion package just after 1.2.3 rc releases ), but difference now is that
old one had two string, with and without arguments, and now we have just with

after running some gdb, we have a winner:

svn_error_t *
svn_io_file_read (apr_file_t *file, void *buf,
                  apr_size_t *nbytes, apr_pool_t *pool)

More debug steps show me that *pool brings a ` character:
Can't read file '` '

This is exaclty what are happening. I guess need to dig who are sending
garbage to translation..


Helio Chissini de Castro
Research and development
Mandriva Brasil Labs
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 9 14:59:06 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.