Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In search of an XLIFF editor #2

Open
ghost opened this issue Jul 30, 2015 · 24 comments
Open

In search of an XLIFF editor #2

ghost opened this issue Jul 30, 2015 · 24 comments

Comments

@ghost
Copy link

ghost commented Jul 30, 2015

Hi there,

I plan on helping out with the translations (English -> Turkish) but I haven't been able to find a good XLIFF editor for Mac OS X. I checked the list of apps on Wikipedia but every link on that page has its own different problems. (Some are paid, some links are dead, some requires Java which I refuse to install on any of my computers.) Since I couldn't find a proper app to handle .xliff files (or rather, file) can I get some recommendations?

I bought Xliffie and iXLIFF from the Mac App Store but they didn't let me edit the file. I also downloaded Xcode hoping that it'd have its own .xliff editor since it's able to create and export .xliff files but that didn't work either. The only solution that worked was to download the trial version of an app called Counterparts Lite, but it costs $19 for continued use.

I'd appreciate some help.

Thanks.

@mfb
Copy link
Collaborator

mfb commented Jul 30, 2015

Hi @dombili I don't have a Mac but if I can get my hands on one I'll try some things out.

You could also try the cloud-based translation tools, like memsource.com which has a free personal edition or transifex.com where I already uploaded it: https://www.transifex.com/projects/p/eff/resource/jobid35_en_trxlf/ or others..

@ghost
Copy link
Author

ghost commented Jul 31, 2015

Thanks for your reply, mfb.

I'm somewhat familiar with Transifex, so I tried that first after you added Turkish language, but it doesn't look like Transifex handles xliff files (at least the one you uploaded) well. Here's what I see when I try to start the translation process:

screen shot 2015-07-31 at 07 22 37

As you can see, some strings are properly shown, but some are just a mess. (I'm not familiar with xliff files, so I assume it doesn't suppose to do that.) For example, when I use the .xliff file I got from GitHub on the app I mentioned that works (which I only have the trial version of), strings look like this:

screen shot 2015-07-31 at 07 29 17

That's much more cleaner and easy to work with. I'm sure you'd agree with me.

I can work on Transifex, but as of right now, I'd have to double the time I'm going to spend translating because of how messy the strings look. I'd really appreciate it if you can find a proper solution for Mac (to work locally) or Transifex.

Thank you.

@mfb
Copy link
Collaborator

mfb commented Jul 31, 2015

Meanwhile you could also give Memsource.com a try - it seems to have better XLIFF support (hides the XLIFF markup). I haven't tried other cloud translation services yet.

@ghost
Copy link
Author

ghost commented Jul 31, 2015

I did try memsource.com after going through its invasive account registration process (it required me to enter my phone number and my real name for some reason), but its editor is even worse than that of Transifex. Here's a screenshot:

screen shot 2015-07-31 at 16 59 24

@mfb
Copy link
Collaborator

mfb commented Jul 31, 2015

Interesting, when I use Memsource it hides the markup with little numeric icons:
memsource

@ghost
Copy link
Author

ghost commented Jul 31, 2015

Did you tweak any of the settings? I skimmed through the settings but I didn't see anything that could remove the markup.

