Hi,

I Am on Windows 7 64-bits and I would like to contribute to #7506 and #7508 but I have this error too when cloning the repo. Creating a virtual machine is a solution, but it would be better if Windows contributors could clone the repo.

Regards,

Patrick
Le 16/07/2014 15:53, DP Tor-Contact a écrit :
I am using a Windows Vista 32-bit machine. (yeah pretty awful but I'm at work) I have tried to cole the repo again, it showed the same mistake. I also saw that there are some more filenames with colons. Is there a contributer-base of Windows users? If not we should leave it in that way, I can switch to a virtual machine with Debian. And the documentation should be updated regarding to that.

Regards

spriver

Am 2014-07-16 14:53, schrieb u:
intrigeri:
u wrote (16 Jul 2014 11:28:59 GMT) :
as seen on tails-l10n, there is a folder in the wiki which contains a
colon. This results in problems on Windows systems, where contributors
might want to translate.. but can't checkout this folder.

Can one build the website (with ikiwiki) on Windows?

(I'm fine with adding constraints on filenames if it *really* allows
people to do their translation work on Windows. If it's removing one
stumbling block only to then unhide the next one, I'm not sure it's
worth it.)

you are absolutely right.

Let's ask the person first. Eventually, we should then also update the
documentation accordingly.

cheers
u.
_______________________________________________
Tails-dev mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
[email protected].
_______________________________________________
Tails-dev mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to [email protected].

--
Patrick ZAJDA
Skype: gansta93

_______________________________________________
Tails-dev mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
[email protected].

Reply via email to