[Denemo-devel] [bug #56769] Czech translation update of the file to Translation Project

2019-08-17 Thread anonymous 
URL:
  

 Summary: Czech translation update of the file to Translation
Project
 Project: Denemo
Submitted by: None
Submitted on: Sat 17 Aug 2019 09:23:07 PM UTC
Category: None
Severity: 3 - Normal
  Item Group: None
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

Hi,
I've experienced the issue with the service. See the message and the file is
attached:

"Hi! I am the service robot at the Translation Project,
and was awakened by your submission of 'denemo-2.3.cs.po'.

***> Your PO file seems to have no entries at all, like if it were
empty.

Some error reported above (marked with "***>") prevents me from
accepting your PO file. Sorry! But do not hesitate to resubmit your
PO file, once you think the problem has been fixed. As a robot I am
incredibly patient at these things!

The Translation Project robot, in the
name of your kind translation coordinator.
 "

Greetings, Pavel Fric



___

File Attachments:


---
Date: Sat 17 Aug 2019 09:23:07 PM UTC  Name: denemo-2.3.cs.po  Size: 1MiB  
By: None



___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/


___
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel

Re: [Denemo-devel] PNG selection export (was Re: Beginner questions (cross-staff, PNG selection export, feathered beams, batch export, Print View behaviour))

2019-08-17 Thread Lib Lists 
On Sat, 17 Aug 2019 at 11:11, Richard Shann  wrote:
>
> On Fri, 2019-08-16 at 15:07 +0200, Lib Lists wrote:
> > > Once you have the echo message from the myopen.sh saying what the
> > > command it is issuing is you can then check that the file does in
> > > fact
> > > exist and is a .png image ... indeed you can simply repeat the
> > > command
> > > that myopen.sh is telling you directly on the command line to check
> > > that it is working. (Possible snags could include unusual
> > > characters in
> > > the file name(*) - some operating systems have restrictions and
> > > some
> > > characters such as spaces cause parsing problems).
> > > HTH
> > > Richard
> > > (*) so test with a file named something simple, like "junk.denemo"
> >
> >
> > Hi,
> > thanks for your help.
> > if I launch the script from the terminal it works (as in your example
> > open -a /PATH/TO/Preview mypicture.png). However, when I launch the
> > script from Denemo (I put the full path of the script in the Image
> > Viewer field) nothing happens, i.e. I don't see the echo message on
> > the terminal and the same pop-up window.
>
> As you don't have the echo message we can be pretty sure the problem is
> *not* the same as the failure to launch Safari when trying to use the
> Denemo manual - in that case Safari was launched, it just didn't expect
> a URL on the command line, expecting a file name instead (so you could
> fix that by a script that chopped the initial file:/// off).
>
> I've looked at the source code and it seems the problem is that for
> some Glib versions the success status of the typesetting is being
> inverted.
> I've fixed this now in the sources, but unfortunately I don't think
> there is any daily build for MacOS - indeed I'm not sure if anyone is
> ready, willing and able to build for MacOS - so you will need a work
> around. You may be able to get there by locating the temporary
> directory where Denemo is storing the results of typesetting. On Unix
> it is /tmp/Denemo_*
> a new one of which is created each time you start Denemo. In there you
> will find the .png files that are created (they are named
> denemoprintA.png and denemoprintB.png alternately).

Hi, thanks for your help! I'll fix the safari problem with a script.
I found the TMP folder, on a mac an easy way to find it is to look for
$TMPDIR, which is a different folder than /tmp. There I found the
Denemo folder with a denemoprintA.png picture correctly created.
Yes, I noticed that there are no updated builds for MacOS. Do you know
how difficult is to build for MacOS? Otherwise I'll give a try running
the Windows version with Wine / Crossover.

Lib

>
> HTH
>
> Richard
>
>
>
>
>
>

___
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel

Re: [Denemo-devel] PNG selection export (was Re: Beginner questions (cross-staff, PNG selection export, feathered beams, batch export, Print View behaviour))

2019-08-17 Thread Richard Shann 
On Fri, 2019-08-16 at 15:07 +0200, Lib Lists wrote:
> > Once you have the echo message from the myopen.sh saying what the
> > command it is issuing is you can then check that the file does in
> > fact
> > exist and is a .png image ... indeed you can simply repeat the
> > command
> > that myopen.sh is telling you directly on the command line to check
> > that it is working. (Possible snags could include unusual
> > characters in
> > the file name(*) - some operating systems have restrictions and
> > some
> > characters such as spaces cause parsing problems).
> > HTH
> > Richard
> > (*) so test with a file named something simple, like "junk.denemo"
> 
> 
> Hi,
> thanks for your help.
> if I launch the script from the terminal it works (as in your example
> open -a /PATH/TO/Preview mypicture.png). However, when I launch the
> script from Denemo (I put the full path of the script in the Image
> Viewer field) nothing happens, i.e. I don't see the echo message on
> the terminal and the same pop-up window.

As you don't have the echo message we can be pretty sure the problem is
*not* the same as the failure to launch Safari when trying to use the
Denemo manual - in that case Safari was launched, it just didn't expect
a URL on the command line, expecting a file name instead (so you could
fix that by a script that chopped the initial file:/// off).

I've looked at the source code and it seems the problem is that for
some Glib versions the success status of the typesetting is being
inverted.
I've fixed this now in the sources, but unfortunately I don't think
there is any daily build for MacOS - indeed I'm not sure if anyone is
ready, willing and able to build for MacOS - so you will need a work
around. You may be able to get there by locating the temporary
directory where Denemo is storing the results of typesetting. On Unix
it is /tmp/Denemo_*
a new one of which is created each time you start Denemo. In there you
will find the .png files that are created (they are named
denemoprintA.png and denemoprintB.png alternately).

HTH

Richard







___
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel