Shotwell

Untranslatable strings in import directory format popup

Bug #760399 reported by Robert Ancell on 2011-04-14

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Shotwell	Fix Released	Unknown	redmine.yorba.org #3497
	shotwell (Ubuntu)	Fix Released	Wishlist	Unassigned

Bug Description

Binary package hint: shotwell

Some UI strings in the import directory format popup aren't translatable
See the strings built up using the string concatenation operator around Dialogs.vala:1740

Tags:

Related branches

lp:~ubuntu-desktop/shotwell/ubuntu

Robert Ancell (robert-ancell) on 2011-04-14

Changed in shotwell (Ubuntu):
status:	New → Triaged
importance:	Undecided → Wishlist

Revision history for this message

Robert Ancell (robert-ancell) wrote on 2011-04-14:

Debdiff of changes Edit (2.8 KiB, text/plain)

Bug Watch Updater (bug-watch-updater) on 2011-04-14

Changed in shotwell:
status:	Unknown → Fix Released

Brian Murray (brian-murray) on 2011-04-14

tags:

added: patch

Revision history for this message

Lucas Beeler (lucas-yorba) wrote on 2011-04-15:

We may soon be fixing this issue upstream. Current plans call for doing a Shotwell 0.9.3 release to fix this and selected other small issues listed here: http://trac.yorba.org/query?milestone=0.9.3

Lucas

Bug Watch Updater (bug-watch-updater) on 2011-04-16

Changed in shotwell:
status:	Fix Released → Confirmed

Bug Watch Updater (bug-watch-updater) on 2011-04-20

Changed in shotwell:
status:	Confirmed → Fix Released

Revision history for this message

Sebastien Bacher (seb128) wrote on 2011-04-20:

Was there anything blocking that fix? The bug fixes don't need approval to be uploaded

Revision history for this message

Adam Dingle (adam-yorba) wrote on 2011-04-25:

Sebastien,

We recently released Shotwell 0.9.3 including a fix for this bug. I don't understand your question about blocking this fix - was it intended for Shotwell developers, or for Shotwell packagers at Ubuntu? Can you clarify?

Revision history for this message

Sebastien Bacher (seb128) wrote on 2012-02-23:

the fix is included in the current version shipped in Ubuntu, closing the bug