[ 
https://issues.apache.org/jira/browse/DERBY-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860183#action_12860183
 ] 

Knut Anders Hatlen commented on DERBY-4591:
-------------------------------------------

Hi Kim. I don't see this error if I add 'à' and save the file with UTF-8 
encoding. I do see the same error if I save the file with ISO-8859-1 encoding. 
My text editor (Emacs) automatically picks the correct file encoding based on 
the header in the XML file, which says:

<?xml version="1.0" encoding="utf-8"?>

If you cannot get your editor to save as UTF-8, you may change the header to 
say ISO-8859-1 instead, and it should work.

As to using escape sequences, the character showed up just fine in the PDF 
version when I tried. What's the locale you're using? According to 
http://db.apache.org/derby/manuals/dita.html#Setting+up+your+environment, you 
need to set the LANG variable to en_US.UTF-8.

> Documentation needed for global case-insensitive setting (DERBY-1748)
> ---------------------------------------------------------------------
>
>                 Key: DERBY-4591
>                 URL: https://issues.apache.org/jira/browse/DERBY-4591
>             Project: Derby
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 10.6.0.0
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>             Fix For: 10.6.0.0
>
>         Attachments: DERBY-4591-2.diff, DERBY-4591.diff, DERBY-4591.diff, 
> DERBY-4591.stat, DERBY-4591.zip, DERBY-4591.zip, rrefattribcollation.html
>
>
> The new feature implemented by DERBY-1748 needs to be documented. It appears 
> that the following topics will need to be changed, at least:
> Reference Manual: collation=collation attribute
> Developer's Guide: "Creating a database with territory-based collation", 
> "Character-based collation in Derby". 
> It's pretty hard to tell from all the discussion under DERBY-1748 exactly 
> what has changed and what the new feature does, so a functional spec for that 
> issue that describes the new feature clearly would be very helpful.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to