During the process of translating Blender’s UI, I encountered many ‘technical’ terms that only developers, probably who owned the code lines, could really understood what it means. Searched the source code and found no comments which could help to unpack the meanings of these cryptic words. Here is an example:
Well. It is bounded in the text by a lot of mention to an “origspace”.
So, I suppose that means Origin Space or Original Space.
PreviewLoopCol is bounded by stuff called Preview_MLoopCol.
So, I guess that is related to color (abbreviated Col in other places) of material preview.
That only make sense to developers. But I don’t recall that being exposed to users in UI.
That’s for sure, if you are writing code everyday. It’s not for us translators though. If I had been a Blender developer then it would probably much easier for me to recognise, but then I only know the areas I am working on, a translator is different in that we have to overlook the entire software. It would be so much better for translators if Blender developers also maintain the habit of inkscape developers by giving comments on the terms. Perhaps the API for messages needed to include this option to allow developers putting a comment next to the message and render it as part of the user-comments in PO Message in python (babel.messages).
A loop in Blender Python terms is IIRC a corner of a polygon.
Vertex colors are saved in corners (or loops) I believe, so perhaps this has something to do with this.
