The Weblate Manual 3.3error might look like: OperationalError: (1366, “Incorrect string value: ‘\xF0\xA8\xAB\xA1’ for column ‘target’ at row 1”) UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-3: ordinal messages: 1071: Specified key was too long; max key length is 767 bytes 1709: Index column size too large. The maximum column size is 767 bytes. There are two ways to workaround this limitation. You can configure there must be at least a column called source (which contains the source string) and a column called target (which contains the translation). Additionally there should be the column context (which contains0 码力 | 403 页 | 1.75 MB | 1 年前3
The Weblate Manual 3.2.1error might look like: • OperationalError: (1366, “Incorrect string value: ‘\xF0\xA8\xAB\xA1’ for column ‘target’ at row 1”) • UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-3: • 1071: Specified key was too long; max key length is 767 bytes • 1709: Index column size too large. The maximum column size is 767 bytes. There are two ways to workaround this limitation. You can configure there must be at least a column called source (which contains the source string) and a column called target (which contains the translation). Additionally there should be the column context (which contains0 码力 | 308 页 | 2.43 MB | 1 年前3
Weblate 3.2.1 Documentationerror might look like: OperationalError: (1366, “Incorrect string value: ‘\xF0\xA8\xAB\xA1’ for column ‘target’ at row 1”) UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-3: ordinal messages: 1071: Specified key was too long; max key length is 767 bytes 1709: Index column size too large. The maximum column size is 767 bytes. There are two ways to workaround this limitation. You can configure there must be at least a column called source (which contains the source string) and a column called target (which contains the translation). Additionally there should be the column context (which contains0 码力 | 398 页 | 1.65 MB | 1 年前3
The Weblate Manual 3.2.2error might look like: • OperationalError: (1366, “Incorrect string value: ‘\xF0\xA8\xAB\xA1’ for column ‘target’ at row 1”) • UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-3: • 1071: Specified key was too long; max key length is 767 bytes • 1709: Index column size too large. The maximum column size is 767 bytes. There are two ways to workaround this limitation. You can configure there must be at least a column called source (which contains the source string) and a column called target (which contains the translation). Additionally there should be the column context (which contains0 码力 | 310 页 | 2.43 MB | 1 年前3
The Weblate Manual 3.4error might look like this: OperationalError: (1366, “Incorrect string value: ‘\xF0\xA8\xAB\xA1’ for column ‘target’ at row 1”) UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-3: ordinal messages: 1071: Specified key was too long; max key length is 767 bytes 1709: Index column size too large. The maximum column size is 767 bytes. There are two ways to work around this limitation. You can configure there must be at least a column called source (which contains the source string) and a column called target (which contains the translation). Additionally there should be the column context (which contains0 码力 | 415 页 | 1.73 MB | 1 年前3
The Weblate Manual 3.3error might look like: • OperationalError: (1366, “Incorrect string value: ‘\xF0\xA8\xAB\xA1’ for column ‘target’ at row 1”) • UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-3: • 1071: Specified key was too long; max key length is 767 bytes • 1709: Index column size too large. The maximum column size is 767 bytes. There are two ways to workaround this limitation. You can configure there must be at least a column called source (which contains the source string) and a column called target (which contains the translation). Additionally there should be the column context (which contains0 码力 | 312 页 | 2.56 MB | 1 年前3
The Weblate Manual 3.2error might look like: • OperationalError: (1366, “Incorrect string value: ‘\xF0\xA8\xAB\xA1’ for column ‘target’ at row 1”) • UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-3: • 1071: Specified key was too long; max key length is 767 bytes • 1709: Index column size too large. The maximum column size is 767 bytes. There are two ways to workaround this limitation. You can configure there must be at least a column called source (which contains the source string) and a column called target (which contains the translation). Additionally there should be the column context (which contains0 码力 | 306 页 | 2.43 MB | 1 年前3
The Weblate Manual 3.2error might look like: OperationalError: (1366, “Incorrect string value: ‘\xF0\xA8\xAB\xA1’ for column ‘target’ at row 1”) UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-3: ordinal messages: 1071: Specified key was too long; max key length is 767 bytes 1709: Index column size too large. The maximum column size is 767 bytes. There are two ways to workaround this limitation. You can configure there must be at least a column called source (which contains the source string) and a column called target (which contains the translation). Additionally there should be the column context (which contains0 码力 | 398 页 | 1.65 MB | 1 年前3
The Weblate Manual 3.2.2error might look like: OperationalError: (1366, “Incorrect string value: ‘\xF0\xA8\xAB\xA1’ for column ‘target’ at row 1”) UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-3: ordinal messages: 1071: Specified key was too long; max key length is 767 bytes 1709: Index column size too large. The maximum column size is 767 bytes. There are two ways to workaround this limitation. You can configure there must be at least a column called source (which contains the source string) and a column called target (which contains the translation). Additionally there should be the column context (which contains0 码力 | 399 页 | 1.64 MB | 1 年前3
The Weblate Manual 3.5error might look like this: OperationalError: (1366, “Incorrect string value: ‘\xF0\xA8\xAB\xA1’ for column ‘target’ at row 1”) UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-3: ordinal messages: 1071: Specified key was too long; max key length is 767 bytes 1709: Index column size too large. The maximum column size is 767 bytes. There are two ways to work around this limitation. You can configure there must be at least a column called source (which contains the source string) and a column called target (which contains the translation). Additionally there should be the column context (which contains0 码力 | 419 页 | 1.75 MB | 1 年前3
共 251 条
- 1
- 2
- 3
- 4
- 5
- 6
- 26













