Re: Problem with Mac-Key-Symbols (MUSTFIX)

Jean-Marc Lasgouttes wrote: Konrad Hofbauer <[EMAIL PROTECTED]> writes: Jean-Marc, in order to have a working solution for RC5 (or after), could you let InsetInfo-shortcut and InsetInfo-shortcuts simply output a text-based Command, Option, and Shift (both on screen and in latex, just as Ctrl and

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Konrad Hofbauer <[EMAIL PROTECTED]> writes: > Jean-Marc, in order to have a working solution for RC5 (or after), > could you let InsetInfo-shortcut and InsetInfo-shortcuts simply output > a text-based Command, Option, and Shift (both on screen and in latex, > just as Ctrl and Alt on win/linux)? Co

Re: Problem with Mac-Key-Symbols (MUSTFIX)

On Tue, Oct 28, 2008 at 1:17 PM, Konrad Hofbauer <[EMAIL PROTECTED]> wrote: > Bo Peng wrote: >> >> And help -> shortcuts.py may be too wide under mac. > > It seems already too wide (see attached), also with Win/Linux names. I agree, but the document is at least printable/viewable. This might not b

Re: Problem with Mac-Key-Symbols (MUSTFIX)

> P.S. Admitted, things might get a bit long, but IMO better a suboptimal > solution than a non-compilable userguide. And help -> shortcuts.py may be too wide under mac. Bo

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Konrad Hofbauer <[EMAIL PROTECTED]> writes: > Jean-Marc, in order to have a working solution for RC5 (or after), > could you let InsetInfo-shortcut and InsetInfo-shortcuts simply output > a text-based Command, Option, and Shift (both on screen and in latex, > just as Ctrl and Alt on win/linux)? Ye

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Jean-Marc Lasgouttes wrote: ... Note that Apple Publications Style Guide, in the "Style and Usage" section, recommends to use Command- and Option- (not Cmd and Opt). ... Command key: On first use in print user documentation, identify the Command key with its symbol: Command ([symbol here]) ke

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Jürgen Spitzmüller wrote: Jean-Marc Lasgouttes wrote: *** For LyX 1.6.0 *** The attached patch. Quick and dirty, but does the job. IMO a MUSTFIX, the userguide should compile. This strikes me as a good idea actually. OTOH the unicodesymbols file should not output anything else then a proper

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: > IMHO we should rather introduce something like a > KeySequence::print(KeySequence::DocOutput) > that could replace any non-representable character by a description instead > of > abusing the unicodesymbols file. Yes. Our problem right now is that

Re: Problem with Mac-Key-Symbols (MUSTFIX)

On Mon, Oct 27, 2008 at 9:15 AM, Jürgen Spitzmüller <[EMAIL PROTECTED]> wrote: > Jean-Marc Lasgouttes wrote: >> > *** For LyX 1.6.0 *** >> > The attached patch. >> > Quick and dirty, but does the job. IMO a MUSTFIX, the userguide should >> > compile. >> >> This strikes me as a good idea actually. >

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Jean-Marc Lasgouttes wrote: > > OTOH the unicodesymbols file should not output anything else then a > > proper representation of the given glyph. In the context of InsetInfo > > this might be correct, but what if someone wants to use the symbols > > themselves? > > We have no solution for using the

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: > OTOH the unicodesymbols file should not output anything else then a proper > representation of the given glyph. In the context of InsetInfo this might be > correct, but what if someone wants to use the symbols themselves? We have no solution for u

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Jean-Marc Lasgouttes wrote: Konrad Hofbauer <[EMAIL PROTECTED]> writes: At the same time your email came in, I was in the middle of putting this into bugzilla. Should I still hit "submit" ? Please do. I got an internal server error, nevertheless this now seems to be:

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Jean-Marc Lasgouttes wrote: > > *** For LyX 1.6.0 *** > > The attached patch. > > Quick and dirty, but does the job. IMO a MUSTFIX, the userguide should > > compile. > > This strikes me as a good idea actually. OTOH the unicodesymbols file should not output anything else then a proper representat

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Konrad Hofbauer <[EMAIL PROTECTED]> writes: > At the same time your email came in, I was in the middle of putting > this into bugzilla. Should I still hit "submit" ? Please do. JMarc

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Jean-Marc Lasgouttes wrote: Konrad Hofbauer <[EMAIL PROTECTED]> writes: I proposose: *** For LyX 1.6.0 *** The attached patch. Quick and dirty, but does the job. IMO a MUSTFIX, the userguide should compile. This strikes me as a good idea actually. How well does it work? It works perfectly.

Re: Problem with Mac-Key-Symbols (MUSTFIX)

> >> 2) InsetInfo->shortcut and InsetInfo->shortcuts do not do the same >> thing with respect to Mac Keybindings. Somebody else will need to fix >> this. > > I'll have a look. Thanks. I was concerned with this problem as well but I did not have a mac. Bo

Re: Problem with Mac-Key-Symbols (MUSTFIX)

Konrad Hofbauer <[EMAIL PROTECTED]> writes: > I proposose: > > *** For LyX 1.6.0 *** > The attached patch. > Quick and dirty, but does the job. IMO a MUSTFIX, the userguide should > compile. This strikes me as a good idea actually. How well does it work? Note that Apple Publications Style Guide,

Problem with Mac-Key-Symbols (MUSTFIX)

I am a bit in a hurry now, but: In rc4 the UserGuide does not compile on the Mac because it uses InsetInfo->Shortcuts which outputs the pretty unicode symbols ⌘⌥⇧, but for which no Latex equivalent is there. I proposose: *** For LyX 1.6.0 *** The attached patch. Quick and dirty, but does the