| ||
> I guess it's not as simple as that. Two file names are stored for each file, a At first, we could start by just displaying the hex bytes and not allow renaming. BTW, on my PC I already have stuff like this, courtesy of MS: {8851E12C-0EF9-11D4-A788-009027ABA5D0} I know that these are treated as some special system f*ders, but that's not the point. If something similar is displayed by ZTree it would just look like a standard way of handling special dir/file names, not a shortcoming.
| ||
|
Messages in this Thread
- [Discuss] Unicode and other undisplayable chars (834) - Slobodan Vujnovic - Jul 04,2002 at 20:00 [Discuss]
- [Discuss] Unicode and other undisplayable char (737) - Ben Kent - Jul 04,2002 at 22:11
- Opportunity for ZTree? (763) - Slobodan Vujnovic - Jul 04,2002 at 23:08
- Opportunity for ZTree? (749) - Olivier Avenel - Jul 05,2002 at 00:10
- MS does something similar (763) - Slobodan Vujnovic - Jul 05,2002 at 01:16
- MS does something similar (740) - Olivier Avenel - Jul 05,2002 at 02:08
- MS does something similar (763) - Slobodan Vujnovic - Jul 05,2002 at 01:16
- Opportunity for ZTree? (749) - Olivier Avenel - Jul 05,2002 at 00:10
- Opportunity for ZTree? (763) - Slobodan Vujnovic - Jul 04,2002 at 23:08
- [Discuss] Unicode and other undisplayable char (749) - Juergen Hestermann - Jul 07,2002 at 00:31
- [Discuss] Unicode and other undisplayable char (733) - Greg Black - Jul 07,2002 at 12:00
- [Discuss] Unicode and other undisplayable char (733) - Juergen Hestermann - Jul 07,2002 at 18:04
- [Discuss] Unicode and other undisplayable char (733) - Greg Black - Jul 07,2002 at 12:00
- [Discuss] Unicode and other undisplayable char (737) - Ben Kent - Jul 04,2002 at 22:11