libgit2 / libgit2/libgit2sharp
i18n.commitEncoding is EVIL
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- C#
- Estrellas
- 3.5k
- Forks
- 925
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Recently days I am researching i18n.commitEncoding, It's real an EVIL!!
First of all, I am a Chinese that OS language is en-us with Chinese(simplified) region. The commonly used encoding is GB2312(also GBK, code page 936).
The i18n.commitEncoding was defined in here that Character encoding the commit messages are stored in; git itself does not care per se, but this information is necessary.
OK, It's mean this config will affect the commit messages. but, I have find no any documents to define the format of encoding. I open the references window of Git GUI, and find the Default File Contents Encoding field. First item is System(cp936) of change menu, however, have an item Chinese Simplified (GB2312). They are equivalent in my first impression of two items.
I created a new repository then submit 3 commits with difference i18n.commitEncoding to test they. Both of they commit messages are four words Chinese, and i18n.commitEncoding followed by default, gb2312, cp936. (pushed to https://github.com/Aimeast/TestForFirst/commits/i18n)
git.execan display the second commitGit GUIcan display the first and third commitsGitHubcan display the first and second commits, third commit displayed as JapaneseLibGit2Sharpcan display the first and second commits (third commit not same with Github)
OK, the result real funny. I decompress objects files for digging.
- The first and second commits (e2266b and 38a2b0) were stored as
utf-8 - The third commit (bd9f62) was stored as
gb2312
After my analysis, git.exe can identify format start with cp and followed by code page number. So, we can explain why there is such result.
Now, let's into the issue. The code
// NativeMethods.git_commit_message
[DllImport(libgit2)]
[return : MarshalAs(UnmanagedType.CustomMarshaler, MarshalCookie = UniqueId.UniqueIdentifier, MarshalTypeRef = typeof(Utf8NoCleanupMarshaler))]
internal static extern string git_commit_message(GitObjectSafeHandle commit);
It's always marshal as Utf-8 result in third commit message was messy code. So, I suggest that return raw data then decode string in Proxy.git_commit_message. But, the evil is .Net Framework not support some encoding which supported by git.exe.
Hereafter is my code for detect the encoding for a commit
public static Encoding CpAsEncoding(this Commit commit)
{
try
{
var encoding = commit.Encoding;
if (encoding.StartsWith("cp", StringComparison.OrdinalIgnoreCase))
return Encoding.GetEncoding(int.Parse(encoding.Substring(2)));
return Encoding.GetEncoding(encoding);
}
catch
{
return Encoding.UTF8;
}
}
Not perfect codes, but It's working.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza por NativeMethods.git_commit_message y Proxy.git_commit_message; después, inspecciona cómo se expone Commit.Encoding y cómo Utf8NoCleanupMarshaler gestiona el resultado nativo. Compara el comportamiento con los tres commits de ejemplo usando las codificaciones default, gb2312 y cp936; se considera terminado cuando los mensajes de commit se decodifican correctamente cuando Git declara una codificación de página de códigos compatible.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- csharp, git
- Área
- devtools
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100