Re: how can I adapt documents for LARGE PRINT versions?
On 5/1/08, Joe(theWordy)Philbrook <[EMAIL PROTECTED]> wrote: > But since the maximum base size is only 12 pts, I gotta ask if I'm > missing some obvious technique to easily convert a document for a large > print edition without micro managing or losing all the relative font > sizes??? > I recently stumbled on these two links that may suit your purpose. The first one [1] links to the "type1cm" package which allows "Arbitrary size font selection in LaTeX" (not sure yet, but it seems to be limited to CM fonts), so that scalable (CM) fonts are used. The second one [2] shows a practical example on doing this (examples for 10.5pt and 13pt only, but should be a good start nonetheless). >From my other readings, the "type1cm" is highly recommended to obtain high-quality .pdf output, and suitable for high-resolution prints. Otherwise the resulting .pdf may simply look bad on different .pdf readers. Liviu [1] http://www.ctan.org/tex-archive/help/Catalogue/entries/type1cm.html [2] http://wiki.lyx.org/FAQ/ChangeFontUsingLatex
StarDict
Hi all, Can I use StarDict in LyX under Windows XP? -- Regards, Patrick
includepdf
Hello everyone, I am using the inludepdf package to include a couple of pdf files as an appendix... works fine so far, but the included pdf- files are printed on a new page each. so the caption of the appendix is on e.g. page 7 and the included pdf-file starts at page 8. I have tried to use the enlargethispage command and scaled the pdf to 50% but wasn´t successful. Can anyone help? Thanks very much Regards Mario
Re: how can I adapt documents for LARGE PRINT versions?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It would appear that on May 3, Helge Hafting did say: {# liberally snipped...} > koma-script is a standard part of texlive, which is a popular tex > distribution for some linux distributions. > > If you have debian, then "apt-get install texlive-latex-recommended" > is what you need to get koma-script. Then I suppose that I could work on a document with the lyx provided by whichever distro I'm using. And when I want a large print version I could at least modify a copy of it in my kubuntu environment... Thankyou for the package name. ;) > As for printing a document with different font sizes: > The normal way is to select a different font size. > If that is not possible, then you can redefine > the font sizes latex use ( \small, \big, \footnotesize, > and so on. There are a couple of handfuls of these, no more. > If you redefine these, then the whole document changes accordingly. OK so if I can find the instructions to redefine said font sizes along with a list of the font designations listing their default font sizes, I could redefine them all for a value of ($defaultvalue * 1.5) and then produce the large print output... ??? !!! ??? > This way is some work, but it is definitely less than changing *every* > paragraph in a big document. The amount of work is independent of > document size, no more work for a long book than for a 3-page report. So if this is perhaps something I do with "ERT" commands I could embed a comment with the appropriate ERT command form, with the values that produced the most agreeable large print output, in all my documents. Then when I'd want a large print version All I'd have to do would be to copy the content of the comment to an ERT box at the beginning of the document before producing the large print output, and then simply delete the ERT box when I want to revert to a more normal print size??? If so it would be worth a month of Sundays worth of work to refine the ERT command! Hmmnn, Is the redefining of the latex font size values independent of the koma-script package? Cause if so this solution would likely provide for an ERT command that would work in all my linux environments... Which makes the idea priceless... Thankyou! Is there perhaps, an easy to follow how-to somewhere for this technique of redefining the font sizes? {drool drool} # ##_if_you'd_prefer_an_clearsigned_".asc"_text_file_of_this_## ##message_as_an_mime_encoded_attachment,just_ask_me_while__## ##it's_STILL_IN_my_outbox_folder_._._._=+=+=+=+=+=+=+=+;-)_## #gpg sig for: Joe (theWordy) Philbrook DSA key ID 0x6C2163DE# # You can find my public gpg key at http://pgpkeys.mit.edu/ # # -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIHgTIRZ/61mwhY94RAiMPAJ9y8I3gkgtEw8XP6R5VHI0bt8Nu3wCgrG1f bAsV/v4XVwsbmI7udQRc3QI= =Wq9w -END PGP SIGNATURE- -- | ? ? | |-=- -=- I'm NOT clueless... | But I just don't know. |^ Joe (theWordy) Philbrook | --- J(tWdy)P | <[EMAIL PROTECTED]> | ? ?
Off-topic: Translators wanted for opensource
G'day everyone Please allow me to tell you about our translation project. I'm hoping that some of you might be able to help us with translations or ideas. One of the types of programs that I'm sure will be useful to translate, is text editing programs. Since you guys already work on or translate a text editing program, would you mind telling me what you think one should look for in a text editing program from the point of view of translating it? What things do you think one needs to keep in mind when selecting a single text editing program for a translation project with volunteers? We call our project the Decathlon because we want to encourage people who feel passionate about their language to translate up to ten or more opensource programs into their languages in 2008. This year, we limit our selection of translated programs to applications aimed at end-users, and preferably programs that run on multiple platforms. All translations are done in our web-based translations system, Pootle. The value of Pootle is that a team of translators can work together on a single file. Pootle also has quality checking features, to ensure that translations don't break the software they are used in. Pootle requires the Gettext PO format, but we can convert certain other formats to and from PO. You can read more about the Decathlon project at http://translate.sourceforge.net/wiki/decathlon/mainpage. Or take a look at the online translation system: http://pootle.locamotion.org/ Or join the low-volume newsletter mailing list: https://lists.sourceforge.net/lists/listinfo/translate-decathlon Or contact the project leader, Samuel Murray, at [EMAIL PROTECTED] I look forward to hearing from you. Sincerely Samuel Murray Decathlon project leader
bibtex +LyX
hi, I am trying to use biblographic references using APA style (i.e., (author, year) for citations) I have the default working fine (IEEE or similar style...ie., [1], [1,2], etc.) Anyone willing to tell me how to set the bib citation to APA style in LyX ? Thanks in advance. Cheers, Ed Sykes
disabling page numbering until TOC ?
Hi everybody. I'm fairly new to lyx and tex stuff in general and I'm currently desperately trying to disable page numbers on all pages until TOC (including TOC). I can't use \thispagestyle{empty} on every page, because TOC is more than one page long and it seems to affect only last page of TOC. At http://wiki.lyx.org/FAQ/Unsorted#toc4 I found a possible solution but \pagestyle{empty} does not do anything anywhere in document for reasons which are unknown to me so far. I tried to modify roman numbering before TOC which I have found here: http://wiki.lyx.org/Examples/RomanPageNumbering but I was unsuccessful as well. lyx v1.5.1 This is TeX, Version 3.141592 (Web2C 7.5.6) everything installed from as it is in ubuntu repository :-) Any suggestions ?
Re: includepdf
Mario Braun wrote: > I am using the inludepdf package to include a couple of pdf files as an > appendix... You mean pdfpages? > works fine so far, but the included pdf- files are printed on a new page > each. so the caption of the appendix is on e.g. page 7 and the included > pdf-file starts at page 8. > > I have tried to use the enlargethispage command and scaled the pdf to 50% > but wasn´t successful. I think this isn't the way pdfpages is supposed to be used. If you want a caption, include a single pdf page via the graphics dialog. Jürgen