Help needed to translate Projectify

[Nicolas Petton]

Hi!

I've recently added support for translating Projectify[1] strings, and
the next release will be accompanied with a French translation plugin.

I would like to add more languages to Projectify, but unfortunately I
only speak English and Frensh myself, so I'm looking for help :-)

Cheers,
Nico

[1] https://projectify.wiki

[Odin]

I speak Dutch natively, so I could help with translating it into Dutch if you are interested.

Op woensdag 13 januari 2021 om 22:15:58 UTC+1 schreef Nicolas Petton:

[Nicolas Petton]

Odin <odin...@gmail.com> writes:

Hi Odin,

> I speak Dutch natively, so I could help with translating it into Dutch if
> you are interested.

Definitely! Thanks for offering your help!

Would you like me to send you the English tiddlers or do you want to
open pull requests on GitHub?

Cheers,
Nico

[Odin]

I saw that you added a skeleton for the dutch language on your GitHub so I can open a pull request to translate the skeleton, right? I that case, doing it via Github is fine for me.

The tiddler $:/language/projectify/ is made of pairings. I am guessing the translated words go on the right? So I would need to translate the yellow parts?: 

AddProject/Caption: Add project
AddProject/Hint: Create a newproject  

Op donderdag 14 januari 2021 om 17:48:37 UTC+1 schreef Nicolas Petton:

[Nicolas Petton]

Odin <odin...@gmail.com> writes:

> I saw that you added a skeleton for the dutch language on your GitHub so I
> can open a pull request to translate the skeleton, right? I that case,
> doing it via Github is fine for me.

Excellent, thank you!

> The tiddler $:/language/projectify/ is made of pairings. I am guessing the
> translated words go on the right?

Exactly, the translated strings are on the right side.

> So I would need to translate the yellow parts?:

Yes, that's exactly it!

Thanks again!
Nico

[David Gifford]

Added this to the toolmap, and deleted the dead link to ProjectManager.

[Nicolas Petton]

David Gifford <dgif...@crcna.org> writes:

> Added this to the toolmap, and deleted the dead link to
> ProjectManager.

Thanks!

Nico

[PMario]

Hi Nicolas,

I did have a short look to your github repo. .. I think you should do your "string management" in a different way, which is more maintainable.

AND the library / language build process will need a naming convention, which is different to yours. ...

TW knows so called *.multids see: https://github.com/Jermolene/TiddlyWiki5/tree/master/languages/de-DE

Those tiddlers will be expanded to single tiddlers, when the language is activated.

For plugins we use a "namespace" schema like: $:/plugins/<author>/<plugin-name>/<tiddler-name>

For core languages it is: $:/languages/en-GB,  $:/languages/de-DE and so on. ... For language-addons it will probably be eg: $:/languages/de-DE/<author>/<plugin-name>/xxx.multis

I use "probably" here, since the language-addon functionality isn't implemented in the core yet. .. I'll push a DRAFT pull-request today. Then we will see, how it will be implemented.

Please be patient. Otherwise you and others will need to make a lot work several times.

-mario

[Nicolas Petton]

PMario <pmar...@gmail.com> writes:

> Hi Nicolas,

Hi Mario!

> "string management" in a different way, which is more maintainable.

> [...]

> TW knows so called *.multids see:
> https://github.com/Jermolene/TiddlyWiki5/tree/master/languages/de-DE
> Those tiddlers will be expanded to single tiddlers, when the language is
> activated.

I think you've missed the multids tiddlers in Projectify then ;)

I kept a few language tiddlers as separate files on purpose (the ones
that are longer, contain paragraphs or other HTML tags).

> I use "*probably"* here, since the language-addon functionality isn't

> implemented in the core yet. .. I'll push a DRAFT pull-request today. Then
> we will see, how it will be implemented.

Because we lack support for language addons doesn't mean Projectify
cannot be translated today. It's just not as convenient as it could be,
and the UX isn't ideal.

> Please be patient. Otherwise you and others will need to make a lot work
> several times.

The thing is, I need Projectify to be available in French today.

I won't mind moving files to another namespace or restructuring folders
the day language addons land in core, it's nothing more than a sed
script afterall. :-)

Cheers,
Nico

[PMario]

On Saturday, January 16, 2021 at 5:42:20 PM UTC+1 Nicolas Petton wrote:

> "string management" in a different way, which is more maintainable.
> [...]
> TW knows so called *.multids see:
> https://github.com/Jermolene/TiddlyWiki5/tree/master/languages/de-DE
> Those tiddlers will be expanded to single tiddlers, when the language is
> activated.

I think you've missed the multids tiddlers in Projectify then ;)

Yes. I did ;)

 

I kept a few language tiddlers as separate files on purpose (the ones
that are longer, contain paragraphs or other HTML tags).

Ahh. OK. As I wrote, I did have a very fast view. .. Then you are OK. It's probably only the directory structure, that should be changed to make it scale.

 

> I use "*probably"* here, since the language-addon functionality isn't
> implemented in the core yet. .. I'll push a DRAFT pull-request today. Then
> we will see, how it will be implemented.

Because we lack support for language addons doesn't mean Projectify
cannot be translated today. It's just not as convenient as it could be,
and the UX isn't ideal.

The TW "pluginlibrary" edition and the TW library build process need a defined directory structure.

If it is done once, it's more or less a copy paste "thing" to get more plugins / language addons going.

 

> Please be patient. Otherwise you and others will need to make a lot work
> several times.

The thing is, I need Projectify to be available in French today.

I think I do have a working prototype now. Will post the draft soon ..

I won't mind moving files to another namespace or restructuring folders
the day language addons land in core, it's nothing more than a sed
script afterall. :-)

 

Once the system and workflow is approved for the core, it should be relatively simple to adjust it for 3rd party devs.

I did test a workflow to translate the tiddlywiki/menubar to German. The translation workflow is simple and the "build workflow" is "standard tiddlywiki".

The import can be done using the TW ControlPanel : Plugins tab.

It will be the same mechanism for 3rd party plugins.

We will need to improve the UI, since having plugin lists with 100+ elements isn't funny to use in a modal view. But at least it works (for me ;)

have fun!

mario

[Nicolas Petton]

PMario <pmar...@gmail.com> writes:

Hi Mario,

> We will need to improve the UI, since having plugin lists with 100+
> elements isn't funny to use in a modal view. But at least it works (for me
> ;)

I could give you a hand with that if you want. If you open a WIP pull
request, I'd be happy to jump in and think about ways to improve the UI.

Cheers,
Nico