Hi all,
Reading some mails on the GIMP mail list, I ran across the procedure
to install some more fonts for not only Gimp, but the system and
StarOffice to use also. Well, I installed the fonts, went to the
shell and issued the command xset fp+ <font directory> and then the
rehash command and all fonts are there! Ok, that went well, but each
time I restart the system, I have to do it all over again? Is there
a way to make it permanent and read the new fonts like it does the
ones the system installs or is that a no-no?
end of line
Tracer
Shell commands:
xset fp+ <new font directory>
xset fp rehash
--
---KMail 1.2--- SuSE Linux v7.2---
Registered Linux User #225206
/tracerb(a)sprintmail.com/ *Magic Page Products*
*Team Amiga* http://home.sprintmail.com/~tracerb
Hi:
I just bought this printer, thinking it would work right out of the box. I'm
running SUSE 9.3 with CUPS, and it does not seem to support this model.
Anybody got this printer to work? Any pointers would help.
Best regards.
--
Alfredo Cole-Tuckler
Sid Boyce wrote:
> http://www.mandrake.tips.4.free.fr/opensuse10.3.review.html
> Mentions of "for the uninitiated" sounds about right. To sidestep any
> problems with the DVD, I've installed from Factory. Looks like the DVD
> should have been delayed until it was compared with Factory for
> stability.
> I think the reviewer attempted to be fair (he points to the URL to
> show where he is coming from). Perhaps some pertinent pointers for 11.0.
> Regards
> Sid.
http://www.mandrake.tips.4.free.fr/opensuse10.3.review.html should be
MUST READING for management at Novell and at openSuSE.org. It is
eminently fair and for the most part, accurate. I think any
inaccuracies could be attributable to unfamiliarity rather than bias.
If this reviewer hadn't been what I would call a 'Power-user', and had
instead been someone converting from Windows, not only would they
probably not have had a successful install, but would have an article
that Microsoft would probably have printed in full page ads throughout
the world. As it is, it should wake up Senior Management in SuSE.
regards
Richard
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
The proxy works for firefox but not for konq in 11.0 kde 4. I've tested the
proxy via yast and it works fine. Also, other browsers recognise it. Bug?
I'm using squid on a 10.3 server with 11.0 and KDE4
Thanks.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
I performed a fresh install of opensuse 10.3 and proceeded to go to
http://software.opensuse.org/search for the codecs
I selected and executed Codec-Audio-Video.ymp. During the installation
process I received a dialogbox with the following major message and assoc
options.
No valid solution found with just resolvables of best architecture
and
speex cannot be installed due to missing dependencies.
--
View this message in context: http://www.nabble.com/Problem-with-codec-installer-in-opensuse-tp14946930p1…
Sent from the openSUSE community mailing list archive at Nabble.com.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
Anybody tried it?, is it actually being used on the Opensuse project?.
Looks interesting.... Maybe it can replace workflow apps on
Domino/Notes...
Webpage: http://swamp.sourceforge.net/
SWAMP - The Workflow Platform
SWAMP is a workflow processing platform. Workflows are processes with
many people involved in many working steps. In a real world scenario
these workflows are highly dynamic, but still many systems try to
hardcode the business logic. That leads to raising efforts to adapt
the system.
Here is where SWAMP steps in: The workflow is designed in a XML based
meta language in one file which is read by SWAMP. Workflows can be
built from different workflow 'patterns' like simple actions,
decisions, selections, loops, but also custom code and external events
if required.
SWAMP builds a HTML GUI from the workflow definition file that guides
different users through the whole process, sends notifications if
required, assembles overview pages over all running processes and much
more. A SOAP interface can be used to integrate external systems into
the workflow.
These are SWAMPs main Features:
* Support of many different workflow patterns
* Flexibility in workflow design: A workflow can be specified in a
single XML file
* Workflow evolution: Workflows can be developed while in
operation (versioning)
* Ease of use: clear and straightforward XML based workflow
definition language, no coding skills needed
* Workflows can attach data and files
* Automatic web-GUI generation for handling individual tasks and
administrating workflows
* Running on Linux + Windows with OS-independant tools: Java, Tomcat, MySQL
* MySQL + LDAP authentication possible
* User and Role management, workflows/tasks can be restricted
* Mail notification system included
* Unlimited amount of different workflow-types on one server
* Scheduler to control time-critical workflow paths
* SOAP interface allows interaction with external systems
* Openness: Custom code allows unlimited functionality, event- and
data gateways
* Customizeable overview lists with filters
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
I had that little symbol "electrical plug" on the bottom of the screen,
indicating whether I was connected or not. It diappeared, probably my
doing, how do I get it back to get connected?
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
What do I have to do after I download, say thuntherbird, I find two
incons on the desktop with a lot of files in each, what is the next step
to get the program going.?
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
It's been several years since I saw this problem and I forget how to fix it.
The --help command is confusing to me. The problem: the computer is
approximately 8 months slow--it thinks it's last March. Interestingly, the
time is correct. If I need to be in SU mode, please advise.
TIA--
doug
Blessed are the peacemakers ... for they shall be shot at from both sides.
--A.M. Greeley
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
Hi,
a couple of months ago I wrote about the large file sizes that I was
getting when I converted a word .doc file to OO odt file, with the
intention of later converting it to pdf. They were in the size of
megabites. This is a bit of an ongoing saga for me, as this time I made
up the newsletter for the organization using Open Office from the start,
and then attempted to convert the odt file to pdf in linux. I ended up
having to go back to windows in order to get the file sizes to a
manageable size, the linux files were too large.
Here is a rundown of what I did.
1. I made up the newsletter using Open Office. The final file size was
198kb. Not too bad, I thought that it was going to work out as I
expected the file to be smaller yet when I converted that to a pdf file.
2. I converted the odt file to pdf. The resultant pdf file was
758.8kb. I am shooting for around 200kb, but will send a file up to
300kb. Any larger and it takes too long for the dialup users to
download it.
3. I tried to play around with the pdf conversion process by reducing
picture quality, and/or reducing the quality of the total pdf document.
I produced two other pdf's this way, and believe it or not when I
reduced the quality of the document to 50% it actually produced a larger
file on my first attempt. That file was 789kb. The second attempt (30%
quality) was 750 kb.
I decided to save the newsletter odt file in doc format to see how large
it would be, before I quit linux for Windows. It came out to 270kb. I
was hoping to open it in word in winxp, and then convert it to pdf. But
the formatting was so messed up it was easier to start over fresh in
Word. But then, they tell me it isn't going to work right when try to
save it as a doc file in open office. The new word file displaying the
same information (plus an extra couple of pages of text that I forgot on
the copy that I produced in OO) as the newsletter produced in odt came
out to 220kb.
4. Those linux pdf files were too large to use, so I went back to WinXP
and made up the file in Word (220kb). I then converted that to pdf, and
got a file size of 270kb. That is useable, and I don't know of any way
to make it smaller in Windows unless I start removing some pictures from
the newsletter.
As it stands now, I think that I will have to stick with windows for
this task unless someone has a brainstorm and thinks of a way to make
these linux pdf files smaller.
Mark
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
