205: Couldn't import changeset with special german characters (umlaut)

Notice: this is a static mirror for historical purposes.

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

205

Source Integration

WebSVN

public

2011-05-16 10:31

2011-05-16 10:34

Reporter

Markus Hastreiter

Assigned To

John Reese

Priority

normal

Severity

minor

Reproducibility

always

Status

resolved

Resolution

duplicate

Product Version

Target Version

Fixed in Version

Summary

205: Couldn't import changeset with special german characters (umlaut)

Description

Some of my file names in the subversion repository have special german characters like ä, ö, ü, etc. When importing a changeset with these characters I got the following error message:

APPLICATION ERROR #401
Database query failed. Error received from database was #1366: Incorrect string value: '\x81llerD...' for column 'filename' at row 1 for the query: INSERT INTO mantis_plugin_Source_file_table ( change_id, revision, action, filename ) VALUES ( ?, ?, ?, ? ).

I managed to get around this issue by applying the advice given in 130:227 also to the filename. But it would be nice if a fix could also be added to the "offical" release.

Additional Information

In "process_svn_log" a few lines before
# Branch-checking
changed
$t_file = new SourceFile( $t_changeset->id, '', trim( $t_matches[2] ), $t_action );
to
$t_filename = iconv('CP850', 'UTF-8', $t_matches[2]);
$t_file = new SourceFile( $t_changeset->id, '', trim( $t_filename ), $t_action );

Tags

No tags attached.

Attached Files

Relationships

duplicate of

093

new

Couldn't import changeset with umlauts

Notes
(289) Markus Hastreiter (reporter) 2011-05-16 10:33	I suggest this issue should be marked to be related to issue 130 (I can't do this, I'm just a reporter).

(290) John Reese (administrator) 2011-05-16 10:34	This is a known issue related to the method chosen for gathering data from Subversion. There are some tips on how to resolve this for your own specific situation in 093, but the root cause can't be fixed in a cross-platform manner without reworking the entire plugin to use a proper SVN access layer.

Issue History
Date Modified	Username	Field	Change
2011-05-16 10:31	Markus Hastreiter	New Issue
2011-05-16 10:33	Markus Hastreiter	Note Added: 289
2011-05-16 10:34	John Reese	Note Added: 290
2011-05-16 10:34	John Reese	Relationship added	duplicate of 093
2011-05-16 10:34	John Reese	Status	new => resolved
2011-05-16 10:34	John Reese	Resolution	open => duplicate
2011-05-16 10:34	John Reese	Assigned To	=> John Reese

Time: 0.1406 seconds.
memory usage: 8,389 KB

hosted with