It seems that omegaT doesn't create an XLIFF but just translates the PO directly. Let me verify that ...
I see that the first suggestion loses the plural:
Is converted to XLIFF as:
Here is the confirmation of a seasoned user of omegaT:
No, OmegaT does not create an intermediary file. It translates the source file directly.
That means that either the Maxprograms or the po2xliff solution has to be taken (can be used). Until Igor decides to support PO natively.
thanks very much for the help! I tried the online converter at localise.biz but it has a file size limit of 1MB so it didn't work in this case, but the Maxprograms CLI tool is intuitive and it worked a dream, so thanks once again!
is there any indication of whether Igor is intending to introduce native PO support? like I said, I'm sure the question has been asked many times but it would be quite ideal not to need to rely on these tools every time.
Igor can only answer that question himself :).
BTW: Where exactly did you download the Maxprograms CLI tool? Did you have to compile it? On what OS are you?
Sorry, I found them. Kind of Rodolfo, to make them available!
ah you know what good point let me just put the details here for anyone else's reference
this is the CLI program and this is the GUI equivalent.
the CLI is available for macOS (which I'm on currently), Windows and Linux. I ran the following
[path to binaries]/convert.sh -file [path to file I converted].po -srcLang en-US -tgtLang kw
which automatically recognised the .po file without any other command line options. replace the code after
to ISO language codes of your choice, and voilà, a usable XLIFF file in the directory of the files you want to convert!
alternatively, use the XLIFF Manager GUI to achieve the same goal by setting the same options. both also provide you with the option to create XLIFF 2.0 files, if you want!
Since during my trial with XLIFF Manager I couldn't have CTE work with a sdlxliff file converted back from xlf (XLIFF 1.2), thus being warned that it could not open it "because it was unsegmented" (not true, because I could see both source and target segments), I tried with XLIFF 2.0 but this time CTE went into a sort of loop and I had to kill the process.
Is CTE incompatible with the XLIFF 2.0 protocol?
There are numerous flavours of the xliff format produced by various tools. You can create a support ticket attaching those xliff files.
I'm sure this must have been asked already, but does the team intend to integrate support for .po files at any point?
Background: Transifex in particular is extremely annoying because it locks downloading translations as XLIFF files behind a subscription (like $100 a month lmao you really thought!!!!) and only allowing free users to download .po files. Competitors like Trados, Swordfish, OmegaT, Wordfast etc. all support .po files but CaféTran doesn't, and I really would love to continue using CaféTran for localising strings in .po format without having to rely on third party tools. So, do devs intend to add native support into CaféTran in an upcoming release?
In the meanwhile, are there any recommended ways to convert .po to .xliff and vice versa for use in CaféTran without paying through the nose for third-party tools that I'm not gonna use? Thanks in advance!