go-swagger route can't handle Chinese characters properly

[nlimpid]

Problem statement

go-swagger will ignore swagger:route section when there is Chinese character in it.

Swagger specification

code to generate swagger.json

package swagger

// swagger:route GET /online get room list 中
//
// Lists pets filtered by some parameters.
//
// This will show all available pets by default.
// You can get the pets that are out of stock
//
//     Responses:
//       default: test
//
func getOnline() {}

result

{
  "consumes": [
    "application/json"
  ],
  "produces": [
    "application/json"
  ],
  "schemes": [
    "http",
    "https"
  ],
  "swagger": "2.0",
  "info": {
    "title": "Ksweb API.",
    "version": "1.0.0"
  },
  "basePath": "/api",
  "paths": {},
  "definitions": {
...
// others

but if remove the '中' character in the go code, the swagger.json will have the router.

{
  "consumes": [
    "application/json"
  ],
  "produces": [
    "application/json"
  ],
  "schemes": [
    "http",
    "https"
  ],
  "swagger": "2.0",
  "info": {
    "title": "Ksweb API.",
    "version": "1.0.0"
  },
  "basePath": "/api",
  "paths": {
    "/online": {
      "get": {
        "description": "This will show all available pets by default.\nYou can get the pets that are out of stock",
        "tags": [
          "get",
          "room"
        ],
        "summary": "Lists pets filtered by some parameters.",
        "operationId": "list",
        "responses": {
          "default": {
            "$ref": "#/responses/test"
          }
        }
      }
    }
  },
  "definitions": {
...
// abbreviate details

Steps to reproduce

swagger generate spec -o ./swagger.json -m

generate the swagger.json, ignore the model definition here.

Environment

swagger version: 0.10.0
go version: go.1.8.3 darwin/amd64
OS: macOS 10.12.5

[nlimpid]

I am sorry that I am wrong. The problem remains and can be reproduction with which I mention, but the real problem is "operationId" can't be Chinese characters.

It's a problem but I think it is not important, so I choose to close this issue.