LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-01-2017, 03:11 AM   #16
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 187

Rep: Reputation: 86

Quote:
Originally Posted by cgorac View Post
So as far as I can see now it's not possible to write Cyrillic out of the box? No T2A encoding file, and probably no Cyrillic fonts included.
Please provide a (minimalitic)tex-testfile, one goal is to provide tetex-compatibility.
 
Old 10-01-2017, 04:39 AM   #17
cgorac
Member
 
Registered: Oct 2009
Posts: 87

Rep: Reputation: 31
Quote:
Originally Posted by franzen View Post
Please provide a (minimalitic)tex-testfile, one goal is to provide tetex-compatibility.
Sure, here it goes:

Code:
\documentclass{report}

\usepackage[T2A]{fontenc}
\usepackage[utf8]{inputenc}

\begin{document}

Здраво, свијете!

\end{document}
Unrelated to this, it seems also that moreverb.sty is missing, and tetex had it.
 
1 members found this post helpful.
Old 10-01-2017, 04:45 AM   #18
cgorac
Member
 
Registered: Oct 2009
Posts: 87

Rep: Reputation: 31
And this one, with Central European Latin characters is problematic too:

Code:
\documentclass{report}

\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}

\begin{document}

Ćao, svijete!

\end{document}
Namely, processing with LaTeX would go fine, but then dvi2pdf is producing following error: "dvips: ! Couldn't find header file: cm-super-t1.enc".
 
Old 10-01-2017, 01:14 PM   #19
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 187

Rep: Reputation: 86
Quote:
Originally Posted by staus View Post
I always try out various distros by seeing if Lyx will correctly display its help files under tools. The old tetex software worked flawlessly in Slackware, but not after texlive was installed. That was the reason I did not use Robby Workmans texlive about a year ago. It is probably only missing one or two sty files.
I assume lyx asks for article.cls, which is provided by the texlive package.
I had to do
rm -rf ~/.tex*
and as root:
mktexlsr
fmtutil-sys --all

It's also possible that it just works if you login again, as you might have still tetex environment variables set.
 
1 members found this post helpful.
Old 10-02-2017, 12:00 AM   #20
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,221

Rep: Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709
Quote:
Originally Posted by staus View Post
I always try out various distros by seeing if Lyx will correctly display its help files under tools. The old tetex software worked flawlessly in Slackware, but not after texlive was installed. That was the reason I did not use Robby Workmans texlive about a year ago. It is probably only missing one or two sty files.
The difference is that franzen actually knows what he's doing with texlive packaging - I was just pressing keys and hoping for a best ;-) (I'm only *half* kidding when I say that, for what it's worth)
 
Old 10-02-2017, 12:09 AM   #21
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,221

Rep: Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709
Re the suggestion to add the other three texlive-* packages to Slackware, I'm pretty much certain that's a non-starter. The whole reason that texlive wasn't in Slackware long ago was its size. I made a (somewhat) noble effort to shoehorn it in several times but was never successful at finding a happy compromise between size and functionality. Thankfully, franzen came along and fixed that, so here we are.

Ideally, what happens from here is that the texlive-extra, texlive-fonts, and texlive-docs builds continue to be maintained on SBo by franzen, and it only seems reasonable that they will be "in sync" with the texlive version in Slackware. Of course, this won't really take effect until the -current tree is released as a stable version.

In the meantime, two suggestions for franzen:
1. The texlive version on SBo hopefully won't pass the one in Slackware - in essence, I'd prefer not doing any updates on SBo that don't first occur in Slackware.
1a. Maybe sync the stuff on SBo with the stuff in Slackware, i.e. configure flags and such, but not variable names (e.g. PRGNAM->PKGNAM)
2. As much as possible, let's make sure the texlive-* stuff on SBo will work as-is on -current.
2a. If (2) isn't possible, let me know and we'll see about pushing necessary changes to ponce's -current repo.

I hate to even imply that more work is required of you, as you've done *plenty* in just making this usable, so please let me know if I can help with any of this.
 
7 members found this post helpful.
Old 10-02-2017, 06:30 AM   #22
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 187

Rep: Reputation: 86
Quote:
Originally Posted by rworkman View Post
Ideally, what happens from here is that the texlive-extra, texlive-fonts, and texlive-docs builds continue to be maintained on SBo by franzen, and it only seems reasonable that they will be "in sync" with the texlive version in Slackware. Of course, this won't really take effect until the -current tree is released as a stable version.

In the meantime, two suggestions for franzen:
1. The texlive version on SBo hopefully won't pass the one in Slackware - in essence, I'd prefer not doing any updates on SBo that don't first occur in Slackware.
1a. Maybe sync the stuff on SBo with the stuff in Slackware, i.e. configure flags and such, but not variable names (e.g. PRGNAM->PKGNAM)
2. As much as possible, let's make sure the texlive-* stuff on SBo will work as-is on -current.
2a. If (2) isn't possible, let me know and we'll see about pushing necessary changes to ponce's -current repo.
I'll do so :-)
 
