On Sep 23, 2010, at 11:10, JiHO wrote:
> On Wed, Sep 22, 2010 at 18:51, Christiaan Hofman <[email protected]> wrote:
>>> I have few questions:
>>> - what are stringByDeTeXifyingString and stringByTeXifyingString
>>> supposed to do? Neither of those does anything: when I have latex
>>> commands (\textit, \circ etc.) they do not replace, apply, or suppress
>>> them.
>>
>> They replace tex commands that are also used as escapes, such as {\'e}, and
>> they also clean some braces. They certainly do not convert all tex commands,
>> because we're not a tex parser.
>
> Ok. An I guess DeTeXifying means removing those commands without
> affecting the output while TeXifying is converting those commands into
> their RTF equivalent. i.e.:
> {\'e} -- DeTeX --> e
> {\'e} -- TeX --> é
> Is that right?
That's correct.
> If it is, what is the difference between DeTeX and stringByRevingTeX?
>
I assume you mean stringByRemovingTeX. That's very different, it removes tex
commands.
>>> - I am using a table with one line and two columns. Whether its width
>>> is specified as 100% or unspecified, it seems limited to a maximum
>>> with (it does not take the whole width when bibdesk is maximized on a
>>> large screen). Is that expected also?
>>> - More generally, I find that BD renders the HTML differently from
>>> Safari (of CSS Edit). For example, it does not seem to honor the
>>> padding settings on <p> elements.
>>>
>>
>> It's converted to rich text (NSAttributedString), and rich text support for
>> html is limited wrt the webview.
>
> OK, so I am actually better off doing everything in RTF directly then.
I think so.
> My only big remaining issue is that BibDesk template values are not
> expanded within links. For example if I have an RTF file with a only a
> link to the DOI:
>
> {\rtf1\ansi\ansicpg1252\cocoartf1038\cocoasubrtf320
> {\fonttbl\f0\froman\fcharset0 Palatino-Roman;}
> {\colortbl;\red255\green255\blue255;}
> {\info
> {\author
> Foo}}\paperw11900\paperh16840\margl1440\margr1440\vieww9000\viewh8400\viewkind0
> \pard\tx566\tx1133\tx1700\tx2267\tx2834\tx3401\tx3968\tx4535\tx5102\tx5669\tx6236\tx6803\ql\qnatural\pardirnatural
> {\field{\*\fldinst{HYPERLINK "http://dx.doi.org/%3C$string.Doi/%3E"}}{\fldrslt
> \f0\fs22 \cf0 <$string.Doi/>}}}
>
> The "<$string.Doi/>" element of the link is converted by TextEdit in
> HTML entities: "%3C$string.Doi/%3E". Even if I replace the %3*
> commands by < and > with a plain text editor, the link still points to
> http://dx.doi.org/<$string.Doi/> and not to the expanded form (i.e.,
> not the actual value of the DOI).
I am not sure what your'e doing here, but you're not doing something you're
supposed to do. Don't mess with the RTF data directly, that won't be
interpreted as the template, the rich text you see in a rich text editor will
be.
Also, I don't know what <$string.Doi/> should stand for? I think you want
something like <$urls.Doi/>.
> Is there any way that BibDesk can
> expand template values in links.
>
Use the "linkedText" key, e.g. <$urls.Doi.linkedText/>.
> As a subsidiary question: I can't seem to be able to edit the
> appearance of links in RTF. They always are underlined and blue. Is it
> impossible to have them look like regular text?
>
Not as far as I know.
> Thanks in advance,
>
> JiHO
> ---
> http://maururu.net
Christiaan
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
