Abdelrazak Younes wrote:
> So you would be OK if I change also all code that deals with format names?
The question is: Do non-ASCII format names make sense? I really don't know.
If the answer to that question is yes and it does not create problems
elsewhere, then it would be OK with me.
> In this case, I think the format should be an enum instead.
>
> enum FileFormat {
> jpg,
> lyx,
> etc
> };
Won't work. Users can add their own formats. We could of course create an
enum for know formats and a userdefined value, but that would make the code
more ugly.
>> So IMO you have two options:
>>
>> - convert all filenames to docstring, but don't change the existing
>> design
>
> That's my plan for now.
>
>> - Do the big thing and implement proper handling of filenames.
>
> I will be reasonable this time and do the conversion first ;-)
:-) That can't upset anybody.
Georg
