Is it possible for CT to show the comments or ID of a string in strings files?
Comments usually appear before a string or section of strings:
/* Comment */
IDs are usually tied to the developers code and appear to the left of the equal sign:
"15.paletteLabel" = "You should translate this part"
"VersionFieldString" = "%@ (%@)";
Comments and IDs usually contextualize the string and appear when a source document is opened as a tab (at the bottom of CT's window), but when working with multiple documents under a single project, I was unable to find a way to make the tab's content change to reflect the selected document.
This second suggestion sounds very time consuming… I'm working with .strings file, normally used in macOS/iOS software localization. I'm not sure I understand your first suggestion… Do you mean opening the strings file, creating a new glossary, confirming all strings as they are, and then opening the file again to translate? Not practical either, as comments wouldn't be interpreted as translatable strings by CT.
I don't see XLIFFs as CT strong suit. Here's how other tools deal with comments and IDs:
If you open the xliff file in CT, you should be able to see the comments as well provided they follow the xliff file specification.
As for the .strings file, try solution with the HTML Source Preview:
1. Open your .strings file in Word and save it as a web page (.html).
2. Open the preview html file via the menu Resources > Open HTML page for source preview... . See it in detail here:
This does, kind of, work. Although “Most of the currently-translated segments will be highlighted in this view” doesn't really happen. This would be ok for a small file, but not on large ones – as the filter seems to ignore the source preview, making search obsolete (and probably tedious, in case it worked).
Moreover, I believe CT should be able to do this. Even though translators have sometimes to resort to multiple loops of workarounds to finally get to work, this doesn't make CT “fun to use”. No intention to sound sour here, your help is much appreciated.
“If you open the xliff file in CT, you should be able to see the comments as well provided they follow the xliff file specification.”
Yes, I do see them in XLIFFs. Would it be possible to have this on strings files as well?
You might submit a support ticket and attach a sample .strings file with comments and IDs to implement them in a future update. Thanks!
Will do, thanks!
For the filter: //comments can be placed behind the translatable string too//
The /* comments */ in .strings files are displayed as CafeTran's notes in the latest build 2017040101. Please download the update 5 and apply it again. You would need to start a new .strings project for the updated filter.