We have i18n on the roadmap, but to be real with you we first have to address a couple of other urgent topics we need to cover before crossing that bridge 🙂

I get that entirely haha. Its not a big deal to implement, I was just wondering if I was making things more complicated without reason. As for the field name customisation, I checked my identity schema and it is configured as 'Email', but the login flow still returns a node with the identifier field: Identity schema:

"properties": {
        "email": {
          "type": "string",
          "format": "email",
          "title": "Email",
          "minLength": 3,
          "<http://ory.sh/kratos|ory.sh/kratos>": {
            "credentials": {
              "password": {
                "identifier": true
              }
            },
            "verification": {
              "via": "email"
            },
            "recovery": {
              "via": "email"
            }
          }
        },

The flow identifier node:

{
                "type": "input",
                "group": "default",
                "attributes": {
                    "name": "identifier",
                    "type": "text",
                    "value": "",
                    "required": true,
                    "disabled": false,
                    "node_type": "input"
                },
                "messages": [],
                "meta": {
                    "label": {
                        "id": 1070004,
                        "text": "ID",
                        "type": "info"
                    }
                }
            },

Ok nice 🙂