Talk:ToolTranslate

Serve tt.js statically?

This is a terrific tool! Thank you for making it. Just wondering if tt.js should be served from //tools-static.wmflabs.org/tooltranslate/tt.js ? I guess just a symlink from ~/public_html/static/tt.js so the current URL doesn't change? Thanks again. — Sam Wilson ( Talk • Contribs ) … 21:42, 20 July 2016 (UTC)

Uhhh... what was that thing again? I added the static/tt.js symlink, but still get a 404. Do I have to do this on a specific server? (I do get much of my other JS from there, but have no idea how to put files there; is there documentation?) --Magnus Manske (talk) 15:00, 21 July 2016 (UTC)

AAH! It needs to be in "~/www/static" (source). All good now. --Magnus Manske (talk) 15:04, 21 July 2016 (UTC)

Oh right! Thanks for figuring it out. I thought it could be either www/static or public_html/static, but I guess not! :) — Sam Wilson ( Talk • Contribs ) … 00:07, 22 July 2016 (UTC)

Composer support?

Nice work with the PHP class; that'll be useful I reckon (I want to use translations in cron jobs). Would you be into adding a composer.json file and adding the repo to Packagist? Would make it simpler to use and update in projects. Thanks! — Sam Wilson ( Talk • Contribs ) … 00:07, 22 July 2016 (UTC)

Frankly, I don't use those when I can avoid it, and I don't know how either of those work. There is a recent (for someone who started on 8-bit CPUs) flood of (language-specific) package managers, some of them nested, and I'm sure it simplifies some things, but I remain somewhat sceptical. That said, if you have some straight-forward documentation on how to do that (and what it's good for), please let me know! --Magnus Manske (talk) 08:44, 22 July 2016 (UTC)

No worries. I guess I wasn't looking at this from the point of view of non-PHP development, where certainly a PHP package manager doesn't seem a very useful thing! So I'll stick to manually defining this package in my composer.json file (which has exactly the same effect as you doing it at the repo level, but is not so good for tracking particular versions; that's not really a problem yet it it doesn't really matter). I might add a note to the docs about using Composer, if that's okay? — Sam Wilson ( Talk • Contribs ) … 09:27, 23 July 2016 (UTC)

Santali language missing from languages.json

Hi, I was trying to translate some tools in Santali language (tooltranslate.toolforge.org). But, I'm unable to, as it is unable to recognize the language code. Adding Santali: ᱥᱟᱱᱛᱟᱲᱤ to below json file may solve the issue.

https://tools.wmflabs.org/tooltranslate/data/languages.json

Thanks Rocky 734 (talk) 02:19, 24 July 2023 (UTC)

Licensing of translations?

Are translators asked to apply any content license to their translations, such that they could be freely redistributed, rather than linked? I get that most translations are relatively short, but I think not beyond the level of copyrightability. For an example, TranslateWiki's About page:

Translations by translators are licenced CC-BY 3.0, and derivative works may also be licenced under the licences of the respective Free and Open Source projects the translations have been or will be added to.

I'm considering a proposal for development funds for Cradle to be rebuilt as an extension integrated into Wikibase's UI, and one potential goal would be to eliminate external dependencies for e.g. corporate/government/institutional installs. GreenReaper (talk) 17:08, 13 April 2024 (UTC)