Re: LyX-to-LyX pasting from "English" to "English (USA)" annoyances

[Scott Kostyshak]

On Sun, Jan 21, 2018 at 09:22:22AM +, Jürgen Spitzmüller wrote:

> I think this will be hard to get right. Also language varieties such as
> American and Britisch English or Swiss and German German differ in
> details (e.g. spelling or hyphenation rules). Changing the language
> automatically could result in subtle problems.
> 
> Having said that, your case is special since "English" and "English
> (USA)" refer to the same variety, American English. On the other hand,
> it also differs sometimes in LaTeX-generated output (as you observe
> yourself), so changing it without user intervention is problematic
> here, too.

OK that makes sense. Best not to change anything.

Scott


signature.asc
Description: PGP signature

Re: LyX-to-LyX pasting from "English" to "English (USA)" annoyances

[Scott Kostyshak]

On Sun, Jan 21, 2018 at 08:51:25PM +, Cris Fuhrman wrote:
> On Sat, Jan 20, 2018 at 5:39 PM, Scott Kostyshak  wrote:
> 
> > I do this maneuver enough times that I find it annoying.
> >
> 
> I'd map the command to change language text to a hot key (I'm pretty sure I
> did this before with one of the text formatting things I found myself doing
> often).

This is a good idea! I'm not sure why, but I did not even think of
making a command-sequence that does what I want. Thanks, Cris!

> A possibly cool feature would be for LyX to detect that a user is often
> doing the same (uncommon) command and propose mapping it to a hot key? I'm
> sure some software somewhere does this...

Clippy? :)

> Asking people how often it happens (in the users forum) is likely to
> generate more heat than light, mainly because it's only from folks who are
> subscribed.

True, but if we can predict the bias, then it gives information. If no
one on lyx-users finds this issue to be common (as appears to be the
case here), then I think the average LyX user is even less likely to
come across the issue. I would just guess this because I think the
average LyX user is less likely to set some documents to "English" and
some to "English (USA)". But I'm not so confident in that guess.

> A more precise way to know would be to collect usage metrics
> for LyX, which was not a well liked idea from my recollection of that in
> the forum.

Yeah, that would have some benefits, but I don't think there is support
for it.

Thanks for your response,

Scott


signature.asc
Description: PGP signature

Re: Need to display computer code listings with normal, bold, and strikeout display

[Scott Kostyshak]

On Mon, Jan 22, 2018 at 12:17:57AM +, ll...@writersglen.com wrote:
> 
> Hello,
>  
> Four questions:
>  
> I'm developing a technical book in which I need to display computer code 
> listings with normal, bold, and strikeout  display, but this doesn't seem 
> possible with my version of lyx/LaTex.
>  
> I'm using:
>  
> lyx - version 2.2.3
> TexLive 2015 (I think, but don't know how to check)
> Ubuntu 16.04
>  
> My understanding from several hours of web search is that by moving from 
> TexLive to Xetex or LuaTex and specifying the fontspec package and monospace 
> font with normal, bold, and strikeout faces, I can solve my problem.
>  
> But this scary prospect raises questions:
>  
> 1) Seems that I need to wipe out all traces of TexLive before I install 
> either XeTexLuaTex -- is this true?

TeX Live comes with XeTeX and LuaTeX. You can see this on the command
line. Just type e.g. lualatex --version

> 2) Need to choose either XeTex of LuaTex -- is there a preferred choice or 
> relevant trade-off?

I don't know much, but I think XeTeX is more mature but LuaTeX is under
more active development.

> 3) Will such drastic surgery put my current *.lyx file at risk?

I don't know. LyX does have support for XeTeX and LuaTeX.

> 4) Is theree a better/easier way to accomplish my goal?

I'm not exactly sure what you want to do. Can you send a minimal example
.lyx file to the list that has how you currently type set "computer
code". To do strikeout, did you try to go to font properties and specify
it?

Please respond to the list.

Best,

Scott


signature.asc
Description: PGP signature

Need to display computer code listings with normal, bold, and strikeout display

[lloyd]

Hello,
 
Four questions:
 
I'm developing a technical book in which I need to display computer code 
listings with normal, bold, and strikeout  display, but this doesn't seem 
possible with my version of lyx/LaTex.
 
I'm using:
 