5 members found this post helpful.
Old 10-02-2017, 09:08 AM   #23
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 4,632

Rep: Reputation: 1530Reputation: 1530Reputation: 1530Reputation: 1530Reputation: 1530Reputation: 1530Reputation: 1530Reputation: 1530Reputation: 1530Reputation: 1530Reputation: 1530
My thanks also to all involved in bringing this to Slackware. It is very timely for me, as I will likely practise my rusty LyX skills in the near future.
Quote:
I always try out various distros by seeing if Lyx will correctly display its help files under tools.
I have just installed LyX-2.2.3 on -current using the SlackBuild from ponce's repo. As I have Alien Bob's LibreOffice, to get spell checking and the thesaurus in LyX, I pointed the settings for Thesaurus dictionaries and Hunspell dictionaries under Tools->Preferences->Paths to the LibreOffice location at /usr/lib(64)/libreoffice/share/extensions/dict-XX/ (where XX is country code) and then set the Spellchecker engine to Hunspell under Tools->Preferences->Language Settings->Spellchecker.

[edit] A better way is to create a directory /usr/share/myspell (default location for hunspell) and put the dictionary and thesaurus files in there. [/edit]

Last edited by allend; 10-03-2017 at 09:24 AM.
 
Old 10-11-2017, 04:57 AM   #24
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 187

Rep: Reputation: 86
Quote:
Originally Posted by cgorac View Post
Sure, here it goes:

Code:
\documentclass{report}

\usepackage[T2A]{fontenc}
\usepackage[utf8]{inputenc}

\begin{document}

Здраво, свијете!

\end{document}
This happens because the updmap.cfg shipped by tlnet lists a lot of fontmaps( e.g. here the problem is cm-super)
which may not be present. I'll send a fix to Pat.

Meanwhile, comment the cm-super maps in /usr/share/texmf-dist/web2c/updmap.cfg and then as root-user
/usr/bin/updmap-sys --nohash --syncwithtrees

Be aware, that these changes will be overwritten on a reinstall of texlive.


Quote:
Unrelated to this, it seems also that moreverb.sty is missing, and tetex had it.
I added moreverb.sty to the (next)base package.

Johannes
 
Old 10-11-2017, 07:14 AM   #25
cgorac
Member
 
Registered: Oct 2009
Posts: 87

Rep: Reputation: 31
Quote:
Originally Posted by franzen View Post
Meanwhile, comment the cm-super maps in /usr/share/texmf-dist/web2c/updmap.cfg and then as root-user
/usr/bin/updmap-sys --nohash --syncwithtrees
Thanks, tried that but same problems I mentioned above, with both T1 and T2A font encoding, are still there. Here is output of running LaTeX over example where T2A is used:

Code:
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017 on Slackware) (preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./foo.tex
LaTeX2e <2017-04-15>
Babel <3.10> and hyphenation patterns for 84 language(s) loaded.
(/usr/share/texmf-dist/tex/latex/base/report.cls
Document Class: report 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texmf-dist/tex/latex/base/fontenc.sty

! Package fontenc Error: Encoding file `t2aenc.def' not found.
(fontenc)                You might have misspelt the name of the encoding.

See the fontenc package documentation for explanation.
Type  H <return>  for immediate help.
 ...                                              
                                                  
l.104 \ProcessOptions*
                      
?

Last edited by cgorac; 10-11-2017 at 07:15 AM.
 
Old 10-11-2017, 07:28 AM   #26
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 187

Rep: Reputation: 86
Quote:
Originally Posted by cgorac View Post
Thanks, tried that but same problems I mentioned above, with both T1 and T2A font encoding, are still there. Here is output of running LaTeX over example where T2A is used:
I forgot that you don't have the cyrillic-packages. Here it worked, should work for everybody with the next texlive package in -current hopefully.
 
Old 10-11-2017, 02:36 PM   #27
navigium
Member
 
Registered: Aug 2014
Location: Switzerland
Distribution: Slackware, Debian, FreeBSD
Posts: 89

Rep: Reputation: 48
That's awesome news! My two regular annoyances with Slackware were the lack of Python 3 and Texlive. The next release is going to be my favorite Linux in the last 20 years or so...
 
Old 10-12-2017, 05:16 AM   #28
gauchao
Member
 
Registered: Dec 2009
Location: Veneto
Distribution: SLACKWARE 14.2 64bit
Posts: 225

Rep: Reputation: 50
I wish to thank you both, rworkman and franzen, for all the good work with TexLive. It's a huge suite and you have done all the hard work to bring it to Slackware. Thank you very much!
 
4 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Texlive in Current? byzkarl Slackware 2 01-17-2016 09:49 AM
update texlive (tlmgr): no texlive.tlpdb tramni1980 Slackware 3 03-30-2011 07:30 AM
Slackware64 -current made public! bsdunix Slackware 289 06-19-2009 12:15 AM
LXer: Slackware64 -current made public! LXer Syndicated Linux News 3 05-21-2009 12:02 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:12 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration