Re: hf-tikz.sty on fedora 16
On 06/06/2013 7:37 PM, Patrick Dupre wrote:
Hello,
I am trying to install hf-tikz.sty and colortbl.sty (from colortbl.zip) on a
fedora 16.
Where should I installed them ?
I tried:
/usr/share/texmf/tex/latex/base
but there are not found.
Did you run texhash?
So I put them in a special directory where latex can read them, but
I get:
)) (/usr/share/texmf/tex/generic/pgf/frontendlayer/tikz.code.tex
Package: tikz 2006/10/17 v1.10 (rcs-revision 1.68)
This version of tikz is very old, and likely incompatible with hf-tikz.sty
(/usr/share/texmf/tex/generic/pgf/libraries/pgflibraryplothandlers.code.tex
File: pgflibraryplothandlers.code.tex 2006/10/16 v1.10 (rcs-revision 1.8)
\pgf@plot@mark@count=\count183
\pgfplotmarksize=\dimen232
)
\tikz@lastx=\dimen233
Normal \dimen register pool exhausted, switching to extended pool.
\tikz@lasty=\dimen256
\tikz@lastxsaved=\dimen257
\tikz@lastysaved=\dimen258
\tikzleveldistance=\dimen259
\tikzsiblingdistance=\dimen260
\tikz@figbox=\box84
\tikz@tempbox=\box85
\tikztreelevel=\count184
\tikznumberofchildren=\count185
\tikznumberofcurrentchild=\count186
\tikz@fig@count=\count187
\tikz@expandcount=\count188
(/usr/share/texmf/tex/generic/pgf/libraries/pgflibrarytikztopaths.code.tex
File: pgflibrarytikztopaths.code.tex 2006/10/16 v1.10 (rcs-revision 1.5)
)))
! I can't find file `pgflibrarytikzshadings.code.tex'.
...t pgflibrarytikz\pgf@temp .code.tex
\catcode `\@ =\csname tikz...
l.22 \usetikzlibrary{shadings}
Please type another input file name
! Emergency stop.
...t pgflibrarytikz\pgf@temp .code.tex
\catcode `\@ =\csname tikz...
l.22 \usetikzlibrary{shadings}
*** (job aborted, file error in nonstop mode)
I cannot find a pgflibrarytikzshadings.code.tex file.
What should I do?
Update your TeX distro.
--
Julien
Re: How to fully specify preamble
On 2013-06-15, Pietro Cortese wrote:
> [-- Type: text/plain, Encoding: --]
> Hello,
> I imported a latex template file from a project I'm working on. The project
> defined a latex preamble that conflicts with the elements that are added by
> default by lyx, therefore I need to export to latex and change the preamble
> before compiling my contribution.
> Is there a way to avoid lyx filling the preamble with its definitions?
> \usepackage[latin9]{inputenc}
> \setcounter{secnumdepth}{3}
> \setcounter{tocdepth}{3}
> \usepackage{amsmath}
> \usepackage{amssymb}
> \usepackage{graphicx}
> \makeatletter
Under Document>Settings:
You can disable the automatic loading of amsmath and amssymb.
You can change the used input encoding.
You can (probably) remove the "tocdepth" setting.
I find it convenient to open View>Source, show the complete document, and
start experimenting with the Document>Settings (applying every now and then
and checking the result).
Günter
Re: error - could not find Latex command for character
On 2013-06-16, Alexandru Cabuz wrote:
...
> I am using the Romanian Standard keyboard layout, which uses diacritics
> with comma-below, such as ș and ț.
> They appear correctly in BOTH the interface and the pdf output, except I
> still get the popup with the error:
> Could not find Latex command for character 'ș' (code point 0x219).
> Some characters of your document are probably not representable in the
> chosen encoding.
> Changing the document encoding to utf8 could help.
> This error seems to be pointless. How can I get rid of it?
What "LaTeX encoding" do you use? Maybe it is "latin10", which fakes the
comma-below accent:
\ProvideTextCommandDefault\textcommabelow[1]
{\hmode@bgroup\ooalign{\null#1\crcr\hidewidth
\raise-.31ex\hbox{\check@mathfonts
\fontsize\ssf@size\z@
\math@fontsfalse\selectfont,}\hidewidth}\egroup}
Does it work, if you copy and past from the PDF or
search for a word with comma below accented character(s)?
> I have searched through the user archives, including the old archives,
> could not find an answer to this.
The problem is that:
* LaTeX has no proper support for the comma below.
http://tug.org/pipermail/tex-live/2008-August/017204.html
http://en.wikipedia.org/wiki/Romanian_alphabet#.28La.29TeX
* LyX has no mapping for the Unicode characters with comma below.
#0x0218 "" "" "" # LATIN CAPITAL LETTER S WITH COMMA
BELOW
#0x0219 "" "" "" # LATIN SMALL LETTER S WITH COMMA BELOW
#0x021a "" "" "" # LATIN CAPITAL LETTER T WITH COMMA
BELOW
#0x021b "" "" "" # LATIN SMALL LETTER T WITH COMMA BELOW
We could add the fallback overlay definition from latin10.def and
use \textcommabelow{} in the "unicodesymbols" Unicode -> LaTeX mapping.
* A proper solution would be to use XeTeX or LuaTeX engines and
Unicode-encoded fonts (Document>Settings>Fonts>use non-TeX fonts).
Günter
Re: Hyphenation problem
On 06/15/2013 05:10 PM, Liviu Andronic wrote:
> On Sat, Jun 15, 2013 at 2:48 AM, Louis Turk
> wrote:
>> Hi lyxers,
>>
>> I'm having a perplexing problem. I'm using the Cardo font, which enables the
>> use of English, Hebrew, and Greek on the same page easily. But I can't get
>> curl quotes to work. They work with this font in Open Office. So why not in
>> Lyx?
>>
> Is this hyphenation or quotes issue? If it's quotes, did you play with
> Document > Settings > Language > Quotes? If it doesn't help, please
> provide a _minimal_ example of your document.
>
> Liviu
>
>
>> Louis
>>
This line solved my problem:
\setmainfont[Ligatures=TeX]{Cardo}
That Liviu for your willingness to help.
Louis
error - could not find Latex command for character
Hello, Question on v2.0.3, debian wheezy. I am using the Romanian Standard keyboard layout, which uses diacritics with comma-below, such as ș and ț. They appear correctly in BOTH the interface and the pdf output, except I still get the popup with the error: Could not find Latex command for character 'ș' (code point 0x219). Some characters of your document are probably not representable in the chosen encoding. Changing the document encoding to utf8 could help. This error seems to be pointless. How can I get rid of it? I have searched through the user archives, including the old archives, could not find an answer to this. Thank you! -- Alexandru I. Cabuz Tel: +40 (0)722.478.168 --- Please no Word or Powerpoint attachments. Send plain text, rich text format, html, or pdf instead. See http://www.gnu.org/philosophy/no-word-attachments.html