lyx - version 2.2.3
TexLive 2015 (I think, but don't know how to check)
Ubuntu 16.04
 
My understanding from several hours of web search is that by moving from 
TexLive to Xetex or LuaTex and specifying the fontspec package and monospace 
font with normal, bold, and strikeout faces, I can solve my problem.
 
But this scary prospect raises questions:
 
1) Seems that I need to wipe out all traces of TexLive before I install either 
XeTexLuaTex -- is this true?
 
2) Need to choose either XeTex of LuaTex -- is there a preferred choice or 
relevant trade-off?
 
3) Will such drastic surgery put my current *.lyx file at risk?
 
4) Is theree a better/easier way to accomplish my goal?
 
Many thanks to all,
 
Lloyd
 
 
 
 
 
 
*
My books:

THE GOSPEL OF ASHES
http://thegospelofashes.com

Strength is not enough. Do they have the courage 
and the cunning? Can they survive long enough to 
save the lives of millions? 

FREEIN' PANCHO
http://freeinpancho.com

A community of misfits help a troubled boy find his way 

AYA TAKEO
http://ayatakeo.com

Star-crossed love, war and power in an alternative 
universe

Available through Amazon or by request from your 
favorite bookstore


**

Re: LyX-to-LyX pasting from "English" to "English (USA)" annoyances

[Cris Fuhrman]

On Sat, Jan 20, 2018 at 5:39 PM, Scott Kostyshak  wrote:

> I do this maneuver enough times that I find it annoying.
>

I'd map the command to change language text to a hot key (I'm pretty sure I
did this before with one of the text formatting things I found myself doing
often).

A possibly cool feature would be for LyX to detect that a user is often
doing the same (uncommon) command and propose mapping it to a hot key? I'm
sure some software somewhere does this...


> Thoughts?
>

Asking people how often it happens (in the users forum) is likely to
generate more heat than light, mainly because it's only from folks who are
subscribed. A more precise way to know would be to collect usage metrics
for LyX, which was not a well liked idea from my recollection of that in
the forum.

Re: How to extend a standard layouts

[racoon]

On 21.01.2018 00:13, Richard Heck wrote:

On 01/20/2018 11:30 AM, racoon wrote:

By default LyX loads standard layouts and insets. Is there a way to
extend them without overwriting the default .inc file and without
using a module?

Let's say I want to extend the standard Note style.

I don't want to use a module since I want to make a non-optional
change to the Note inset. For example, I want to use another font size
for all LyX notes.

If I understood correctly, I can just put a copy of the stdinset.inc
file from the library to the user directory. But this will have the
unwelcome effect to overwrite whatever is in the stdinset.inc in the
library directory. So, to avoid unwanted consequences, I will have to
update my user stdinset.inc every time the library stdinset.inc
changes, for example, in a new version of LyX.


I have run into this problem, too. Some form of it will arise any time
you want to emend or amend a layout file.

I wonder if a longer-term solution is required, then. Might there be
some way we could have 'extensions' of this kind? Maybe they could be
named things like stdinsets.inc.ext and they would always be loaded
after the corresponding other file was.


That sounds like a good solution to me. (And it could, in principle, be 
extended to other files: For every file where this seems reasonable, 
whether .inc, .module, etc., it is checked whether there is a file with 
the same name with the additional extension .ext and then loaded.)


Daniel

Re: LyX-to-LyX pasting from "English" to "English (USA)" annoyances

[Jürgen Spitzmüller]

Am Samstag, den 20.01.2018, 17:39 -0500 schrieb Scott Kostyshak:
> The ideal behavior for me would be that whenever I paste text that is
> in
> language "mylanguage (x)" into a document that has language
> "mylanguage
> (y)" and no other language, the text would be pasted as
> "mylanguage (y)". However, thinking about what the LyX behavior
> should
> be, I don't know what to suggest. On the one hand, I don't think we
> should change the default behavior since it is correct to treat
> "mylanguage (x)" and "mylanguage (y)" as different languages.
> On the other, I don't think this is a big enough issue that we should
> have a preference for it. So I don't know what to suggest.

I think this will be hard to get right. Also language varieties such as
American and Britisch English or Swiss and German German differ in
details (e.g. spelling or hyphenation rules). Changing the language
automatically could result in subtle problems.

Having said that, your case is special since "English" and "English
(USA)" refer to the same variety, American English. On the other hand,
it also differs sometimes in LaTeX-generated output (as you observe
yourself), so changing it without user intervention is problematic
here, too.

Jürgen

> 
> Thoughts?
> 
> Scott
> 

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