After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 682136 - [nautilus] invalid format in ja.po
[nautilus] invalid format in ja.po
Status: RESOLVED FIXED
Product: l10n
Classification: Infrastructure
Component: Japanese [ja]
GNOME 3.4
Other Linux
: Normal normal
: ---
Assigned To: Takayuki KUSANO
Takayuki KUSANO
Depends on:
Blocks:
 
 
Reported: 2012-08-18 05:50 UTC by Jiro Matsuzawa
Modified: 2012-08-18 06:31 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch for this bug (1.33 KB, patch)
2012-08-18 06:29 UTC, Jiro Matsuzawa 		none Details | Review

Description Jiro Matsuzawa 2012-08-18 05:50:32 UTC 
The format of the following msgstr in ja.po is invalid.

#: ../libnautilus-private/nautilus-file-operations.c:2929
msgid "Duplicating file %'d of %'d (in \"%B\")"
msgstr "%'d / %'d のファイルを \"%B\" から \"%B\" へ複製中"

It causes nautilus to crash.
A backtrace is here:
------------------------
Program received signal SIGSEGV, Segmentation fault.

+ Trace 230695

Thread 140737144416000 (LWP 4566)

  • #0 g_file_query_info
    from /lib64/libgio-2.0.so.0
  • #1 custom_basename_to_string
    at nautilus-file-operations.c line 798
  • #2 eel_strdup_vprintf_with_custom
    at eel-string.c line 583
  • #3 f
    at nautilus-file-operations.c line 907
  • #4 report_copy_progress
    at nautilus-file-operations.c line 2936
  • #5 copy_files
    at nautilus-file-operations.c line 4414
  • #6 copy_job
    at nautilus-file-operations.c line 4549
  • #7 ??
    from /lib64/libgio-2.0.so.0
  • #8 ??
    from /lib64/libglib-2.0.so.0
  • #9 ??
    from /lib64/libglib-2.0.so.0
  • #10 start_thread
    from /lib64/libpthread.so.0
  • #11 clone
    from /lib64/libc.so.6 






Comment 1


Jiro Matsuzawa





          2012-08-18 06:29:15 UTC
        



Created attachment 221684 [details] [review]
patch for this bug