Feature #275

a global setting for the encoding of all fields

Added by J C almost 4 years ago. Updated 7 months ago.

Status:Closed Start:06/18/2009
Priority:Normal Due date:
Assigned to:- % Done:

0%
Category:- Spent time: -
Target version:V0.15
Resolution:duplicate

Description

Currently, individual fields can be marked as unicode-enabled, but they default to non-unicode, which I think would seem to discourage people from using unicode.

Instead, I think there should be a global setting that indicates the encoding of the file as a whole (default: UTF-8), and SOLID should flag any characters that violate that. Thus, SOLID would only be happy with, say, pure ANSI or pure UTF-8, and not with any mixed encoding.

Once that's in place, MAYBE individual fields could be marked as exceptions to the general encoding scheme. But I'm not sure it's good for SOLID to be happy about mixed encoding.

History

#1
Updated by Beth Bryson almost 3 years ago

This would be helpful.

#2
Updated by J C almost 3 years ago

Related issue (of lesser importance):
"need a column indicating encoding, in top-left pane" http://projects.palaso.org/issues/show/431

#3
Updated by Cambell Prince over 2 years ago

I see mixed encoding all the time. e.g. IPA in unicode, vernacular has a hacked font and the project isn't yet able to go unicode.

#4
Updated by Cambell Prince over 2 years ago

Cambell Prince wrote:

I see mixed encoding all the time. e.g. IPA in unicode, vernacular has a hacked font and the project isn't yet able to go unicode.

I prefer #431

#5
Updated by Beth Bryson over 2 years ago

Cambell Prince wrote:

I see mixed encoding all the time. e.g. IPA in unicode, vernacular has a hacked font and the project isn't yet able to go unicode.

Certainly mixed encodings do happen reasonably often.

The way I would re-write this issue would be to ask for a global setting per language. Thus, I can say that all the Manobo data is in Unicode, and then when I say a field is in Manobo, SOLID expects to find Unicode there.

If I have a file with Manobo in Unicode and Manobo in a legacy encoding, then in FLEx I will make two writing systems, so I can import one through an encoding converter. So in my world, if a single language had two encodings, that would be two different writing systems (and my suggestion would still work). I don't know if that is possible in the SOLID world though.

But in my experience, having a single language in both legacy and Unicode is much more rare than having different WSs in different encodings.

#6
Updated by Cambell Prince over 2 years ago

  • Target version set to V0.14

#7
Updated by Cambell Prince over 2 years ago

  • Target version changed from V0.14 to V0.15

This is the same as the setup wizard.

#8
Updated by J C 7 months ago

  • Status changed from New to Closed
  • Resolution set to duplicate

It looks like 431 is the preferred option, so I'll close this as a duplicate. (Also, Solid does now know how to flag some encoding issues.)

Also available in: Atom PDF