headers
Rainer Backes | 1 Sep 12:41
Picon

Umlauts and the filesystem

Hi,

I'm using SnipSnap 1.0b3-uttoxeter on my site www.falkenauge.info. The system is running SuSE 10.1,
SnipSnap is running standalone with apache as proxy. Storage for Snips is the filesystem.

Now my problem: I'm trying to backup the filesystem to another machine (acutally a NetWare server) with
rsync. Everything works fine, except for Snips with an umlaut or an 'ß' in the title. On the place of the
umlaut or the 'ß' a '?' appears in the linux filename. The rsync daemon on the other side cannot create
directories with a '?' in the name, because '?' is not allowed in filenames.

Is there a way to work around that ?

Thanks a lot 

Rainer Backes
Permalink | Reply | 0 comments |
headers
John Daues | 18 Sep 22:50
Favicon

update document

I now have 3 documents on a wiki page, like so:

[add file]
doc1.odt
doc2.odt
doc3.odt

I have an updated version of doc1.odt. I fear if I add the new doc1.odt, 
I'll get this:

[add file]
doc1.odt
doc2.odt
doc3.odt
doc1.odt

which is ugly.

What can I do?
Permalink | Reply | 1 comment |
headers
Ryan Barrett | 18 Sep 23:13
Picon

Re: update document

On Mon, 18 Sep 2006, John Daues wrote:

> I have an updated version of doc1.odt. I fear if I add the new doc1.odt,
> I'll get this:
>
> [add file]
> doc1.odt
> doc2.odt
> doc3.odt
> doc1.odt

nah, the new doc1.odt will overwrite the old one. just make sure you don't
mind losing the previous version!

-Ryan

--
http://snarfed.org/
Permalink | Reply | 0 comments |
headers
Ryan Barrett | 19 Sep 00:22
Picon

Re: update document

On Mon, 18 Sep 2006, John Daues wrote:

>>> nah, the new doc1.odt will overwrite the old one.
> Simply because it is the same filename?

yup.

>>> just make sure you don't mind losing the previous version!
> Not in this case, but what if I do ?

snipsnap does provide change history, but only for the text of snips. it's not
a general-purpose SCM.

if you want access to the previous version, you can either copy the text of
the file into a snip and edit it there going forward, put the file in CVS or
Subversion or another SCM, or just rename it something like doc1_v1.1.odt.

renaming it is, obviously, the least work. :P

-Ryan

--
http://snarfed.org/
Permalink | Reply | 0 comments |

Gmane