Yes, I understand it would be nice. However, those comments ideally come from the source code, and the translation platform is really something different from being able to edit the source code.

I'm closing this as WONTFIX, because it's out of scope.

lasse.liehu wrote:

Sorry I didn't make it clear earlier, but I meant uses of the field that are language specific. Not the documentation that should be in the source code.

This includes writing down the reasons for why the current translation for a specific message was done the way it was done or why the translation is currently the way it is.

I understand that most of them should probably ideally be instead written in change summaries (at least in the old UI; don't know about the new UX). And also that term choices should probably ideally be documented in glossaries when they are available.

Besides that I guess the only use case I had in mind was including comments for use with external tools. Like in KDE two language teams use the translator comment field to add properties to messages. The properties are then gathered from PO files to property map files, which are then distributed with the PO files.[1] The properties can then be accessed from other messages using a certain syntax. The properties can be different noun cases, conjugations and anything arbitrary.

Having now thought more about this, this could complicate things more than it would be worth. Sorry for the noise.

[1] http://pology.nedohodnik.net//doc/user/en_US/index-mono.html#sv-collect-pmap