Talk:GiFT: Difference between revisions
m →Front-ends: new section |
|||
| Line 10: | Line 10: | ||
:How is remote-side supposed to know which character encoding the other peer uses? That would require negotiation with each single peer and support for numerous character encodings. ISO-8859-1 covers only Latin-1. The above characters are just examples anyway. Arabic, Japanese, Cyrillic wouldn't work at all unless maybe all peers stick to the same encoding. That's why modern file-sharing networks use Unicode whereas olders didn't give a damn, only worked for ASCII or some other subsets. --[[User:217.87.68.60|217.87.68.60]] 12:30, 6 September 2007 (UTC) |
:How is remote-side supposed to know which character encoding the other peer uses? That would require negotiation with each single peer and support for numerous character encodings. ISO-8859-1 covers only Latin-1. The above characters are just examples anyway. Arabic, Japanese, Cyrillic wouldn't work at all unless maybe all peers stick to the same encoding. That's why modern file-sharing networks use Unicode whereas olders didn't give a damn, only worked for ASCII or some other subsets. --[[User:217.87.68.60|217.87.68.60]] 12:30, 6 September 2007 (UTC) |
||
== Front-ends == |
|||
Berlios have posted "Jazza"[http://developer.berlios.de/projects/jazza/] in Feb last year_> [[User:MonstaPro|MonstaPro]]:<sup>[[User_talk:MonstaPro|Talk]]:[[Special:Contributions/MonstaPro|Contrib.]]</sup> 13:43, 26 September 2007 (UTC) |
|||
Revision as of 13:43, 26 September 2007
Is giFT still maintained, or is it dead? There haven't been any new releases in a *long* time...
- See for yourself: http://sourceforge.net/projects/gift ¦ Reisio 22:53, 26 July 2006 (UTC)
?????
"giFT currently lacks unicode support included, so it is impossible to share files with characters such as "ø","ä", "å", "é", "è", "ó", "ö", "ù", "ü" in their names."
AFAIK, accented Latin characters such as "ø","ä", "å", "é", "è", "ó", "ö", etc., are already included in ISO-8859-1(read: 8-bit extended ASCII), and therefore have never required Unicode support to be displayed correctly. Unless you meant that GiFT was designed so badly that could handle only 100%-pure-ASCII filenames. KSM-2501ZX, IP address:= 200.143.28.19 16:31, 16 June 2007 (UTC)
- How is remote-side supposed to know which character encoding the other peer uses? That would require negotiation with each single peer and support for numerous character encodings. ISO-8859-1 covers only Latin-1. The above characters are just examples anyway. Arabic, Japanese, Cyrillic wouldn't work at all unless maybe all peers stick to the same encoding. That's why modern file-sharing networks use Unicode whereas olders didn't give a damn, only worked for ASCII or some other subsets. --217.87.68.60 12:30, 6 September 2007 (UTC)
Front-ends
Berlios have posted "Jazza"[1] in Feb last year_> MonstaPro:Talk:Contrib. 13:43, 26 September 2007 (UTC)