Comments

• 

  EdizonTN 02 Nov 21 21:54 GMT-0000

  Hello,

  Firstly, "Update Translation documentation" - It's a really good idea!

  Next, I have a some things for thinking....

  1. synchro between transifex and gitlab - I don't know if it work with gitlab too): https://docs.transifex.com/transifex-github-integrations/github-tx-ui

  2. language.php - what about divide it to two files - one for frontend, second for backend? This is a easyiest way how to speed up a translate process. For the most times, is frontend more important to translate.

  3. Cleanup translation files. Ex. transifex - shows, what is progress in translation for each language.
  Preview @02.11.2021:
  Total strings: 21,776
  Dutch (nl) 4,241 strings to translate, ~ 88% done
  Swahili (sw) 4,767 strings to translate, ~ 87% done
  Arabic (ar) 5,160 strings to translate, ~ 80% done
  Croatian (hr) 5,703 strings to translate, ~ 80% done
  Catalan (Valencian) (ca@valencia) 6,599 strings to translate, ~ 71% done
  ...etc

  But, if I check translation personally - I found, that translated strings contains original english text in many cases!

  You can find here (real state of dutch translation for example): https://www.transifex.com/tiki/tiki-translation/viewstrings/#nl/tiki-master/153829998
  ...how many dutch string you founds?

  Ok, what is real translation status for each language?

  I do a Slovak translation. When I started, was ~ 60% translated strings in Slovak.
  I cleaned non-translated copy only strings. Today's status is: 20% translated. Really translated.
  It's a big difference.

  btw, state of translation was one of things, which had impact on my decision, to use a tikiwiki for my project. Not good thing.
  That's all.

  I believe, that tiki will be have a long and productive live..
  Thanks for reading.
  Ed.

  • 

    Marc Laporte 12 Dec 21 03:11 GMT-0000

    Good point @EdizonTN.

    I just added Translation Priorities

    Thanks!
• 

  hman 02 Nov 21 22:13 GMT-0000

  4,000 - 5,000 strings? Is that the number that was missing and had to be added, if I may ask?
  4,000- 5,000 can hardly be the total number. For German I had to translate ~ 15,000 strings, and I know there are between 2,000 & 3,000 that still need translation. And these figures are after deduplication! Not included in those figures are very numerous strings that cannot be translated unless missing tra() have been added.

  Also, do not forget the ~ 300 strings for Javascript which have to be dealt with separately.

  If you want to see the strings that my tools extract from Tiki 18.8, have a look at my feature request for a "generic" language, there you can find all those strings that can be translated.
  hman

  • 

    EdizonTN 02 Nov 21 22:49 GMT-0000

    Yes, 4000-5000 are string which missing translation.
    Transifex indicating total 21776 translation strings right now...

    • 

      hman 03 Nov 21 20:40 GMT-0000

      Thanks. I salute everyone who, like me, tries to localize Tiki (and despairs over the numerous problems, like missing tra() and and vast problems with ambiguities...).

      What is your target release? I see in Tiki 21.4, for instance, Dutch is just 130 kBytes in size.
      Thanks

      • 

        EdizonTN 03 Nov 21 23:06 GMT-0000

        Hi,
        I do it for tiki 23.0.
        Language files delivered at install are not complette. Due this, dutch can have only 130kB . Check it in the transifex. There are full of strings (but untranslated, copied ).
        I'm in the middle of the frontend translation (I hope) and I found only few errors (can you see in bug reports). I think, v23.0 is better than 21.4.
        But yes, some sentences is truly hard for translate. Especially some special words, as Tracker In other systems is used as forms, for example..... etc,...etc,...
        I wish you a full bag of the patience
        Ed.

        • 

          hman 03 Nov 21 23:34 GMT-0000

          Problematic is the fact that Tiki acts totally ignorant of context when it comes to translation via the tra() function. The button to log out the Wiki is labelled "log out", and the button for paying the items in the shopping cart is also labelled "log out". The translations for these are totally different in German, and possibly in Dutch as well.

          Sometimes strings are totally untranslatable like "of" (used in calendar for repeated events). You will find the same string in totally different contexts in half a dozen other places, but the tra() function simply makes pattern matching.

          And many hundreds of strings cannot be translated at all, because the devs "forgot" to enclose it in tra().

          Very many basic system functions from the menu aren't listed in the PHP code at all. They are defined in the initial .SQL file that gets directly transferred to the database.

          "Tracker" was also really hard to translate. The most direct translation into German, that points out to the root meaning sounds way to much like George Orwell, which is why after a LOOONG period of contemplation I decided to go for "Nachverfolgung", because it is a term with no negative connotation expressing another aspect of "tracker".

          Other critical things were the wild mixture of "layout", "design", "theme", "look & feel" in Tiki...