Edit: I also tried it on my Windows machine (which I don't use for work), but the result remains the same:

capture

Either I'm doing something wrong or we don't have the same file. (I got the file from the repository.)

@mfb
Copy link
Collaborator

mfb commented Jul 31, 2015

It looks like in your case, for some reason Memsource is using line breaks to detect the strings rather than parsing and interpreting the XLIFF. What was File Type set to when you imported the file?

@ghost
Copy link
Author

ghost commented Jul 31, 2015

I could check, but I get 404 error when I try to reach memsource's login page right now. (What the hell?)

But the file I uploaded on memsource is still on my disk and it's an .xlf file, so it should be the same.

@ghost
Copy link
Author

ghost commented Aug 3, 2015

So, I have an update.

I contacted Transifex's support and asked them why the strings look so messy on their editor. I got this reply just now:

Hello ,

Thank you for using Transifex and for submitting your request.

This is a well known issue and a strange one to solve.
We follow XLIFF 1.0 Specification, where

< and &

must always be used in place of the character they reference. However this is not the whole case, as we change all the entities once the file is being uploaded on our server. The issue starts to become worrying when someone downloads the translations where the entities reference are in place of the characters. But, there are some developers who prefer the entities reference form the characters.

Hope I shed some light in the issue.

Kind regards,
Name redacted

Their response didn't make any sense to me, but that's because I know nothing about XLIFF files or how does one create them. I hope it does help you.

@mfb
Copy link
Collaborator

mfb commented Aug 3, 2015

Yes transifex doesn't interpret the XLIFF and CDATA markup for whatever reason.. they told me that they haven't had a lot of requests for better XLIFF support (yet)? I think you should try to get the file interpreted as XLIFF by memsource, which I assume wasn't happening when you uploaded there.

@ghost
Copy link
Author

ghost commented Aug 3, 2015

I'm pretty sure I uploaded the file as .xlf on memsource but their website doesn't give me whole lot of confidence. (I couldn't login their site for 2 straight days.) Which is kind of important considering I'll be doing my work using their website. I'll probably end up buying that app I'd mentioned. That seems like a more secure way to do it. I wouldn't want my work and time go to waste because of some stupid bug on memsource's editor.

I'm curious though, is working on XLIFF files really that necessary? Clearly there isn't good enough support for this file type. Not that I'm complaining but I must have spent at least a few hours trying to find a solution (and I came up with nothing) which is a time I could've spent translating. There may be some people out there who're willing to help, but don't have as much spare time as me to try to find which app or website works the best (or even work at all) with XLIFF files. That's not an ideal situation for both of the involved parties.

Edit: Can you confirm that these translations work fine with your system? I only translated small part of the file since there's no guarantee that it'll work. Thanks. (Sorry for creating a different repository, I couldn't upload the file here. I'll remove it after your confirmation.)

@yurifw
Copy link

yurifw commented Aug 4, 2015

Hello all, I'm also having trouble editing XLIFF files, I was about to give up when I e-mailed Kim from EFF and got referred here.

I'm on Linux, can someone recommend me one? The wikipedia page didn't help me, the CAT tools I found keep crashing or refuse to open XLIFF files. Still didn't try memsource, I would rather be able to work offline...

update:
I'm giving a try to memsource, so far, everything has gone well, but i am also working with xliff files for the first time, so if someone could test this file i would appreciate

@mfb
Copy link
Collaborator

mfb commented Aug 5, 2015

@yurifw For some reason your translation is missing the XML markup that should be there inside the <target> tag. When you were editing in Memsource you should have seen some highlighted tags that you needed to keep there, they will be filled in with HTML when you download the completed translation.

If you want a local tool, on Linux I could recommend Virtaal. Depending on your distro this might be as easy as apt-get install virtaal. Disabling the plugins under preferences might help if it seems slow (freezing up while you do things). I found it was slow when editing large strings of content (splitting these up into shorter translatable sections of content might make sense).

@mfb
Copy link
Collaborator

mfb commented Aug 5, 2015

@dombili You need to start with job 35: https://github.com/EFForg/www-l10n/blob/master/translations/tr/JobID35_en_tr.xlf Looks like you started with job 21 which is for Farsi.

@ghost
Copy link
Author

ghost commented Aug 5, 2015

Yeah, that's the file I got from Transifex. It was under the Turkish language section and it was for the Secure Messaging Scorecard page. Strange that it's for Farsi. Anyway. I translated the file you linked to (only small parts of it for testing purposes) and uploaded here. Please let me know if it works or not. Thanks.

@yurifw
Copy link

yurifw commented Aug 5, 2015

ok, I modified the file, didn't realize they were missing, I think everything is correct now, if you can confirm that, I'll leave you in peace and work on the translation xD

@mfb
Copy link
Collaborator

mfb commented Aug 5, 2015

@yurifw it worked, although I got a "Failed to validate semantic integrity" warning, probably because only part of the string was there? It's ideal if the XML tags in source and target all match up, so it can be automatically validated and there's no need to eyeball the HTML.

@dombili it worked, although since there are no XML tags (bpt, ept etc.) in your translations, I got a "Failed to validate semantic integrity" warning. It would be ideal if you had a way to include the XML tags in the translation, so the translation can be automatically validated.

@ghost
Copy link
Author

ghost commented Aug 5, 2015

Unfortunately there isn't a way. My editor looks like this (shared previously) and it doesn't even allow me to edit the reference (source) language. I still have to deal with html syntax, but since you don't seem to have an alternative to XLIFF files, I'll just have to suck it up and try to work with it.

If this problem isn't a deal breaker for you, I'll go ahead and buy the app and start translating.

@obazia
Copy link
Contributor

obazia commented Aug 5, 2015

Virtaal works fine on Fedora21. I installed it with a simple yum install from the regular repositories and for the first time I'm managing to use a translation tool on Linux without any problems :)

@mfb
Copy link
Collaborator

mfb commented Aug 5, 2015

@dombili this isn't ideal for me because I can't do automated import. I think it'd be worth trying two things: 1) Virtaal has a Mac beta download and 2) Memsource - did you try setting the file type to XLIFF? And maybe email them if you can't login, or try using a VPN to connect - it could be some network issue? There are probably other options out there, but Virtaal and Memsource are two I know of which allow you to export the bpt and ept XLIFF tags, which give us completely automated import. But if you do use this, we can make it work.. Thanks!

@ghost
Copy link
Author

ghost commented Aug 5, 2015

I realise this isn't ideal. I was mostly asking whether you can work with/around it. I'm out of my comfort zone as well since I'm not using the tools I'm comfortable with.

1- I installed Virtaal but I got this message on my first run without even seeing the UI:

screen shot 2015-08-05 at 20 54 25

Latest update to its beta version was in 2012, so it's safe to assume Virtaal isn't a viable option. At least for me.

2- I was able to login to memsource after deleting cookies and cache files, but that's not my problem with them. Right now I want, but in the future I need, to be able to work offline. Memsource doesn't allow this. I tried installing their app assuming it'd allow me to work offline but when I try to install their Mac app I get this error message:

screen shot 2015-08-05 at 21 01 25

Along with this, my login problems and their online editor looking bootstrap-y, I don't have a lot of confidence that my translations will be safe there. I could've eased my mind by keeping a local copy of my translations on my computer and solved this issue, as well as the problem you're probably gonna have with automation, but as I said, working online won't be an option for me soon.

I realise I'm looking like a whiny person here, but I really am trying to find a good solution for both of us. It just doesn't seem to exist.

I'll buy the app I'd mentioned and start working with that. If there's anything I can do to help you with the automation inconvenience I'll cause you, please let me know.

@mfb
Copy link
Collaborator

mfb commented Aug 5, 2015

Ok. If you can find a way to "transfer from source" or "copy source to target", preserving the XLIFF markup, that would be great. If not, maybe you can file a feature request :)

@yurifw
Copy link

yurifw commented Aug 5, 2015

@mfb I think you got that warning because I only translated part of the file, and I only inserted the html tags on the translated parts, (in memsource, I started translating from line 359, so before that, there is neither text nor html tags before line 359 in the translation). Could that be it?

@mfb
Copy link
Collaborator

mfb commented Aug 5, 2015

@yurifw hope so, it's not especially easy to debug :) Just wanted to flag it. On memsource what I did was click "copy source to target" (Control-Insert) to get all the XLIFF tags in there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants