CJK-Latex

I use latex a lot to write my lab reports for physics. Everything works fine, I am using the vim latex-suite from aur and tetex. Now i need to write a paper for linguistics and I'd like to use latex for it since it has very nice fonts for the phonetic alphabet. the problem is that I also need to use japanese characters in the paper. I tried installing cjk-latex following this website
http://www.physics.wustl.edu/~alford/te … latex.html but my documents just show blank where the japanese text should go.
Has anybody successfully installed cjk-latex in archlinux?
Any help or information would be greatly appreciated.
Thanks

See http://alexkrispin.wordpress.com/2010/0 … eshooting/
I know you are not using xelatex. However, I think that if you have the texlive fonts added to fontconfig's cache, that xelatex will find those which are good for Japanese along with other system fonts which are suitable for Japanese (but won't work with regular latex). I haven't tried this but it looks at least plausible.

Similar Messages

XML Publisher for CJK Support

Hi,
How to make xml publisher support cjk characters in pdf format?
In xml publisher template tab, I can preview my report in html/excel/rtf formats correctly, but in pdf format cjk characters become '?????'.
It seems like some fonts for pdf are miss.
Is there any setting need to be checked again, please?
I use Xml publisher 5.5 to create my rtf template, and my apps server version is 11.5.10.2.
The url below might have some hints, but I can't open it.
http://www.oracle.com/technology/products/xml-publisher/resource/XMLP_LOCALIZATION.html
Help on this will be really appreciated.
Thank you and best regards,
Zhxiang

Hi,
It seems that we should to write a xdo.cfg file and put that in $AF_JRE_TOP/lib.
is it right??
thanks and best regards,
zhxiang
e.g. xdo.cfg
<config version="1.0.0" xmlns="http://xmlns.oracle.com/oxp/config/">

<properties>

<property name="system-temp-dir">/tmp</property>

<property name="pdf-compression">true</property>

<property name="pdf-security">true</property>
<property name="pdf-open-password">user</property>
<property name="pdf-permissions-password">owner</property>
<property name="pdf-no-printing">true</property>
<property name="pdf-no-changing-the-document">true</property>
</properties>


<fonts locales="zh-TW">
<truetype path="/fonts/ALBANWTT.ttf" />
</fonts>
<fonts>

<font family="Arial" style="normal" weight="normal">
<truetype path="/fonts/Arial.ttf" />
</font>
<font family="Default" style="normal" weight="normal">
<truetype path="/fonts/ALBANWTJ.ttf" />
</font>

<font-substitute name="MSGothic">
<truetype path="/fonts/msgothic.ttc" ttcno="0" />
</font-substitute>
</fonts>
</config>

HT5361 Is it possible to embed raw latex into a mail message to display an equation?

Hi,
Is it possible to embed raw latex (or any other meta data format like HTML) into a mail message? I would really like to be able to send equations directly without converting them to PDF or GIF first.
Thanks,
Joe

I just borrowed a quadratic equation from the MathML Wikipedia site and grafted it into an HTML document. It imaged fine in Safari 7. It should be noted that neither the latest Google Chrome or FIrefox rendered the same content accurately.
Laying out your entire email message (including MathML) in HTML can be tedious. Once it is displayed in the browser, each use of the command+I will put the browser content in a new Mail compose window. So, you cannot add an equation to existing Mail composition. Select, copy and paste (or paste and match style) will not work either.
Depending on the importance you place on email equations, at one time, Design Science (MathType) claimed compatibility with Apple Mail (4.5) where you could input your equation in MathType and it could then be placed within the email. The mail recipient would not need a copy of MathType installed for this to work. MathType even allows you to key your equation in with LaTeX syntax to generate the equation.
You could check with them about functionality (or restrictions) with Mail 6 and 7 on OS X, as it might provide a more productive way to achieve your goals.

How to handle TeX/LaTeX equations in InDesign?

Hi All,
I've recd. a request to handle one of the title already done in LaTeX software in InDesign, for this I need to do the below tasks:
(1) Need to convert the LaTeX data to load in InDesign
(2) Need to convert the equations done with LaTeX coding as equation objects in InDesign
(3) Need to retain the LaTeX links to work in InDesign, so that while generating the PDF, these links should be worked
So pl. give me your suggestions to handle the above mentioned tasks. I know I can use the third-party tool called 'MathMagic' to handle point 2 (but this tool seems expensive), but I need to know whether any other easy methods to handle. I'm using InDesign - CS3 (Windows)
Thanks,
Praveen

Hi Peter,
Thanks for the response.
For points 1 and 3, I decided to convert the LaTeX contents to XML to fix the linking using automation thro' JS. For point 2, I'm still studying to find a solution and since this is the first time we've recd. this request, we're not ready to invest for one title.
Thanks again,
Praveen

Learning LaTeX, is it Worth It?

I've been motivated lately to look more in depth at LaTeX and knew ahead of time that there would be a steep learning curve. I've read arooaroo's Getting to Grips with LaTeX tutorials, and also the The not so Short Introduction to LaTeX and have messed around a bit with various examples using the <code>teTeX</code> package available in extra.
Anyway, I'm wondering if LaTeX is really all that beneficial to a guy who just likes the idea of separation of presentation and content, wants to get away from bloated WYSIWYG editors, and doesn't really have plans on writing long research papers/books/articles. I would love use it for regular small papers and possibly coding project documentation, etc. I really like the fact that it's plain text, and thus easy to use version control with as well. I think it has a ton of great features versus other methods of creating documents, but it also has a lot of drawbacks in my eyes.
The problem is not memorizing the syntax, but all of the different packages you can get, many of which do the same thing and not in consistent ways...it gets confusing fast. Just inserting graphics into a document, or converting it to PDFs can be done by multiple packages/commands. If you want graphics that will eventually end up in a pdf file, then you have to go a whole other direction (no longer converting to EPS, blah blah blah). How do you find out the most common/appropriate package for your purposes? Even the math related functions that LaTeX is so famous for requires differing packages according to what you want to display (the math stuff is cool, but I probably wouldn't use it much). I also think it's strange that you are forced to run the command <code>latex</code> multiple times when doing things like building a table of contents or an index page...why can't it just run through it multiple times automatically?
Plus customization of styles seems overly hard...yes I know that the default styles are very well researched and thought out and look very professional, but I'd still like to be able to change things easily when necessary. I don't like the idea of every single document being produced looking exactly the same. I know a lot about graphic design and typography, etc. and feel like LaTeX might hold me back some. I like the level of detailed control it gives you over your writing's semantics, but the design side of things seems too set in stone.
Anyway, I'm just not sure that LaTeX is for me...how do other people feel about it? Are there other systems out there like it? Am I really stuck in the world of OO.org and Word to do what I want?

I switched to LaTeX within the last five months or so, only a little after I switched to Arch. I just graduated, I was an English major, and just immediately started writing short assignments in LaTeX based on the easy examples people gave. My early documents look like default LaTeX, but I later got the hang of making everything look the way I wanted. I actually ended up writing a senior english thesis (~85 pages) in LaTeX. I used Chicago style citations, and found LaTeX's references and BibTeX not very worth it for this -- instead I just used my own macros. This not only made citations easy and consistent for me, but also allowed me to index things very easily.
In the end, I had an incredibly beautiful, easy to read thesis, with nice headings, consistent style, table of contents, bibliography, index, etc. Although I spent a lot of time learning how to format things in LaTeX (which was occasionally distracting), I don't think that I could have made anything comparable in a WYSIWYG editor, even had I spent more time on it.
I wrote it completely in vim. I used a lot of splits and vsplits, since I divided the chapters into different files for such a long document, and I got very quick at finding things, although I must admit everyone else found it very strange looking.
One thing that will make your life easier is called latexmk, it's a perl script that will run LaTeX as many times as necessary. It has a few cool options:
latexmk.pl file.tex makes the file, running whatever needs to be run
latexmk.pl -pdf file.tex makes a pdf
latexmk.pl -pvc runs it in continuous preview mode, meaning every time you save the text file, it will run LaTeX, and you can view it in another window
I personally used a bunch of autocmd in vimrc to nmap latexmk.pl and xdvi to make it easy to update and view LaTeX files. I'm sure some people would find this too much work, but if you already love vim, I think it's a good solution.
Since then I've used LaTeX for many other purposes, papers, letters, resumes, etc. It's a beautiful program if you ask me, and only took me a few months to "master" it, at least to the point that I'm very happy with everything I create in it.

Font problem in Latex

After a fresh install of Leopard I tried to use 'LatexIt' or 'Latex Equation Editor' for nice equations in Keynote. I obviously need Latex for that, and I installed Latex via fink. But unfortunately, something goes wrong: the equations that are created are not using the Computer Modern font and they look ugly or completely wrong. In Tiger it looked so nice!
So, then I tried latex by hand: I make a .tex file, and
I can generate a beautiful .dvi from a .tex file (it looks perfect in xdvi),
I can generate a beautiful .ps from a .dvi file (it looks perfect in gv),
but I cannot generate a .pdf from a .ps (bad fonts again). I tried to use
both pstopdf, and the automatic conversion by Preview, both with the
same poor results.
Then I manually added the CM fonts in FontBook, but it does not seem to
make any difference.
Now I don't know what to do. Can somebody give me a suggestion how to
create good pdfs again?

Just a long shot, but have you tried to toggle syntax highlighting on and off in the preferences "Source" tab? That will rewrite the color table for the source editor. The "Console" foreground color is is set in the "Console" tab of the preferences.
All colors are stored in the user preferences file:
~/Library/Preferences/TeXShop.plist
If you cannot change the colors using TeXShop's Preferences panel, the preferences file may be corrupted. Then I'd try to quit TexShop and to remove this preferences file.
Regards
Léonie

LaTeX composition in (g)vim with live update-as-you-type PDF preview

Ever since I tried the gummi LaTeX editor, I've been intrigued by the idea of having a live-updating PDF preview--i.e., a PDF output panel which updated as I typed. This provides all the good things of WYSIWYG, but without taking away the control I have by editing the source directly. However, apart from its preview panel, I was thoroughly unimpressed with gummi as an editor. It had none of the advanced features I was used to.
Since then, I've been trying various techniques to make it work with my preferred editor, (g)vim. At first, I used latexmk with the -pvc option which recompiles whenever the file changes, along with a PDF editor that refreshes whenever the file changes (like evince); but found it slow and tended to get stuck.
My current method is to use mupdf as my viewer, with a custom LaTeX script which calls xdotool to update mupdf whenever I have a successful compilation. This seems to be working fairly well.
Here's an animated GIF screen capture showing it in action
There is typically still a 1-second delay between typing something and it showing on the PDF preview, but it's not really any worse than it seems to be wih gummi, and I get to use a world-class editor.
I should note that I'm not using the vim-latex suite plugin or anything similar, so I don't know whether or not any of this is compatible.
Anyway, I thought I'd post my method here just in case anyone thought it useful, or more importantly, anyone had any feedback for how it might be improved. I'm not a programmer (--my degrees are in philosophy!--) and don't really have that much experience with vim or bash scripting, so forgive my naive methods.
Anyway, in my ~/.vim/ftplugin/tex.vim I have:
" Function to save, check if already compiling and compile if not
function! KKLtxAction()
" go to right directory
lcd %:p:h
" save the file if need be and it's possible
if filewritable(bufname("%"))
silent update
endif
" see how many kkltx processes there are
" note that there are always 3 when the checking itself happens
" so we need there to be no more than that
let numrunning = system("ps ax | grep kkltx | wc -l")
if numrunning < 4
exec "silent !kkltx " . expand("%") . " &"
endif
endfunction
" Call this function whenever mupdf the cursor moves
" But only in gvim
if has("gui_running")
au CursorMoved *.tex call KKLtxAction()
au CursorMovedI *.tex call KKLtxAction()
endif
So whenever the cursor moves, the file saves and checks if the compilation script is running. If it is not, it runs it. Here's the script, named kkltx. (To make it work, create a ~/.config/kkltx folder. Sorry about the stupid name; I needed it to be uncommon.)
#!/bin/bash
file="$1"
logfile="${file%.tex}.log"
auxfile="${file%.tex}.aux"
# check to see when file was last saved and
# check see what version of file was last compiled
currmodified=$(stat -c %Y "$file")
oldmodified=$(cat $HOME/.config/kkltx/lastprocessedfile)
# if they're the same exit with no change
if [ "$currmodified" == "$oldmodified" ] ; then
echo "nochange"
exit 0
else
# if compilation is necessary, check what program to use
# 'xelatex' should appear in first 5 lines for xelatex docs
if head -n 5 "$file" | grep -i -q 'xelatex' > /dev/null 2>&1 ; then
execprog="xelatex"
else
execprog="pdflatex"
fi
# try to compile
if ${execprog} -interaction=batchmode -file-line-error -synctex=1 "$file" > /dev/null 2>&1 ; then
# if compiling worked check if bibtex needs to run
if cat "$logfile" | grep -i -q 'undefined citations' > /dev/null 2>&1 ; then
if bibtex "$auxfile" > /dev/null 2>&1 ; then
if ! ${execprog} -interaction=batchmode -file-line-error -synctex=1 "$file" > /dev/null 2>&1 ; then
echo "failure"
exit 1
fi
else
echo "bibfail"
exit 2
fi
fi
# check if a rerun is necessary to update cross-references
if cat "$logfile" | grep -i -q 'rerun to get' > /dev/null 2>&1 ; then
if ! ${execprog} -interaction=batchmode -file-line-error -synctex=1 "$file" > /dev/null 2>&1 ; then
echo "failure"
exit 1
fi
fi
# update mupdf by sending the r key to it
xdotool search --class mupdf key --window %@ r > /dev/null 2>&1
echo "success"
# save time of compilation
echo -n "$currmodified" > "$HOME/.config/kkltx/lastprocessedfile" 2>/dev/null
else
echo "failure"
exit 1
fi
fi
exit 0
One thing you miss out on with mupdf is the SyncTeX ability in, e.g., TeXworks that allows you jump from the source to the corresponding part of the PDF and vice-versa. Here's a kludge that at least gets to you to the right page by using xdotool to send the signal to move to a certain page matching the source, or to read what page mupdf is on, and move to the beginning of the source code for that page (or strictly, a couple inches over and down). Again, in my ~/.vim/ftplugin/tex.vim
" \v to open the viewer
nnoremap \v :exec "silent! !mupdf ".expand("%:r").".pdf &"
" forward search with mupdf
function! MuPDFForward()
" make sure I'm in the right directory
lcd %:p:h
let pageforward = 0
" find where I am now; adjust for starting with 0
let searchline = line(".") + 1
let searchcol = col(".") + 1
" use synctex to find the page to jump to
let pageforward = system("synctex view -i " . searchline . ":" . searchcol . ":\"" . expand("%") . "\" -o \"" . expand("%:r") . ".pdf\" | grep -m1 'Page:' | sed 's/Page://'")
" if a page other than 0 is found, send the page number to mupdf
if pageforward > 0
call system("xdotool search --class mupdf type --window %1 \"" . pageforward . "g\"")
endif
endfunction
" inverse search with mypdf
function! MuPDFReverse()
lcd %:p:h
let gotoline = 0
" call a script which returns the line number near start of page shown on mupdf
let gotoline = system("syncreverse-mupdf.sh " . expand("%:p:r"))
if gotoline > 0
exec ":" . gotopage
endif
endfunction
" mappings \f and \r for forward and reverse search
nnoremap <buffer> \f :call MuPDFForward()<CR>
nnoremap <buffer> \r :call MuPDFReverse()<CR>
Here is the script syncreverse-mupdf.sh called by the above:
#!/bin/bash
# syncreverse.sh full-path-of-PDF-minus-extension
pathfn="$1"
# reduce filename to base, add .pdf
pdffile="$(echo "$pathfn" | sed 's@.*/@@g').pdf"
# change to directory containing files
cd "$(echo "$pathfn" | sed 's@$.*$/[^/]*@\1@g')"
# read page number in mupdf window title
page=$(xdotool search --class mupdf getwindowname | sed 's:.* - $[0-9]*$/.*:\1:')
# synctex lookup; remove junk
line=$(synctex edit -o "$page:288:108:$pdffile" | grep -m1 'Line:' | sed 's/Line://' | head -n1)
line=$(echo "$line" | sed -n 's/$[0-9]*$.*/\1/p')
# return line for gvim
echo "$line"
exit 0
I also recommend putting mappings in vim to send keys to mupdf to move around, so you can move around in the preview but without making (g)vim lose focus. These are just examples.
nnoremap <silent> <buffer> <C-PageDown> :silent! call system("xdotool search --class mupdf key --window %@ Page_Down")<CR>
nnoremap <silent> <buffer> <C-PageUp> :silent! call system("xdotool search --class mupdf key --window %@ Page_Up")<CR>
Anyway, these could definitely be improved, by, for example, accommodating master/sub-documents, and so on. Thoughts?
Last edited by frabjous (2010-11-04 22:41:21)

OK, I've uploaded a PKGBUILD to AUR. Since I've changed how it handles recognizing when it's safe to recompile, it no longer needs to have a weird name. The name is now:
vim-live-latex-preview
It comes with a very short vim help file, which I'll copy here.
*live-latex-preview.txt* For Vim version 7.3. Last change: 2010 Oct 27
*live-latex-preview*
A plugin for creating a live-updating PDF
preview for a LaTeX file in MuPDF
Default key bindings:~
\p = Begin auto-compilation and launch MuPDF preview.
\o = End auto-compilation and close MuPDF preview.
\s = Check the result of the last compilation;
jump to first error in case of errors.
\f = Forward search to page in PDF matching cursor
position in source.
\r = Reverse/inverse search to position in source
matching active page in MuPDF. (Very approximate.)
\<PageUp>, \<PageDown>, \<Up>, \<Down>, \<Right>, \<Left>, \G
\m, \t, \-, \+, \= = Send the corresponding keystrokes
to the MuPDF preview without losing focus on vim Window
The '\' can be changed by changing <LocalLeader>.
Be aware that your file is saved whenever the cursor moves. Be sure
to take the appropriate measures to keep back-up saves and undo files
so you can undo changes if need be.
To compile with XeLaTeX rather than PDFLaTeX, include the string
'xelatex' somewhere in the first five lines of your file (e.g., in a
comment). Currently only PDFLaTeX and XeLaTeX are supported. (Support
for LuaLaTeX and/or LaTeX > dvips > ps2pdf may be added in the future,
but they may be too slow for the live updating process anyway.)
The plug-in does not currently support master- and sub-documents
via LaTeX's \input{...} and \include{...} mechanisms. This may be
added in the future.
vim:tw=78:ts=8:ft=help:norl:
This is a new version; pretty much completely rewritten from the above. In particular, I've tried to incorporate keenerd's ideas; in particular some changes:
Rather than grepping the active processes, when it begins a compilation, it records the process ID of the compilation script, and will not begin a new compilation until that process finishes.
When it first launches MuPDF, it records the Window ID and sends it back to vim, so vim knows which instance of MuPDF to refresh or work with.
I've added a \s quick key which provides a one-word summary of the effects of the last compilation and jumps to the line number of the first error, if there were errors.
The script is located in a separate file in the main $VIMRUNTIME/ftplugin folder, rather than a user's tex.vim file.
I'm sure there's still plenty of room for improvement. I'd still like to get it to handle master/sub-documents well, for example. All comments welcome.

How to insert a LaTeX equation in a quiz? Captivate 8

How to insert a LaTeX equation in a quiz? Captivate 8

Video was based on an explanations somewhere on my blog, both for replay and for audio (in 6-7: http://blog.lilybiri.com/toggle-shape-buttons). Same for the mute button, where I told the author that there is a bit of a maths mistake in his expression:
Expression cpCmndMute = 1 - cpCmndMute
He reversed it, which will lead to negative 1. Lucky for him that Captivate doesn't understand negative numbers, -1 will be translated to +1. But as an engineer, this feels terribly wrong to me. I don't know why he deleted my comment....
Sorry for ranting...
As for a replay button, in CP5.5 maybe this easier expression could work as well: Assign cpCmndGotoSlide with rdinfoCurrentSlide.
Should check, but for the moment on this system no 5.5 available

How do I add LaTeX or an image to a PDF in Preview?

I would like to be able to annotate a PDF with math formulas. I saw an option for adding latex, but I can't get it to work. I could create the image of the formula that I want to add, but I can't seem to add an image to the PDF either.
Any suggestions will be appreciated.
Thanks,
Nicole

With Acrobat Professional (perhaps also with Standard)
From the tools menu
The TouchUp Object tool can perform copy & paste.

Geany Latex plug-in PDF preview doesn't work [NEVER MIND]

See the end of this post
Does anyone know how to get the Geany Latex plug-in PDF preview to work? For a while it was creating a shell script in the current directory that didn't have execute permissions for the user, now I can't tell if it's even doing that (the script was designed to erase itself). I tried with both sakura and xterm as the terminal, as well as I tried with evince (my preferred viewer) and xpdfview. Also, the DVI preview doesn't work.
--EDIT--
Wait! The script magically returned. It's called geany_run_script.sh and it looks like this:
#!/bin/sh
evince "/home/skottish/latex/1/John.pdf"
echo "
(program exited with code: $?)"
rm $0
It works if it's chmoded then executed, but that's totally pointless for the user to do.
--FINAL EDIT--
I've spent far too much time on text editors. The reality is that Scite is a perfect fit for me. It's fast as hell, supports every language I want, it's fully scriptable, has auto completion... it does everything I need it to do and far more. I'm sure a very simply Lau script will implement this and anything else that I need.
--FINAL EDIT, THE NEXT GENERATION--
In Scite, you just need to put something like this in one of the options files. This works for Evince. The menu item 'pdfPreview' will be in the 'Tools' menu for .tex files:
# PDF preview through Evince
command.name.1.$(file.patterns.tex)=pdfPreview
command.1.$(file.patterns.tex)=pdflatex $(FileName) && evince $(FileName).pdf
command.subsystem.1.$(file.patterns.tex)=0
Making the second command line into this will clear up the .aux, .log. and .pdf files also:
command.1.$(file.patterns.tex)=pdflatex $(FileName) && evince $(FileName).pdf && rm $(FileName).aux $(FileName).log $(FileName).pdf
Now onto spell check...............................
--FINAL EDIT, BACK TO THE BEGINNING AGAIN--
It turns out with Geany all that needs to be done is to add this to Build-->Set Arguments-->PDF creation. Then when you go Build--> Latex -> PDF, it would launch evince:
pdflatex --file-line-error-style "%f" && evince "%e".pdf
Of course adding this to the end would clean up the build files also:
&& rm "%e".pdf "%e".log "%e".aux
Last edited by skottish (2008-09-05 21:18:29)

I don't have the Windows 7 machine in front of me to test this on, but the XP machine behaves the same if I open up Reader or Acrobat before I click Preview PDF in LiveCycle.

CJK characters in xml element name

Hi People,
I have a question as it looks like I am doing something wrong, but I do not know what.
I am trying to use CJK characters in the element name of an xml document and the element names are encoded/parsed using the default encoding and not the encoding specified at the xml document.
This is the specific code
     ByteArrayOutputStream baos = new ByteArrayOutputStream();
     Document document = DocumentBuilderFactory.newInstance().newDocumentBuilder().newDocument();
     document.appendChild(document.createElement("\ub3c4\uba54\uc778"));
     TransformerFactory tFactory = TransformerFactory.newInstance();
        Transformer transformer = tFactory.newTransformer();
        transformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");
        transformer.transform(new DOMSource(document), new StreamResult(baos));
        System.out.println(new String(baos.toByteArray(), "UTF-8"));
        System.out.println(new String(baos.toByteArray()));(you have to run this on a system that does not have UTF-8 as the default locale :-)
The result of this is
<?xml version="1.0" encoding="UTF-8" standalone="no"?><???/>
<?xml version="1.0" encoding="UTF-8" standalone="no"?><도메인/>
So the encoding of the element name is not UTF-8 but the default encoding.
Just in case someone ask
$ java -version
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13-120)
Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_05-b13-52, mixed mode)
Thanks,
Lucas

Hi Alpha.23,
well I'm not sure, and maybe I'm totally wrong, but here is what I think about your problem.
As there is no error while running the code, there should be no XML problem (so the characters you are using are XML compatible for tag names).
I think the problem is the ability of any computer to display such chars. The questionmark often indicates that there is a char which cannot display correctly. This depends partitially on the font your are using.
If I try to display the chars with simple System.out.println("\ub3c4\uba54\uc778"); I get those question marks too. So I guess the console of my IDE (eclipse) can't display these Korean symbols. But I haven't installed the specific language-support for any of the Asian languages (so I don't know what happend when they are installed, though I guess that doesn't solve the problem...).
So my tip is first to look for a way to print these char in general (on the console, into a file, maybe try to create a word document because a unicode font -i.e. Arial Unicode- is able to print these - try ALT+47700 or ALT+46020).
Best Wishes
esprimo

Keynote 6.0 seems to break LaTeXiT: workarounds?

I use LaTeXiT to place equations in my Keynote presentations. In Keynote 6.0, I can still copy equations from LaTeXiT into Keynote, but I can't copy equations from Keynote back into LaTeXiT. Does anyone know of a workaround?

I am working quite a lot now with Keynote 6 and LaTeXiT, and find two sorts of work flow convenient:
(1) Put a brand new formula on your slide
(1.1) Format formula with LaTeXiT
(1.2) Drag and drop pdf formula from uper window of LaTeXiT onto some suitable directory in finder.
        This creates a pdf file containing the formatted formula
(1.3) Drag and drop the pdf file with formula from finder to Keynote slide
(1.4) Re-position formula with Format --> Arrange ---> Position in Keynote if neccessary
(2) Modify and existing formula on your slide
(2.1) Now you should have a formula pdf file in some directory, as sketched in (1)
(2.2) Drag and drop formula file from finder directory to upper window of LaTeXiT.
(2.3) Modify and re-format formula with LaTeXiT
(2.4) Drag and drop the formula into finder directory
(2.5) Mark old formula on slide
(2.6) Use Format --> Image --> Replace in Keynote, select new formula in file selection menu
(2.7) In several cases, the new formula will not fit properly on the slide.
       Then press Format -> Arrange -> Original Size. This should display the picture properly, and you can
        re-size it according to your needs

Illustrator breaks preview when I used it with LaTex

I am having a bizarre problem using Illustrator CS3 on Leopard. Here is the sequence of events:
1. I create a diagram in Illustrator. I save a copy of that diagram as an eps file (or as a pdf).
2. I embed that eps (or pdf) diagram as a figure in a LaTex document and compile it. The code I use is:
\begin{figure}[htp]\centering\includegraphics[height=50mm]{figtiming.eps}\caption{Timing of the model.} \label{fig:timing}\end{figure}
3. All the sudden, every pdf file I open has fonts that are all wrong! It's like somehow this breaks preview's ability to properly decode the fonts of all pdf files.
When I restart the computer, everything is strangely back to normal.
Help!
Many thanks, Ryan

Hi Allen,
Is there any way to store the back up to Mac and restore after formating?

How do i write latex in numbers

How do I write math with latex in numbers?

Pages doesn't support LaTeX commands either. And if you're referring to the iOS version of Pages, it doesn't have much if anything in the way of an equation editor built in that I know of. There might be an equation editor for iOS that would create an equation as a graphic which you could then paste into Pages.
If you're asking about the Mac version of Pages, you can get MathType which will work with Pages. Or you can use something like LaTeX Equation Editor (which may be getting rather old now):
http://evolve.lse.ac.uk/software/EquationEditor/
which can export a PDF which you can then embed in Pages.
Regards.

The pdf font quality changes if another pdf file is open, for pdfs generated by Latex Beamer

Hi There,
I create pdf presentation files using Latex Beamer. I see a strange behavior when I open the file with Adobe reader to read it. If another pdf file is already open, the quality of the font is good but the shadow of the boxes disappears. If no other pdf file is open, the shadow box is good but the font has a low quality.
Does anyone know about this problem?
Thanks
Kaveh

Kaveh,
I am having a similar issue with PDFs i create from Photoshop and added links in Acrobat. The quality of the text was changing on me and I hadnt realized it was when I had more than one PDF open.
Please let em know if you come to any resolution on this.
Thanks,
Jamie

CJK-Latex

Similar Messages

Maybe you are looking for