[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gettext] Bug#680630: [gettext] msgmerge: merges distinct src co
Re: [bug-gettext] Bug#680630: [gettext] msgmerge: merges distinct src comment lines (fwd)
Fri, 13 Jul 2012 09:06:29 +0200
KMail/1.13.7 (Linux/220.127.116.11-0.5-default; KDE/4.6.4; x86_64; ; )
> [: Bastien Montagne :]
> In our context (Blender translation), lines like
> “bpy.types.Image.mapping:'REFLECTION'” are source lines exactly as
> "standard" ones, inasmuch they allow us to point to one usage of the given
> msgid… Actually, many of our msgids only have that kind of source, without
> any relation to their actual location in code.
Note that this is not about the definition, but about practical usage. For
example, a powerful dedicated PO editor can open the source file and show
the referenced line, in a source view pane of some sort, at translator's
single keypress; it may even automatically display source lines as
translator moves through messages. This is the intent of source references.
Obviously, PO tools cannot rely on source references if they are in a
custom, specific to the project format. If that is the case, then only
translators (or tools) involved with the project know how to use such
references, and then they count as project-specific information. The
expected place for such information is #. comments.
Chusslove Illich (Часлав Илић)
Description: This is a digitally signed message part.