Re: Hyphenation mess :-(
Am Montag, 6. Dezember 2004 18:12 schrieb Jean-Marc Lasgouttes: > There are a number of regexps for that, but in this case, it is the > opening parenthesis that triggers, I guess. > > I would do as follows: > > if I find a line with opening parenthesis so that what follows does > not form an existing file name and _if_ the line is exactly 80 chars > long (check the value, maybe), then try to merge with the next line. At least in tetex the line width can be configured. From /etc/texmf.cnf: % It's probably inadvisable to change these. At any rate, we must have: % 45 < error_line < 255; % 30 < half_error_line < error_line - 15; % 60 <= max_print_line; % These apply to Metafont and MetaPost as well. error_line = 79 half_error_line = 50 max_print_line = 79 It would be nice if the parsing could work without the line length information. Or it could be guessed: If the n (maybe n = 3) longest lines all have the same width, then this is the line width. There is also an option --recorder in tetex, which records all opened files in a file with extensiom .fls. But I don't know if all tex variants support this option. Georg
Re: Hyphenation mess :-(
Jean-Marc Lasgouttes wrote: > Angus> More importantly, tell me how I should recognize > Angus> .../preamble.tex is part of the file name. Ie, what > Angus> characteristic indicates that it is a file name? Is it the > Angus> blank line that follows or do I need to recognize the > Angus> characteristics of the .../preamble.tex string? > > There are a number of regexps for that, but in this case, it is the > opening parenthesis that triggers, I guess. > > I would do as follows: > > if I find a line with opening parenthesis so that what follows does > not form an existing file name and _if_ the line is exactly 80 chars > long (check the value, maybe), then try to merge with the next line. > > I also did a patch that I never applied which does the opposite > (handle several file name son the same line). I guess the two should > be merged. > http://marc.theaimsgroup.com/?l=lyx-devel&m=108232356511531&w=2 Ouch :-( How horrible. Using regexes to parse a file reminds me of reLyX and the pain I suffered in there. You know far, far more about these log files than me, but it seems that a file name is followed either by a space or by an empty line. That, together with your ideas above should result in a fairly robust test. MikTeX can handle file names with spaces in them, can't it? Maybe we need a log file containing such a file name too? -- Angus
Re: Hyphenation mess :-(
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Can you tell me where I should look in the LyX source to find Angus> the code that parses the log file for these dependencies. LaTeX::deplog in LaTeX.C Angus> More importantly, tell me how I should recognize Angus> .../preamble.tex is part of the file name. Ie, what Angus> characteristic indicates that it is a file name? Is it the Angus> blank line that follows or do I need to recognize the Angus> characteristics of the .../preamble.tex string? There are a number of regexps for that, but in this case, it is the opening parenthesis that triggers, I guess. I would do as follows: if I find a line with opening parenthesis so that what follows does not form an existing file name and _if_ the line is exactly 80 chars long (check the value, maybe), then try to merge with the next line. I also did a patch that I never applied which does the opposite (handle several file name son the same line). I guess the two should be merged. http://marc.theaimsgroup.com/?l=lyx-devel&m=108232356511531&w=2 JMarc
Re: Hyphenation mess :-(
Angus Leeming wrote: > Can you tell me where I should look in the LyX source to find the code > that parses the log file for these dependencies. I believe it is in src/LaTeX.C, in LaTeX::scanLogFile(). Another place that suffers from linebreaks is the extraction of error messages. > More importantly, tell me how I should recognize .../preamble.tex is part > of the file name. Ie, what characteristic indicates that it is a file > name? Is it the blank line that follows or do I need to recognize the > characteristics of the .../preamble.tex string? I don't know. Georg
Re: Hyphenation mess :-(
Jean-Marc Lasgouttes wrote: >> "Angus" == Angus Leeming <[EMAIL PROTECTED]> >> writes: > >>> Clever. Actually, I think we should do something like that when >>> parsing .log files, but I am not sure how. > > Angus> Can you give an example? > > This bug, for example: > http://bugzilla.lyx.org/show_bug.cgi?id=1027 > > JMarc Ok, LyX wants to parse the log file to see which files it should monitor for changes. An example of the log file data might be: ... Special comment 'contentCmt' (/afs/md.kth.se/md/ho me/damek/chr/thesis/doc//preamble.tex Setting paper size -- Can you tell me where I should look in the LyX source to find the code that parses the log file for these dependencies. More importantly, tell me how I should recognize .../preamble.tex is part of the file name. Ie, what characteristic indicates that it is a file name? Is it the blank line that follows or do I need to recognize the characteristics of the .../preamble.tex string? -- Angus
Re: Hyphenation mess :-(
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: >> Clever. Actually, I think we should do something like that when >> parsing .log files, but I am not sure how. Angus> Can you give an example? This bug, for example: http://bugzilla.lyx.org/show_bug.cgi?id=1027 JMarc
Re: Hyphenation mess :-(
Jean-Marc Lasgouttes wrote: >> "Angus" == Angus Leeming <[EMAIL PROTECTED]> >> writes: > > Angus> No, but that's why we use a loop in the sed script. The list of > Angus> languages always ends with 'loaded.', so get the next line if > Angus> the pattern space doesn't, remove the embedded new line and go > Angus> to the 'loop' label. Having finished looping, either because > Angus> you've found 'loaded.' or because you've reached the end of the > Angus> log file, then print out what you've got, but only if you found > Angus> 'loaded.'. > > Clever. Actually, I think we should do something like that when > parsing .log files, but I am not sure how. Can you give an example? -- Angus
Re: Hyphenation mess :-(
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes: Martin> Works as such :-) Martin> see attached. Martin> What next? Feel free to apply it. I asked about it on fr.comp.text.tex and it appears that there is no way to get this list from TeX... JMarc
Re: Hyphenation mess :-(
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> No, but that's why we use a loop in the sed script. The list of Angus> languages always ends with 'loaded.', so get the next line if Angus> the pattern space doesn't, remove the embedded new line and go Angus> to the 'loop' label. Having finished looping, either because Angus> you've found 'loaded.' or because you've reached the end of the Angus> log file, then print out what you've got, but only if you found Angus> 'loaded.'. Clever. Actually, I think we should do something like that when parsing .log files, but I am not sure how. JMarc
Re: Hyphenation mess :-(
On Thu, Dec 02, 2004 at 11:16:54AM +0100, Lars Gullik Bjønnes wrote: > Martin Vermeer <[EMAIL PROTECTED]> writes: > > | Just found out that in order to get proper hypenation for Finnish out of > | teTeX, you have to turn it on through the texconfig utility! > > > | Believe it or not, by default you only have hyphenation for american, > | french and german... > > > | THIS IS A PROBLEM. > > It has been like that forever. Well, I did not know that either. Otoh, I only write German and English (that ancient version of 'American'...) so there was not much reason to notice... Andre'
Re: Hyphenation mess :-(
On Fri, 2004-12-03 at 12:35, Jean-Marc Lasgouttes wrote: > > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes: > > Martin> Done! > > Martin> Works as such :-) > > Martin> see attached. > > Martin> What next? > > Either you commit it right now or you wait a bit until I have time to > find out how to do this at latex level. I think it is less error prone > than parsing log files (are we sure the list of languages is always on > one line?) No it isn't... but it is when this script is finished with it: that's what N s/\n// does in sed. Actually I read that Thomas Esser will enable all languages by default in future releases. So this problem will go away. Perhaps checking this in is a good enough stopgap for a legacy problem, unless you insist on expending energy to get a perfect solution :-) > JMarc - Martin signature.asc Description: This is a digitally signed message part
Re: Hyphenation mess :-(
Jean-Marc Lasgouttes wrote:
>> "Martin" == Martin Vermeer
>> <[EMAIL PROTECTED]> writes:
>
> Martin> Done!
>
> Martin> Works as such :-)
>
> Martin> see attached.
>
> Martin> What next?
>
> Either you commit it right now or you wait a bit until I have time to
> find out how to do this at latex level. I think it is less error prone
> than parsing log files (are we sure the list of languages is always on
> one line?)
No, but that's why we use a loop in the sed script. The list of languages
always ends with 'loaded.', so get the next line if the pattern space
doesn't, remove the embedded new line and go to the 'loop' label. Having
finished looping, either because you've found 'loaded.' or because you've
reached the end of the log file, then print out what you've got, but only
if you found 'loaded.'.
LANGUAGES=`sed -n '/hyphenation patterns/{
:loop
/loaded\.$/!{
$!{
N
s/\n//
tloop
}
}
/loaded\.$/p
}' chklatex.log`
--
Angus
Re: Hyphenation mess :-(
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes: Martin> Done! Martin> Works as such :-) Martin> see attached. Martin> What next? Either you commit it right now or you wait a bit until I have time to find out how to do this at latex level. I think it is less error prone than parsing log files (are we sure the list of languages is always on one line?) JMarc
Re: Hyphenation mess :-(
Martin Vermeer <[EMAIL PROTECTED]> writes: | On Thu, 2004-12-02 at 12:16, Lars Gullik Bjønnes wrote: > | ... > >> I have known this for years. > | What other things are you keeping secret from me? Only stuff that I have read in teTeX documentation. :-) (and by reading LaTeX log files: "Hypenation pattern for language xx loaded") -- Lgb
Re: Hyphenation mess :-(
On Thu, 2004-12-02 at 12:16, Lars Gullik BjÃnnes wrote: ... > I have known this for years. What other things are you keeping secret from me? - Martin signature.asc Description: This is a digitally signed message part
Re: Hyphenation mess :-(
On Thu, 2004-12-02 at 17:57, Angus Leeming wrote:
> Jean-Marc Lasgouttes wrote:
> > Martin> And then how to build on this?
> >
> > I do not have much time to look at it now, but the idea is that you
> > should use sed to keep only the languages, and then do something like
> >
> > echo "s/@chk_languages@/${languages}/g" >>chkconfig.sed
> >
> > Then if you add the text @chk_languages@ in some text in
> > LaTeXConfig.lyx.in, it will be replaced by the list of available
> > languages.
>
> # Grab the list of languages avaliable to LaTeX
> # by parsing the LaTeX log file, chklatex.log.
> LANGUAGES=`sed -n '/hyphenation patterns/{
> :loop
> /loaded\.$/!{
> $!{
> N
> s/\n//
> tloop
> }
> }
> /loaded\.$/p
> }' chklatex.log`
>
> # Add a line to chkconfig.sed so that the placeholder in
> # LaTeXConfig.lyx.in will be replaced by the list of available
> # languages.
> test "${LANGUAGES}" != "" && \
> echo "s/@chk_languages@/${LANGUAGES}/g" >> chkconfig.sed
Done!
Works as such :-)
see attached.
What next?
- Martin
Index: configure.m4
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/configure.m4,v
retrieving revision 1.85
diff -u -w -r1.85 configure.m4
--- configure.m4 15 Nov 2004 19:13:25 - 1.85
+++ configure.m4 2 Dec 2004 16:26:45 -
@@ -219,6 +219,19 @@
LATEX=
ac_result="not useable"
fi
+# Grab the list of languages avaliable to LaTeX by parsing the LaTeX log file, chklatex.log.
+LANGUAGES=`sed -n '/hyphenation patterns/{
+:loop
+/loaded\.$/!{
+$!{
+N
+s/\n//
+s/^.*for\ //
+tloop
+}
+}
+/loaded\.$/p
+}' chklatex.log`
rm -f chklatex.ltx chklatex.log])dnl
dnl
# Search LaTeX2e
@@ -523,6 +536,11 @@
echo "creating doc/LaTeXConfig.lyx"
echo "s/@chk_linuxdoc@/$chk_linuxdoc/g" >> chkconfig.sed
echo "s/@chk_docbook@/$chk_docbook/g" >> chkconfig.sed
+# Add a line to chkconfig.sed so that the placeholder in
+# LaTeXConfig.lyx.in will be replaced by the list of available
+# languages.
+test "${LANGUAGES}" != "" && \
+echo "s/@chk_languages@/${LANGUAGES}/g" >> chkconfig.sed
sed -f chkconfig.sed "${srcdir}"/doc/LaTeXConfig.lyx.in >doc/LaTeXConfig.lyx
echo "creating $outfile"
Index: doc/LaTeXConfig.lyx.in
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/doc/LaTeXConfig.lyx.in,v
retrieving revision 1.40
diff -u -w -r1.40 LaTeXConfig.lyx.in
--- doc/LaTeXConfig.lyx.in 4 Nov 2004 15:42:38 - 1.40
+++ doc/LaTeXConfig.lyx.in 2 Dec 2004 16:26:46 -
@@ -1,5 +1,7 @@
#LyX 1.4.0cvs created this file. For more info see http://www.lyx.org/
-\lyxformat 232
+\lyxformat 237
+\begin_document
+\begin_header
\textclass article
\language english
\inputencoding default
@@ -7,14 +9,12 @@
\graphics dvips
\paperfontsize 0
\spacing single
-\papersize Default
-\paperpackage a4
-\use_geometry 0
+\papersize default
+\paperpackage none
+\use_geometry false
\use_amsmath 0
-\use_natbib 0
-\use_numerical_citations 0
-\use_jurabib 0
-\use_bibtopic 0
+\cite_engine basic
+\use_bibtopic false
\paperorientation portrait
\secnumdepth 2
\tocdepth 3
@@ -25,9 +25,11 @@
\papercolumns 1
\papersides 1
\paperpagestyle plain
-\tracking_changes 0
+\tracking_changes false
\end_header
+\begin_body
+
\begin_layout Title
Inventory of your LaTeX configuration
@@ -2105,6 +2107,18 @@
if you want to use non-English quotes.
\end_layout
+\begin_deeper
+\begin_layout Subsubsection*
+
+Languages for which hyphenation patterns are loaded:
+\end_layout
+
+\begin_layout Standard
+
[EMAIL PROTECTED]@
+\end_layout
+
+\end_deeper
\begin_layout Subsection
color
@@ -2720,4 +2734,5 @@
is needed by LyX to be able to output url's corrently.
\end_layout
+\end_body
\end_document
signature.asc
Description: This is a digitally signed message part
Re: Hyphenation mess :-(
Jean-Marc Lasgouttes wrote:
> Martin> And then how to build on this?
>
> I do not have much time to look at it now, but the idea is that you
> should use sed to keep only the languages, and then do something like
>
> echo "s/@chk_languages@/${languages}/g" >>chkconfig.sed
>
> Then if you add the text @chk_languages@ in some text in
> LaTeXConfig.lyx.in, it will be replaced by the list of available
> languages.
# Grab the list of languages avaliable to LaTeX
# by parsing the LaTeX log file, chklatex.log.
LANGUAGES=`sed -n '/hyphenation patterns/{
:loop
/loaded\.$/!{
$!{
N
s/\n//
tloop
}
}
/loaded\.$/p
}' chklatex.log`
# Add a line to chkconfig.sed so that the placeholder in
# LaTeXConfig.lyx.in will be replaced by the list of available
# languages.
test "${LANGUAGES}" != "" && \
echo "s/@chk_languages@/${LANGUAGES}/g" >> chkconfig.sed
--
Angus
Re: Hyphenation mess :-(
Martin Vermeer wrote:
>> 'grep -A' is not POSIX. Tru64 Unix's version of grep, for example,
>> doesn't recognize it.
>>
>> sed -n '/hyphenation patterns/{
>> :loop
>> /loaded\.$/!{
>> $!{
>> N
>> s/\n//
>> tloop
>> }
>> }
>> p
>> }' chklatex.log > hyphenation.lst
>
> Yes, this works too :-)
Actually, being anal, I'd check that 'loaded.' was found before printing:
sed -n '/hyphenation patterns/{
:loop
/loaded\.$/!{
$!{
N
s/\n//
tloop
}
}
/loaded\.$/p
}' chklatex.log > hyphenation.lst
> And then how to build on this?
I have no idea.
--
Angus
Re: Hyphenation mess :-(
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> Yes, this works too :-)
Martin> And then how to build on this?
I do not have much time to look at it now, but the idea is that you
should use sed to keep only the languages, and then do something like
echo "s/@chk_languages@/${languages}/g" >>chkconfig.sed
Then if you add the text @chk_languages@ in some text in
LaTeXConfig.lyx.in, it will be replaced by the list of available
languages.
I would prefer to be able to grab the list of languages from inside
latex, but I did not succeed up to know to understand the babel code
that prints out this list.
Hope this helps.
JMarc
Re: Hyphenation mess :-(
On Thu, 2004-12-02 at 16:41, Angus Leeming wrote:
> Martin Vermeer wrote:
>
> > On Thu, 2004-12-02 at 15:06, Jean-Marc Lasgouttes wrote:
> >> > "Helge" == Helge Hafting
> >> > <[EMAIL PROTECTED]> writes:
> >>
> >> Helge> Is edit->reconfigure the right time though? A user may
> >> Helge> routinely use a couple of languages, and which one isn't known
> >> Helge> at reconfigure time.
> >>
> >> Edit>Reconfigure is the right time to tell the user what hyphenations
> >> are available in his babel installation. This is what we want in a
> >> first step.
> >>
> >> JMarc
> >
> > Would this be acceptable as a start?
>
> 'grep -A' is not POSIX. Tru64 Unix's version of grep, for example, doesn't
> recognize it.
>
> sed -n '/hyphenation patterns/{
> :loop
> /loaded\.$/!{
> $!{
> N
> s/\n//
> tloop
> }
> }
> p
> }' chklatex.log > hyphenation.lst
Yes, this works too :-)
And then how to build on this?
- Martin
signature.asc
Description: This is a digitally signed message part
Re: Hyphenation mess :-(
Martin Vermeer wrote:
> On Thu, 2004-12-02 at 15:06, Jean-Marc Lasgouttes wrote:
>> > "Helge" == Helge Hafting
>> > <[EMAIL PROTECTED]> writes:
>>
>> Helge> Is edit->reconfigure the right time though? A user may
>> Helge> routinely use a couple of languages, and which one isn't known
>> Helge> at reconfigure time.
>>
>> Edit>Reconfigure is the right time to tell the user what hyphenations
>> are available in his babel installation. This is what we want in a
>> first step.
>>
>> JMarc
>
> Would this be acceptable as a start?
'grep -A' is not POSIX. Tru64 Unix's version of grep, for example, doesn't
recognize it.
sed -n '/hyphenation patterns/{
:loop
/loaded\.$/!{
$!{
N
s/\n//
tloop
}
}
p
}' chklatex.log > hyphenation.lst
--
Angus
Re: Hyphenation mess :-(
On Thu, 2004-12-02 at 15:06, Jean-Marc Lasgouttes wrote: > > "Helge" == Helge Hafting <[EMAIL PROTECTED]> writes: > > Helge> Is edit->reconfigure the right time though? A user may > Helge> routinely use a couple of languages, and which one isn't known > Helge> at reconfigure time. > > Edit>Reconfigure is the right time to tell the user what hyphenations > are available in his babel installation. This is what we want in a > first step. > > JMarc Would this be acceptable as a start? - Martin Index: configure.m4 === RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/configure.m4,v retrieving revision 1.85 diff -u -r1.85 configure.m4 --- configure.m4 15 Nov 2004 19:13:25 - 1.85 +++ configure.m4 2 Dec 2004 13:57:32 - @@ -219,6 +219,7 @@ LATEX= ac_result="not useable" fi +grep -A 2 "hyphenation patterns" hyphenation.lst rm -f chklatex.ltx chklatex.log])dnl dnl # Search LaTeX2e signature.asc Description: This is a digitally signed message part
Re: Hyphenation mess :-(
> "Helge" == Helge Hafting <[EMAIL PROTECTED]> writes: Helge> Is edit->reconfigure the right time though? A user may Helge> routinely use a couple of languages, and which one isn't known Helge> at reconfigure time. Edit>Reconfigure is the right time to tell the user what hyphenations are available in his babel installation. This is what we want in a first step. JMarc
Re: Hyphenation mess :-(
John Levon wrote: It could even compile a short test file in the background extracting the phrase "hyphenation patterns for ... loaded" from the log. (or Reconfigure could do that.) If we can test the case, then we can Edit->Reconfigure warn the user indeed. Is edit->reconfigure the right time though? A user may routinely use a couple of languages, and which one isn't known at reconfigure time. Perhaps take a look at the log after each and every latex/pdflatex run and warn if no hyphenation was loaded for the document's language(s)? Helge Hafting
Re: Hyphenation mess :-(
On Thu, 2004-12-02 at 12:16, Lars Gullik BjÃnnes wrote: ... > | Attached a patch to the User Guide. > > Very good. (haven't looked at it) Somebody, please do. Or I'll just commit a little later. - Martin signature.asc Description: This is a digitally signed message part
Re: Hyphenation mess :-(
On Thu, 2004-12-02 at 12:39, Jean-Marc Lasgouttes wrote: ... > >> It could even compile a short test file in the background > >> extracting the phrase "hyphenation patterns for ... loaded" from > >> the log. (or Reconfigure could do that.) > > John> If we can test the case, then we can Edit->Reconfigure warn the > John> user indeed. > > The information about what languages have hyphenation can go into > LaTeXConfig.lyx. If LyX knew what hyphenation table is needed for each > language, we could even imagine to show in the interface which > languages have proper hyphenation. That's pretty much what I was (vaguely) thinking of. But how to get the hyphenation info other than by parsing a test log file? - Martin signature.asc Description: This is a digitally signed message part
Re: Hyphenation mess :-(
> "John" == John Levon <[EMAIL PROTECTED]> writes: John> On Thu, Dec 02, 2004 at 12:02:20PM +0200, Martin Vermeer wrote: >> What about adding a panel Preferences->Language >> Settings->Hyphenation shortly explaining this? John> Hmm, not a fan... >> It could even compile a short test file in the background >> extracting the phrase "hyphenation patterns for ... loaded" from >> the log. (or Reconfigure could do that.) John> If we can test the case, then we can Edit->Reconfigure warn the John> user indeed. The information about what languages have hyphenation can go into LaTeXConfig.lyx. If LyX knew what hyphenation table is needed for each language, we could even imagine to show in the interface which languages have proper hyphenation. JMarc
Re: Hyphenation mess :-(
Martin Vermeer <[EMAIL PROTECTED]> writes: | Just found out that in order to get proper hypenation for Finnish out of | teTeX, you have to turn it on through the texconfig utility! > | Believe it or not, by default you only have hyphenation for american, | french and german... > | THIS IS A PROBLEM. It has been like that forever. | I am reasonably well informed on (La)TeX and found this out only now. For some value of "reasonably" I guess :-) I have known this for years. | How are naive users ever going to figure this one out? (And what about | the assumption that things work right out of the box?) > | Attached a patch to the User Guide. Very good. (haven't looked at it) -- Lgb
Re: Hyphenation mess :-(
On Thu, Dec 02, 2004 at 12:02:20PM +0200, Martin Vermeer wrote: > What about adding a panel Preferences->Language Settings->Hyphenation > shortly explaining this? Hmm, not a fan... > It could even compile a short test file in the > background extracting the phrase "hyphenation patterns for ... loaded" > from the log. (or Reconfigure could do that.) If we can test the case, then we can Edit->Reconfigure warn the user indeed. john
Hyphenation mess :-(
Just found out that in order to get proper hypenation for Finnish out of teTeX, you have to turn it on through the texconfig utility! Believe it or not, by default you only have hyphenation for american, french and german... THIS IS A PROBLEM. I am reasonably well informed on (La)TeX and found this out only now. How are naive users ever going to figure this one out? (And what about the assumption that things work right out of the box?) Attached a patch to the User Guide. Undoubtedly automating this process inside LyX will be hard to impossible to do, if we don't want it to be teTeX specific. And running texconfig isn't that hard. But people have to be told about it. What about adding a panel Preferences->Language Settings->Hyphenation shortly explaining this? It could even compile a short test file in the background extracting the phrase "hyphenation patterns for ... loaded" from the log. (or Reconfigure could do that.) Ideas? -- Martin Vermeer <[EMAIL PROTECTED]> Index: UserGuide.lyx === RCS file: /usr/local/lyx/cvsroot/lyx-devel/lib/doc/UserGuide.lyx,v retrieving revision 1.6 diff -u -r1.6 UserGuide.lyx --- UserGuide.lyx 15 Aug 2004 17:08:19 - 1.6 +++ UserGuide.lyx 2 Dec 2004 09:42:37 - @@ -11238,18 +11238,53 @@ there is one in the printed version. \layout Standard -One last note about hyphenation --- LyX automatically breaks up words and +One more note about hyphenation --- LyX automatically breaks up words and inserts hyphens in English text. - (Actually, it's LaTeX that does this, and it will also hyphenate words - in + The words won't be hyphenated until you generate the final output. +\layout Standard + +Actually, it's LaTeX that does this, and it will also hyphenate words in + \emph on some \emph default - other languages.) The words won't be hyphenated until you generate the final - output. + other languages. + To know whether (PDF)LaTeX hyphenates for +\emph on +your +\emph default + language, look at any log file produced by a LaTeX run: it will say +\layout Quote + + +\family typewriter +Babel and hyphenation patterns for american, french, german, ngerman, + nohyphenation, loaded. +\layout Standard + +This tells you that, e.g., if you write in Finnish, you're out of luck. + Study (for the teTeX distribution of LaTeX) the utilities +\family typewriter +texconfig +\family default + and +\family typewriter +fmtutil +\family default + in order to switch hyphenation on for your language by ''uncommenting'' + the relevant line in a file typically named +\family typewriter +language.dat +\family default +. + Sorry for the inconvenience. \layout Standard -If, for some reason, LaTeX can't break a word correctly, you can set hyphenation +If, for whatever reason, LaTeX +\emph on +still +\emph default + can't break a word correctly (e.g., a compound word), you can set hyphenation points manually. This is done with the menu item \family sans signature.asc Description: This is a digitally signed message part
