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

Kim Haase commented on DERBY-4591:
----------------------------------

Thanks, Knut, for the reminder about the environment.

I think this may be hopeless -- the same thing happens both with the simple 
text editor I usually use (the one in CDE --- very old) and NetBeans. There 
seems to be no way to control what format the editor saves in. I don't think it 
looks at the header at all.

In both editors I used Compose-a-backtick to create what in the  editor looked 
like an a with a grave accent, but in my terminal with the LANG variable set to 
en_US.UTF-8, it turned into an A with a tilde in a Solaris terminal window and 
a Greek lowercase alpha in a Windows command prompt window (when I did a grep 
for another word in the line that contained it). And of course I still get the 
"Invalid byte 2 of 3-byte UTF-8 sequence" error.

> 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