User forums > Nightly builds

The 25 october 2006 build is out.

<< < (8/11) > >>

rjmyst3:
In the meantime, perhaps when the wxWidgets encoding conversion routines return an empty string it could be caught and a warning could be shown to the user, such that the file is not lost.

stahta01:
I think the right solution is most likely to set the default at the time of installation by asking the user. But, to me this is NOT a major issue. It is also NOT an issue to be decided at this time. I think it is an issue that should be decided before the final release candidate is done. And, it might make sense for each OS to have a different default if the user does NOT pick something.  I have already voted for an UTF-8 default, but I have no idea of the down side of that default. I have set my CB to UTF-8 today to see what happens. But, I really don't use it enough to be a good test case of whether it is a valid choice.

Tim S

killerbot:
I think for compilers etc, we will see, by trying it out, like you do.
I do think we should avoid to have a BOM in there.

mandrav:

--- Quote ---And, it might make sense for each OS to have a different default if the user does NOT pick something.
--- End quote ---

You should be aware that C::B is not setting any defaults. Instead, the current system encoding is set as default. If your operating system is badly configured, then C::B's "default" encoding will be badly configured too.

MortenMacFly:
Revision 3148 will take care of this issue in an appropriate way.
<sarcasm>Thanks for the patch, ramguru.</sarcasm> :lol: :lol:

--- Quote from: rjmyst3 on October 26, 2006, 10:11:29 pm ---In the meantime, perhaps when the wxWidgets encoding conversion routines return an empty string it could be caught and a warning could be shown to the user, such that the file is not lost.

--- End quote ---
rjmyst3: Thanks for being productive.
With regards, Morten.

Navigation

[0] Message Index

[#] Next page

[*] Previous page