mldonkey, a multi-networks file-sharing client - Patches: patch #3984, Make filename_conversions option...
You are not allowed to post comments on this tracker with your current authentication level.
patch #3984: Make filename_conversions option implementation safe
Submitter: | su_blanc <su_blanc> | ||
Submitted: | Thu 05 May 2005 09:47:24 AM UTC | ||
Category: | Bug fixes | Priority: | 9 - Immediate |
Status: | Done | Assigned to: | amorphous |
Open/Closed: | Closed |
Jump to the original submission
Mon 30 May 2005 09:03:41 PM UTC, comment #10: |
spiralvoice <spiralvoice> |
Mon 30 May 2005 01:15:46 AM UTC, comment #9: IMHO we have to rename it considering that the default value of filename_conversion was set to [(228, "ae");(246, "oe");(252, "ue");(223, "ss");(196, "Ae");(214, "Oe");(220, "Ue");] in the previous CVS. thus (see https://savannah.nongnu.org/bugs/?func=detailitem&item_id=9102#comment19) if somebody already built mlnet with the previous CVS, we force the user to have a default list that may not be as per his needs. I don't think the majority of users know and will use this option. |
su_blanc <su_blanc> |
Sun 29 May 2005 07:00:30 PM UTC, comment #8: Why should we rename it? It should continue to work just fine (if there wasn't an non-utf-8 char entered, and if that is the case the user needs to change that option anyway). |
Amorphous <amorphous> |
Sun 29 May 2005 06:44:52 AM UTC, comment #7: - rename filename_conversion in utf8_filename_conversion to avoid clash with the previous option
|
su_blanc <su_blanc> |
Fri 27 May 2005 02:18:35 PM UTC, comment #6: Yes, that is what i though of.
|
Amorphous <amorphous> |
Fri 27 May 2005 12:37:40 AM UTC, comment #5: I would like but I don't know exactly what you want to do with it...
|
su_blanc <su_blanc> |
Thu 26 May 2005 04:38:21 PM UTC, comment #4: The LGPL explicitly states, that instead the GPL may be applied.
|
Amorphous <amorphous> |
Wed 18 May 2005 09:57:09 AM UTC, comment #3: additional patch for Unicode character support.
|
su_blanc <su_blanc> |
Sat 07 May 2005 05:42:22 AM UTC, comment #2: I think the way to do is to create unichar interface.
|
su_blanc <su_blanc> |
Fri 06 May 2005 10:26:33 PM UTC, comment #1: wouldn't it be good to support any conversion for any utf-8 char to any utf-8 string (or isn't that possible because of multi-byte chars)? perhaps i want to convert some japanese char to something or i want to convert ue to ΓΌ or anything similar... |
Amorphous <amorphous> |
Thu 05 May 2005 09:47:24 AM UTC, original submission:
- make sure we use forbidden chars according to the OS
|
su_blanc <su_blanc> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2005-07-07 | spiralvoice | Status | None | Done | |
Open/Closed | Open | Closed | |||
2005-06-22 | spiralvoice | Assigned to | None | amorphous | |
2005-05-29 | su_blanc | Attached File | - | Added safe_utf8_filename_conversions_option.patch, #4660 | |
2005-05-18 | su_blanc | Attached File | - | Added charset_fix.patch, #4625 | |
2005-05-05 | su_blanc | Attached File | - | Added make_filename_conversions_safe.patch, #4568 |
Powered by Savane 3.13-758e.
Corresponding source code
Applied 2005/05/30, file #4625 and file #4660