11
gtop00
Re: New branch for xoops translation on SVN
  • 2008/5/6 22:54

  • gtop00

  • Friend of XOOPS

  • Posts: 498

  • Since: 2004/11/13


Do you really think that we need such tool?
We do not create code/versions when we translate; we just translate existing text on existing code/versions

I believe that most important is to upgrade (add permissions and check functionality) and use Lang_Tool module. Joomla has a similar module (component).

Using WinMerge and Lang_Tool is more than enough for translations.

Also, I would like to propose the use of an “International” multilingual site where we could work with Lang_Tool and test the translations.

12
JulioNC
Re: New branch for xoops translation on SVN
  • 2008/5/7 2:07

  • JulioNC

  • Quite a regular

  • Posts: 239

  • Since: 2004/10/8


Please, you could see a readme.txt file with new example in it.

Quote:

gtop00 wrote:
Do you really think that we need such tool?
We do not create code/versions when we translate; we just translate existing text on existing code/versions


I don't think so, if you work together with others translators.
Spanish language have a lot of Anglicism, Jargon, etc. so We need to compare with other spanish speakers.

Quote:

Also, I would like to propose the use of an “International” multilingual site where we could work with Lang_Tool and test the translations.


No, is too much work!
Have you got time for it?


Maybe D.J will discuss with us for it as soon as posible.
By the way, Who is The XOOPS Translation Leader ?

13
phppp
Re: New branch for xoops translation on SVN
  • 2008/5/7 2:24

  • phppp

  • XOOPS Contributor

  • Posts: 2857

  • Since: 2004/1/25


I would call it "Localization Team". Once we enables l10n/i18n in XOOPS 3.0+, the team will deal not just 'translation'.
And, what is the relationship with "Internal Team"? I believe you two teams have talked : )

As for tools, I don't have any preferences, but some points:
1 can do the "translation" job
2 easy to use
3 easy to learn how to use
4 the tool itself is translatable : )

14
anderssk
Re: New branch for xoops translation on SVN
  • 2008/5/7 13:17

  • anderssk

  • Quite a regular

  • Posts: 335

  • Since: 2006/3/21


So far as I can see Drupal is closed for SVN.
Joomla has not a singel SVN for language. Some of the local support sites has it own SVN.

But we need to create something that serve XOOPS best

15
gtop00
Re: New branch for xoops translation on SVN
  • 2008/5/7 18:23

  • gtop00

  • Friend of XOOPS

  • Posts: 498

  • Since: 2004/11/13


Hi Julio,
Quote:

JulioNC wrote:
...
I don't think so, if you work together with others translators.
Spanish language have a lot of Anglicism, Jargon, etc. so We need to compare with other spanish speakers.
...

I guess that many language have differences from place to place. This could be considered as a "different" Language instead of a Language "Version", example: Portuguese - Portuguese do Brazil.
Also, It would not be easy to follow up translation versions in addition to XOOPS versions. From the other hand, a wiki or WinMerge could be used for comparizons between the same Language files changes.

Myself (and many others I believe) who are doing translations, are not familiar with coder's special tools and we have not the time to learn them.

From the other hand, in case that we are going to use a XOOPS specific Translation tool (like Lang_Tool), how can we use SVN at the same time?

Quote:

JulioNC wrote:
...
No, is too much work!
Have you got time for it?
...

How much work could be to maintain an empty (from content) site?
I strongly believe that having an International / Multilingual demo/test XOOPS site, would be the best example regarding XOOPS international abilities. I personally have limited time but would be glad to work in such project.

16
gtop00
Re: New branch for xoops translation on SVN
  • 2008/5/7 20:28

  • gtop00

  • Friend of XOOPS

  • Posts: 498

  • Since: 2004/11/13


Quote:

phppp wrote:
I would call it "Localization Team". Once we enables l10n/i18n in XOOPS 3.0+, the team will deal not just 'translation'.

Very interesting!

But what is l10n, i18n ?...

It took me some time to understand:
l10n stands for localization, and i18n, for internationalization. Counting the number of letters between the first and the last letters in those words explains the numbers in the names. Laziness is universal!
[from here]

17
anderssk
Re: New branch for xoops translation on SVN
  • 2008/5/8 11:23

  • anderssk

  • Quite a regular

  • Posts: 335

  • Since: 2006/3/21


Can wee use the download section on SF.NET
There are a category "XOOPS Core Translations" but not mutch in it.

Maybe it could be categorised and local support sites could get access?
I don't know if it is possibel to add access to some parts of the filedirectory?

XOOPS Core Translations
---> Language
----> Core
----> Modules

18
gtop00
Re: New branch for xoops translation on SVN
  • 2008/5/8 12:49

  • gtop00

  • Friend of XOOPS

  • Posts: 498

  • Since: 2004/11/13


You are wright! See also this thread.
There were also many translations in dev.xoops which I cannot find right now.

19
anderssk
Re: New branch for xoops translation on SVN
  • 2008/5/8 21:30

  • anderssk

  • Quite a regular

  • Posts: 335

  • Since: 2006/3/21


precise that is the problem.
If wee all have to post in a thread when we have translated some core or module it wil be the root of all evil.

Where to look - I think the place the useres dowload the core files, should contain the language-files for both modules and core?

20
Mamba
Re: New branch for xoops translation on SVN
  • 2008/5/9 2:12

  • Mamba

  • Moderator

  • Posts: 11366

  • Since: 2004/4/23


Anders, you're making a very good point. We need to look from the user perspective - what is the most user-friendly way of doing the translation for download?
Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

Login

Who's Online

110 user(s) are online (72 user(s) are browsing Support Forums)


Members: 0


Guests: 110


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits