misc/167977: mount_smbfs results are differ when utf-8 or UTF-8 local encoding's name is used

[Alexey]

>Number:         167977
>Category:       misc
>Synopsis:       mount_smbfs results are differ when utf-8 or UTF-8 local encoding's name is used
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 16 19:40:01 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator:     Alexey
>Release:        9.0-RELEASE
>Organization:
>Environment:
FreeBSD ldserver 9.0-STABLE FreeBSD 9.0-STABLE #5: Tue May  8 11:37:38 GMT-6 2012     root at ldserver:/usr/obj/workdata/usr/src/sys/ldserver  amd64

>Description:
When .nsmbrc contains

[default]
charsets=UTF-8:cp866

remote (windows 2000) filenames with "№" character are displayed ok
( "123№123" ), but when 

[default]
charsets=utf-8:cp866

(note lo-case) filenames are garbaged ( same name as above wiil be "123?"). 

Thereis no SMBFS nor NETSMB options in kernel config
options LIBICONV is.

"№" is 3-byte in UTF-8. XLAT16_ACCEPT_3BYTE_CHR isn't used at build time.

ldserver# smbutil -v lc
SMB connections:
VC: \\SSS\USER
(root:wheel) 711
    state:    Session active
    flags:    0x0428 <private|encpwd>
    usecount: 1
    dialect:  6 (NT LM 0.12, Windows for Workgroups 3.1a, NT LANMAN 1.0)
    smode:    3
    caps:     0xf3fd <SMB_CAP_RAW_MODE|SMB_CAP_UNICODE|SMB_CAP_LARGE_FILES|SMB_CAP_NT_SMBS|SMB_CAP_NT_FIND>
    maxmux:   50
    maxvcs:   1
    Share:    D$(root:wheel) 711
        flags:    0x0004 <>
        usecount: 1
>How-To-Repeat:
mount remote smb share, look at files with "&#8470;" in name
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: