[SOLVED] MX-17 package update request: Xfburn

Message
Author
User avatar
MX-16_fan
Posts: 331
Joined: Mon Feb 13, 2017 12:09 pm

[SOLVED] MX-17 package update request: Xfburn

#1 Post by MX-16_fan »

I have been advised to use Xfburn instead of Brasero (https://forum.mxlinux.org/viewtopic.php ... 08#p455808).

Unfortunately using Xfburn's 0.5.4 version that ships with MX-17 (from Debian) is extremely difficult for me: Xfburn's window is about twice as wide as my acual screen, and the window can't be rescaled. This is the only application that has shown this kind of behaviour so far.

The most current stable version of Xfburn seems to be 0.5.5. According to this changelog: https://launchpad.net/ubuntu/+source/xfburn/0.5.5-1, "some fixes for the desktop file" have been implemented there, so maybe that fixes the problem.

I see that 0.5.5 is available in Debian Sid (https://packages.debian.org/en/sid/xfce/xfburn). Could you possibly provide it in the MX Test Repo?


Greetings, and thanks so much in advance for looking into this, Joe
Last edited by MX-16_fan on Mon Aug 10, 2020 3:34 pm, edited 1 time in total.

User avatar
chrispop99
Global Moderator
Posts: 3174
Joined: Tue Jan 27, 2009 3:07 pm

Re: MX-17 package update request: Xfburn

#2 Post by chrispop99 »

Might it be better to try to fix the re-sizing problem first; it's possible it may still happen with the updated version?

Xfburn has never exhibited that behaviour here when testing, although on my everyday machine I use K3B.

Chris
MX Facebook Group Administrator.
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines

User avatar
fehlix
Developer
Posts: 10366
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-17 package update request: Xfburn

#3 Post by fehlix »

MX-16_fan wrote: Fri Jul 27, 2018 11:02 am ...
Unfortunately using Xfburn's 0.5.4 version that ships with MX-17 (from Debian) is extremely difficult for me: Xfburn's window is about twice as wide as my acual screen, and the window can't be rescaled.
This is the only application that has shown this kind of behaviour so far.
...
Seems to be a translation-string related issue with to long translated / unwrapped strings.
Please try to use default build in locale (english)
by starting from the cli or by adjusting the desktop starter accordingly
like this:

Code: Select all

env LANG=C xfburn
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
MX-16_fan
Posts: 331
Joined: Mon Feb 13, 2017 12:09 pm

Re: MX-17 package update request: Xfburn

#4 Post by MX-16_fan »

@fehlix:
fehlix wrote: Fri Jul 27, 2018 12:07 pm (...)
Seems to be a translation-string related issue with to long translated / unwrapped strings.
Please try to use default build in locale (english)
by starting from the cli or by adjusting the desktop starter accordingly
like this:

Code: Select all

env LANG=C xfburn
Thanks for the workaround. With that I get a normal width.

Is that an error in the 0.5.4 source code?


Greetings, Joe

User avatar
fehlix
Developer
Posts: 10366
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-17 package update request: Xfburn

#5 Post by fehlix »

MX-16_fan wrote: Fri Jul 27, 2018 12:51 pm @fehlix:
fehlix wrote: Fri Jul 27, 2018 12:07 pm (...)
Seems to be a translation-string related issue with to long translated / unwrapped strings.
Please try to use default build in locale (english)
by starting from the cli or by adjusting the desktop starter accordingly
like this:

Code: Select all

env LANG=C xfburn
Thanks for the workaround. With that I get a normal width.

Is that an error in the 0.5.4 source code?


Greetings, Joe
I would flag it a an translation code error, as the translation string missing line feeds for line wrappings.
So in this sense as the translation strings are part of the souce code package you can regard it as a source code "bug" ;)
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Stevo
Developer
Posts: 12830
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX-17 package update request: Xfburn

#6 Post by Stevo »

That's something which we should be able to fix in a patch for the affected translation file if necessary. I'll backport 5.5 to see if they've fixed it, and if not, we can work to fix the string in the localization source file...though upstream should also be notified of the bug. Is it in the "de" locale?

User avatar
MX-16_fan
Posts: 331
Joined: Mon Feb 13, 2017 12:09 pm

Re: MX-17 package update request: Xfburn

#7 Post by MX-16_fan »

@Stevo:
Stevo wrote: Fri Jul 27, 2018 2:13 pm That's something which we should be able to fix in a patch for the affected translation file if necessary. I'll backport 5.5 to see if they've fixed it, and if not, we can work to fix the string in the localization source file...though upstream should also be notified of the bug.
Thanks!
Stevo wrote: Fri Jul 27, 2018 2:13 pm Is it in the "de" locale?
Yes.


Greetings, and have a great weekend, Joe

User avatar
Stevo
Developer
Posts: 12830
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX-17 package update request: Xfburn

#8 Post by Stevo »

I can't see any fix Debian added for the 0.5.5 version, no Debian bug reports for the issue: https://bugs.debian.org/cgi-bin/pkgrepo ... t=unstable and there's no change at all in the de translation source file between 0.5.4 and 0.5.5. I can see some sections where it looks like the de translation strings are missing the returns, so I'll try and fix those.

User avatar
fehlix
Developer
Posts: 10366
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-17 package update request: Xfburn

#9 Post by fehlix »

Stevo wrote: Fri Jul 27, 2018 3:21 pm I can't see any fix Debian added for the 0.5.5 version, no Debian bug reports for the issue: https://bugs.debian.org/cgi-bin/pkgrepo ... t=unstable and there's no change at all in the de translation source file between 0.5.4 and 0.5.5. I can see some sections where it looks like the de translation strings are missing the returns, so I'll try and fix those.
Changing the strings below within xfburn.mo for locale DE

Code: Select all

--- xfburn.po.orig	2018-07-27 20:54:43.579202403 +0200
+++ xfburn.po	2018-07-27 21:44:02.265074643 +0200
@@ -162,7 +162,7 @@
 msgstr "Künstler"
 
 msgid "Audio CD playable in regular stereos"
-msgstr "Eine Musik-CD zum Abspielen in normalen Stereoanlagen erstellen"
+msgstr "Eine Musik-CD zum Abspielen\nin normalen Stereoanlagen erstellen"
 
 msgid "Audio composition"
 msgstr "Musikzusammenstellung"
@@ -195,7 +195,7 @@
 msgstr "CD-Abbild brennen (xfburn)"
 
 msgid "Burn a prepared compilation, i.e. an .ISO file"
-msgstr "Zusammenstellung brennen (z.B. ISO-Dateien)"
+msgstr "Zusammenstellung brennen\n   (z.B. ISO-Dateien)"
 
 msgid "Burn image"
 msgstr "Abbild brennen"
@@ -360,7 +360,7 @@
 msgstr "ISO aus CD erzeugen"
 
 msgid "Create a new data disc with the files of your choosing"
-msgstr "Ein neues Datenmedium mit beliebigen Dateien erstellen"
+msgstr "Ein neues Datenmedium\nmit beliebigen Dateien erstellen"
 
 msgid "Create directory"
 msgstr "Neuer Ordner"
@@ -667,7 +667,7 @@
 
 msgid "Prepare the rewriteable disc for a new burn"
 msgstr ""
-"Ein wiederbeschreibbares (RW) Medium für einen neuen Brennvorgang vorbereiten"
+"Ein wiederbeschreibbares (RW) Medium\nfür einen neuen Brennvorgang vorbereiten"
 
 msgid "Proceed to Burn"
 msgstr "Weiter zum Brennen"
gives me those minimal window of the start screen in comparison for the orignal one
You do not have the required permissions to view the files attached to this post.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Stevo
Developer
Posts: 12830
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX-17 package update request: Xfburn

#10 Post by Stevo »

Hmmm...I did a bigger set of changes.

Does this version fix it?

https://drive.google.com/open?id=1FxCv9 ... 4KnDGr7WWJ

Locked

Return to “Package Requests/Status - MX 17/18”