On Feb 19, 2012, at 1:36 PM, stefano franchi wrote:
> I am forwarding to the users' list. This problem starts to exceed my
> lyx/Latex skills. What I can say is this:
>
> If I:
>
> 1. Import your file with the modified latex converter
>
> 2. Change fonts to non-latex
>
> 3. Select full-cov
On Sun, Feb 19, 2012 at 11:00 AM, Eric Weir wrote:
>
> On Feb 19, 2012, at 9:54 AM, stefano franchi wrote:
>
> On Sun, Feb 19, 2012 at 5:13 AM, Eric Weir wrote:
>
>
> On Feb 18, 2012, at 8:16 AM, Eric Weir wrote:
>
>
> After both types of imports I get the following message: "Could not find
>
> L
On Feb 18, 2012, at 8:16 AM, Eric Weir wrote:
> After both types of imports I get the following message: "Could not find
> LaTeX command for character''(code point 0x2028)
> Some characters of your document are probably not representable in the chosen
> encoding. Changing the document encoding
On Feb 17, 2012, at 9:36 AM, Eric Weir wrote:
> On Feb 16, 2012, at 7:47 PM, stefano franchi wrote:
>
>> try this workaround to the workaround. Instead of creating a new
>> converter, simply go to the existing LAtex(plain-->lyx converter, look
>> at the command string (the tex2lyx etc.) and stic
On Feb 16, 2012, at 10:45 AM, stefano franchi wrote:
> On Thu, Feb 16, 2012 at 9:40 AM, Eric Weir wrote:
>>
>> On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
>>
>>> On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir wrote:
>>>
Thanks, Stefano. Don't see how to do that, either. Scrivener do
On Thu, Feb 16, 2012 at 9:40 AM, Eric Weir wrote:
>
> On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
>
>> On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir wrote:
>>
>>> Thanks, Stefano. Don't see how to do that, either. Scrivener does not
>>> appear on the dropdown list. Perhaps there is somethin
On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
> On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir wrote:
>
>> Thanks, Stefano. Don't see how to do that, either. Scrivener does not appear
>> on the dropdown list. Perhaps there is something on the list that would
>> stand in for the Scrivener ou
On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir wrote:
>
> On Feb 15, 2012, at 1:57 PM, stefano franchi wrote:
>
>>> On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
>>>
3. In Tools>>Preferences>>FIle Converters, create a new converter from
Scrivener to Lyx: select "Scrivener" in the From
On Feb 15, 2012, at 1:57 PM, stefano franchi wrote:
>> On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
>>
>>> 3. In Tools>>Preferences>>FIle Converters, create a new converter from
>>> Scrivener to Lyx: select "Scrivener" in the From dropdown list, and
>>> "Lyx" in the "to list. Enter the c
On Wed, Feb 15, 2012 at 10:59 AM, Eric Weir wrote:
>
> On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
>
>> 3. In Tools>>Preferences>>FIle Converters, create a new converter from
>> Scrivener to Lyx: select "Scrivener" in the From dropdown list, and
>> "Lyx" in the "to list. Enter the call to
Am 15.02.2012 um 17:59 schrieb Eric Weir:
>
> On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
>
>> 3. In Tools>>Preferences>>FIle Converters, create a new converter from
>> Scrivener to Lyx: select "Scrivener" in the From dropdown list, and
>> "Lyx" in the "to list. Enter the call to tex2ly
On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
> 3. In Tools>>Preferences>>FIle Converters, create a new converter from
> Scrivener to Lyx: select "Scrivener" in the From dropdown list, and
> "Lyx" in the "to list. Enter the call to tex2lyx with the UTF8 switch
> in the "Converter field":
>
On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
> following on Enrico's excellent suggestion, here is how you can solve
> your Scrivener-related problem in a Lyx-way. The developers are
> working on a permanent solution, it seems. So this may turn
> unnecessary very shortly. At any rate, her
On Wed, Feb 15, 2012 at 5:45 AM, Eric Weir wrote:
>
> On Feb 14, 2012, at 4:47 PM, Enrico Forestieri wrote:
>
>> Eric Weir writes:
>>> I'm attempting to use the workaround suggested by Stefano to get LyX to
>>> recognize a Unicoded document as Unicoded. The workaround involves use
>>> of the tex2
On Feb 14, 2012, at 4:47 PM, Enrico Forestieri wrote:
> Eric Weir writes:
>> I'm attempting to use the workaround suggested by Stefano to get LyX to
>> recognize a Unicoded document as Unicoded. The workaround involves use
>> of the tex2lyx command.
>>
>> I'm on a Mac. When I run the command I
Eric Weir writes:
> I'm attempting to use the workaround suggested by Stefano to get LyX to
> recognize a Unicoded document as Unicoded. The workaround involves use
> of the tex2lyx command.
>
> I'm on a Mac. When I run the command I get a command not found message.
> When I do locate tex2lyx, h
On Tue, Feb 14, 2012 at 11:18 AM, Eric Weir wrote:
>
> On Feb 14, 2012, at 11:07 AM, BH wrote:
>
>> I'm guessing the problem is that tex2lyx isn't in your PATH, which
>> means you must provide it yourself. So from the Terminal, you should
>> type, for example,
>>
>> /Applications/LyX.app/Contents/
On Feb 14, 2012, at 11:07 AM, BH wrote:
> I'm guessing the problem is that tex2lyx isn't in your PATH, which
> means you must provide it yourself. So from the Terminal, you should
> type, for example,
>
> /Applications/LyX.app/Contents/MacOS/tex2lyx
Thanks, Will do. But while I'm at it, is ther
On Tue, Feb 14, 2012 at 10:54 AM, Eric Weir wrote:
>
> Just correcting a typo in the subject heading.
>
> --
>
> I'm attempting to use the workaround suggested by Stefano to get LyX to
> recognize a Unicoded do
Just correcting a typo in the subject heading.
--
I'm attempting to use the workaround suggested by Stefano to get LyX to
recognize a Unicoded document as Unicoded. The workaround involves use of the
tex2
20 matches
Mail list logo
