similar to: Filenames with Windows-1250 chars

Dear colleagues, I would like to have GAM regression lines (package gam) thicker than the default setting does. Is there any way to change the width of regression line when plotting gam.objects from the package GAM with more than one predictor? Changing lwd parameter in plot function controls all line components, including points making them thicker as well, which is not what I would like to

Hi folks! I upgraded a red hat linux fileserver (kernel version 2.4.18-14) from samba 2.x to samba 3.02. After the upgrade, the special chars in windows filenames (German Umlaute) were no more visible to clients but either substituted with a little black rectangle or completely suppressed - depending on the client operating system (W2000/W98). Within the archived list I found a hint that the

Dear List, I am writing a paper in Hungarian, that I Sweave and than pdfLaTeX. Everything is fine, except for two accented letters in the graphs that behave strange, though on the screen and in eps exports they look perfect. The problem is that I need pdf graphs, since I would like to have a PDF after LaTeX-ing. For the example below I downloaded the following two font sets: 1. Latin Modern

Hello all, I have a problem with the display of filenames > 80 chars when served by Samba-3.0.0 to Windows clients. System: GNU/Linux debian 3.0.1 upgraded to testing/unstable on ALPHA processor (XP-1000), Kernel: custom 2.4.22 + acl support (kernel pkg could only be compiled by downgrading binutils to 2.12.90 & using gcc-3.0) Samba: Samba-3.0.0.final.deb (testing/unstable) smb.conf:

Hi experts, Two hopefully quick questions: 1. If I create files with names with special characters, such as ><*:"?\|, on the linux server box, I can see these filenames display just fine. But windows client the special characters do not show up properly. Is there a option to set? I tried: In [global] section: character set = ISO8859-2 client code page = 852

There's a bug reported in Debian about the tty being screwed up by wierd filenames, see http://bugs.debian.org/bug=242300 On the one hand, find will also do this. On the other hand, ls will replace such chars with a question mark. Upon inspection, it appears to be fairly simple to also do this in rsync (in the rwrite() function). Here's a patch. Opinions? Perhaps don't do it

--- Miroslav Lichvar <lichvarm@phoenix.inf.upol.cz> wrote: > At first I had to remove parentheses in configure.in, line 208, > autoconf or m4 don't like it there. OK, it works for me but I will fix it as the parens are not necessary. > I tried tagging using metaflac with some iso-8859-2 chars, but these > chars were replaced by '#' chars, something wrong is here.

--- Miroslav Lichvar <lichvarm@phoenix.inf.upol.cz> wrote: > On Fri, Nov 08, 2002 at 12:39:52PM -0800, Josh Coalson wrote: > > --- Miroslav Lichvar <lichvarm@phoenix.inf.upol.cz> wrote: > > > I have few notes: > > > > > > It seems there is changed API in CVS again. So, what about adding > > > function like > > > unsigned

> -- Miroslav Lichvar <lichvarm@phoenix.inf.upol.cz> wrote: > On Tue, Dec 17, 2002 at 01:01:08PM -0800, Josh Coalson wrote: > > --- Miroslav Lichvar <lichvarm@phoenix.inf.upol.cz> wrote: > > > Ok, what about enabling the 3dnow function in libFLAC by default? > > > I think time has shown the function is bugfree... :) > > > > Yeah, I just

Hi all This question came up several times in this list in the last couple of weeks, but nobody seems to have found a solution... so I post this again, hoping that anybody out there has the answer. I compiled Samba 3.0.0beta3 on Solaris 9 with the following options: --with-winbind --with-acl-support --with-included-popt --with-pam Starting the daemon or doing testparm gives me always: Error

--- Josh Coalson <xflac@yahoo.com> wrote: > > -- Miroslav Lichvar <lichvarm@phoenix.inf.upol.cz> wrote: > > On Tue, Dec 17, 2002 at 01:01:08PM -0800, Josh Coalson wrote: > > > --- Miroslav Lichvar <lichvarm@phoenix.inf.upol.cz> wrote: > > > > Ok, what about enabling the 3dnow function in libFLAC by > default? > > > > I think time

Hey guys How do you upcase the special characters (????)? I use latin-1 and not utf-8. How did you solve this problem? (nice ruby way or ugly hack doesnt matter) Daniel -- Posted via http://www.ruby-forum.com/.

Hi, I came across the problem with rsync-2.5.5 on Cygwin/Win2K while rsyncing with filenames which have 'strange' (non latin-1) characters in filenames. The problem is that filenames on Windows system are coded (in our case) in codepage 852, while server (Linux system) has filename coding according to ISO-8859-2. This two are not fully compatible, causing rsync to simply skip copying some

The report on R_help about problems loading package irr (in a UTF-8 locale, it seemed) prompted me to look a little deeper. There are quite a few packages with Latin-1 chars in their .R files, and a couple in UTF-8. Apart from non-ASCII chars in comments, this is a problem as the code concerned cannot be represented in some locales R runs in (for example Japanese on Windows). It happens

R-devel (pre-2.5.0) now has enough facilities to allow packages with non-ASCII character strings to work reasonably well in locales where the fonts use support the characters used. For example, names in Western European languages can be used on both Latin-1 (and hence Windows 1252) and UTF-8 systems. It should also be possible to make use of non-ASCII object names. To enable this, two

Since R 2.5.0 it has been possible to declare the encodings of character strings (at the level of individual elements of a character vector). As a reminder, here is the announcement in NEWS o R now attempts to keep track of character strings which are known to be in Latin-1 or UTF-8 and print or plot them appropriately in other locales. This is primarily intended to make it possible

This issue might interest you, because it solves filenaming incompatibilities between Windows (in different languages), and Samba. In fact, the problem is in Windows, and not in Samba (surprising, isn't it ? ;-) By the way, thanks to you for your documentation, which helped me a lot resolving this issue. Regards, Christopher >>> Original message: I've found many messages

Hye, we use a samba 2.2.3a which works fine most time. now i found that one client has some strange problems. when the user copies files to the smb-share some of them will be created with very strange filenames. For example let's say the original file is named: my_nicetestfile.txt then on the server the file will be created as my_nic~1.txt and also a file will be created called

On Tue, Dec 17, 2002 at 01:01:08PM -0800, Josh Coalson wrote: > --- Miroslav Lichvar <lichvarm@phoenix.inf.upol.cz> wrote: > > Ok, what about enabling the 3dnow function in libFLAC by default? > > I think time has shown the function is bugfree... :) > > Yeah, I just haven't done it because I don't remember hearing > feedback from others about using it (or

We have been able to get windows workstations to validate against win2k for authentication, but in looking at local shares on the linux box (via samba), do the users need to be localized to a group in /etc/group to allow access to files on the linux system that samba is running on. Here is the smb.conf we have come up with (along with modifications): [global] workgroup = donbest