Re: Cannot get Externam Material: Inkscape figure to work

[Jürgen Spitzmüller]

Am Freitag, den 03.11.2017, 08:28 +0100 schrieb racoon:
> The feature works in rc1 now. Great!

Good. Thanks for confirming.


> But there is no UI preference to set the scaling, right?

Right. It seems to have been left out by purpose (there's an according
comment in the xtemplate file), but it would be easy to add it (now;
later, it would be a file format change).

Scott, are you interested in that? See attached patch.

Jürgen

> 
> Daniel
> 
diff --git a/lib/xtemplates/inkscape.xtemplate b/lib/xtemplates/inkscape.xtemplate
index e4fc14d531..ff0b6b5ae7 100644
--- a/lib/xtemplates/inkscape.xtemplate
+++ b/lib/xtemplates/inkscape.xtemplate
@@ -46,11 +46,12 @@ Template Inkscape
 	FileFilter "*.{svg}"
 	AutomaticProduction true
 	Transform Rotate
+	Transform Resize
 	Preview InstantPreview
 	Format PDFLaTeX
 		TransformCommand Rotate RotationLatexCommand
-		# Resize is not desirable here, as fonts are sized to surrounding LaTeX font
-		Product "$$RotateFront\\input{$$AbsOrRelPathMaster$$Basename.pdf_tex}$$RotateBack"
+		TransformCommand Resize ResizeLatexCommand
+		Product "$$RotateFront$$ResizeFront\\input{$$AbsOrRelPathMaster$$Basename.pdf_tex}$$ResizeBack$$RotateBack"
 		UpdateFormat pdftex
 		UpdateResult "$$AbsPath$$Basename.pdf_tex"
 		Requirement "xcolor"
@@ -63,7 +64,8 @@ Template Inkscape
 	FormatEnd
 	Format LaTeX
 		TransformCommand Rotate RotationLatexCommand
-		Product "$$RotateFront\\input{$$AbsOrRelPathMaster$$Basename.eps_tex}$$RotateBack"
+		TransformCommand Resize ResizeLatexCommand
+		Product "$$RotateFront$$ResizeFront\\input{$$AbsOrRelPathMaster$$Basename.eps_tex}$$ResizeBack$$RotateBack"
 		UpdateFormat pstex
 		UpdateResult "$$AbsPath$$Basename.eps_tex"
 		Requirement "xcolor"


signature.asc
Description: This is a digitally signed message part

Re: [LyX/master] * cs.po

[Pavel Sanda]

Guenter Milde wrote:
> Would it be sesnsible to introduce a "wontfix"-like tag for such cases so
> that we can easily differentiate between "not yet translated" and "not
> required to be translated"?
> Or would this make things more complicated than required?

It would make sense to have, but I think it's not worth the effort
considering what we would have to tweak... Of course, if you feel brave :)
Pavel

Re: Language problems ... again

[Jürgen Spitzmüller]

Am Freitag, den 03.11.2017, 00:10 -0400 schrieb Scott Kostyshak:
> On Thu, Nov 02, 2017 at 08:43:35PM +, Kornel Benko wrote:
> > Am Donnerstag, 2. November 2017 um 21:37:25, schrieb Jürgen
> > Spitzmüller 
> > > Am Donnerstag, den 02.11.2017, 21:17 +0100 schrieb Kornel Benko:
> > > > examples/ja/sweave.lyx not compilable. Resetting the English
> > > > text at
> > > > section 5
> > > > 'The user manual ofSweave is at'
> > > > cures the problem.
> > > 
> > > A more sane solution is to set "Language package" in Document
> > > Settings
> > > from "None" to "Automatically".
> > > 
> > > Jürgen
> > 
> > Yes, this works. +1
> 
> Works here also. I would say +1 for 2.3.x.

I went for the language-agnostic version, since this is used in other
places of the manual, and I don't want to interfere with Koji's style.

Jürgen

> 
> Scott

signature.asc
Description: This is a digitally signed message part

Re: [LyX/master] * cs.po

[Guenter Milde]

On 2017-11-02, Pavel Sanda wrote:
> Kornel Benko wrote:
>> Am Donnerstag, 2. November 2017 um 10:14:52, schrieb Pavel Sanda 
>> 
>> > commit 534b1e9c9062b9e526566115dd5816cea220feab
>> > Author: Pavel Sanda 
>> > Date:   Thu Nov 2 10:14:28 2017 +0100
>> > 
>> > * cs.po

>> Is it intended that you have so many (122!) tooltip messages marked as
>> translated but still in the English version?

> Since I do not expect many submissions to Journal of American Chemical
> Society to happen in czech language (or reasonable usage of similar
> esoterical layouts) I deliberately do not translate those -- and if you
> value your time, you should do the same :)

Would it be sesnsible to introduce a "wontfix"-like tag for such cases so
that we can easily differentiate between "not yet translated" and "not
required to be translated"?
Or would this make things more complicated than required?

Günter