A p4 check-in failed with the following error:
Submit aborted -- fix problems then use \'p4 submit -c XXXX\'.
Some file(s) could not be transferred from client.
Another reason: P4 considers ANSI-encoded file to be
ANSI file cannot be generally treated as UTF-8 file (which P4 calls
) because not all byte sequences in UTF-8 encoding are valid and P4 produces the following error in such a case:
Translation of file content failed near line 384 file D:\P4
\etc\file.txt
Submit aborted -- fix problems then use 'p4 submit -c 125'.
Some file(s) could not be transferred from client.
In this case, checking line 384 revealed that it contained character ľ
and the file was encoded in ANSI, but Perforce automatically and mistakenly marked it as
(UTF-8).
Solution: perforce filetype and actual file content must be put in sync
if application related to the file allows that, convert the file to UTF-8 and keep file type
.
Generally, this is better solution – you get the file ready for international and special characters.
if file must me kept in ANSI, change file type to