mike-jumper commented on issue #340: GUACAMOLE-660: Add Urdu Language Support URL: https://github.com/apache/guacamole-client/pull/340#issuecomment-454102003 Also, just ran the translation checking script added via #356 against the Urdu translation: ``` The following strings are either NOT defined for the original language or are expected to be inherited from the original language and should be removed: APP.NAME APP.VERSION ``` The `APP.NAME` and `APP.VERSION` strings should be removed from the translation, as they should always be inherited from the English strings. It may also be worth looking through the following, which the script reports might be untranslated as they are exact copies of the English strings (though I'm sure several are false positives): ``` The following strings are identical to the original language and MIGHT be untranslated: APP.FORMAT_DATE_TIME_PRECISE APP.TEXT_HISTORY_DURATION CLIENT.NAME_KEY_ALT CLIENT.NAME_KEY_CTRL CLIENT.NAME_KEY_ESC CLIENT.NAME_KEY_TAB CLIENT.TEXT_FILE_TRANSFER_PROGRESS DATA_SOURCE_DEFAULT.NAME FORM.FIELD_PLACEHOLDER_DATE FORM.FIELD_PLACEHOLDER_TIME MANAGE_CONNECTION.INFO_CONNECTION_DURATION_UNKNOWN MANAGE_USER_GROUP.FIELD_HEADER_USER_GROUP_NAME PROTOCOL_RDP.FIELD_OPTION_RESIZE_METHOD_DISPLAY_UPDATE PROTOCOL_RDP.FIELD_OPTION_SECURITY_NLA PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_DE_DE_QWERTZ PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_EN_GB_QWERTY PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_EN_US_QWERTY PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_ES_ES_QWERTY PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_FAILSAFE PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_FR_CH_QWERTZ PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_FR_FR_AZERTY PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_IT_IT_QWERTY PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_JA_JP_QWERTY PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_PT_BR_QWERTY PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_SV_SE_QWERTY PROTOCOL_RDP.FIELD_OPTION_SERVER_LAYOUT_TR_TR_QWERTY PROTOCOL_SSH.FIELD_OPTION_TERMINAL_TYPE_ANSI PROTOCOL_SSH.FIELD_OPTION_TERMINAL_TYPE_LINUX PROTOCOL_SSH.FIELD_OPTION_TERMINAL_TYPE_VT100 PROTOCOL_SSH.FIELD_OPTION_TERMINAL_TYPE_VT220 PROTOCOL_SSH.FIELD_OPTION_TERMINAL_TYPE_XTERM PROTOCOL_SSH.FIELD_OPTION_TERMINAL_TYPE_XTERM_256COLOR PROTOCOL_TELNET.FIELD_OPTION_TERMINAL_TYPE_ANSI PROTOCOL_TELNET.FIELD_OPTION_TERMINAL_TYPE_LINUX PROTOCOL_TELNET.FIELD_OPTION_TERMINAL_TYPE_VT100 PROTOCOL_TELNET.FIELD_OPTION_TERMINAL_TYPE_VT220 PROTOCOL_TELNET.FIELD_OPTION_TERMINAL_TYPE_XTERM PROTOCOL_TELNET.FIELD_OPTION_TERMINAL_TYPE_XTERM_256COLOR PROTOCOL_VNC.FIELD_OPTION_CLIPBOARD_ENCODING_CP1252 PROTOCOL_VNC.FIELD_OPTION_CLIPBOARD_ENCODING_ISO8859_1 PROTOCOL_VNC.FIELD_OPTION_CLIPBOARD_ENCODING_UTF_16 PROTOCOL_VNC.FIELD_OPTION_CLIPBOARD_ENCODING_UTF_8 SETTINGS_CONNECTION_HISTORY.FILENAME_HISTORY_CSV SETTINGS_CONNECTION_HISTORY.INFO_CONNECTION_DURATION_UNKNOWN ```
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
