dmsmith555 at yahoo.com
Fri Jun 20 08:11:50 MST 2008
DM Smith wrote:
> On Jun 20, 2008, at 8:41 AM, Chris Little wrote:
>> The About field actually has to be RTF (\u####?-style). State your
>> to Troy if you want this to change, but it doesn't make much sense
>> to me
>> that we should want to include RTF markup and UTF-8 character encoding
>> (which isn't permitted in RTF) in the same field.
> I may have misunderstood, but I understood that Troy already spoke on
> this saying that SWORD allowed UTF-8 in RTF as an extension (I think
> this was also stated on the old Module Making page) and that the
> encoding of the conf had to match the encoding of the module.
> Certainly \u#####? is ASCII, so it is valid in all encodings.
> According to the Wiki, both are allowed in RTF but UTF-8 is preferred.
> Granted, I authored this, but I was reflecting what I thought I
> We already have a bunch of release modules with UTF-8 in the conf's
> About field. And more coming in beta.
Thread on the issue starts here (As you go through the thread, it gets
hijacked a couple of times, just keep clicking on "next in thread"):
Troy weighs in here with a statement that utf-8 is also allowed and also
notes that \u codes are not filtered correctly:
I listed which module confs had problems:
There are 188 UTF-8 modules.
Regarding \u RTF Codes, there are only 2 released modules with \u codes,
both of the Chinese.
Without surveying them again (see prior posting, listed above, now
stale) there are a bunch with cp1252. These should be fixed.
There are a bunch that have UTF-8 in their About field. (I don't
remember how many from my earlier survey. I didn't list the number,
because it was deemed as proper.)
At this point, any fix to the RTFHTML filter will be 1.5.12 (hopefully
not later). So any beta module with \u RTF codes should be marked as
More information about the sword-devel