[sword-devel] Encoding question regarding modules
dhowens at pmbx.net
Sat Nov 29 07:38:45 MST 2008
Thanks for the quick response. I think the purpose of the content is to
help new module developers get acquainted with how to do that, so I will
eliminate a potential source of confusion and simplify it to just UTF-8.
Chris Little wrote:
> We only want to publish UTF-8 content, and I would probably tag even
> ASCII content as UTF-8 for the simplification of processing since many
> frontends would perform an unnecessary cp1252 to UTF-8 conversion.
> If the second paragraph (in context) says that we would accept
> submissions in cp1252, that should probably be changed. If it's just
> expressing an ability to handle cp1252 data for legacy content, it could
> be left alone.
> Daniel Owens wrote:
>> I am working on the wiki page for the module creation process, and I
>> seem to have stumbled on an internal inconsistency:
>> "Note that the SWORD Project requires all submitted texts to be Unicode
>> (UTF-8) encoded documents. We recommend that texts be marked up in OSIS
>> or TEI, but will still accept texts based on CCEL documents that are
>> marked up in ThML."
>> Later on:
>> "As mentioned above in the conf's Encoding directive, SWORD modules can
>> be encoded either in Windows Codepage 1252 (cp1252) (a superset of ISO
>> 8859-1) or in UTF-8. See Encoding for a complete explanation and
>> For the purpose of clearing it up, does CrossWire only except source
>> files encoded in UTF-8 or is cp1252 still acceptable?
>> sword-devel mailing list: sword-devel at crosswire.org
>> Instructions to unsubscribe/change your settings at above page
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
PMBX license 1502
More information about the sword-devel