Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Advertises for Translators

minahito
2007-05-16
2013-04-25
  • minahito
    minahito
    2007-05-16

    The XOOPS Cube project has made the patch trackers and has defined the rule for translators, to increase commiters. We welcome translators who have made language files for Legacy package. The project asks them to handle langyuage files directly on CVS. If you hope to take a part in the project as translators, write your hope at this topic as with the following format.

    ----

    Language: {Language name}
    Need the Commit Privilege: {Yes or No}

    * You have to attach the file which you have translated already. It proves that you can contribute to the project.

     
    • GIJOE
      GIJOE
      2007-05-16

      Language:
      Need the Commit Privilege: No

      These files are made from original japanese and patched a few lines by me.

       
      • minahito
        minahito
        2007-05-16

        Thank you!

        I've downloaded the language files from your site and have committed them to CVS with the following "README.ja.txt". In README, I request users to check missing updating.

        If this README has some problem, point it. I'll modify it soon.

        ----
        [README.ja.txt]

        GIJOEさんが作成された Legacy 2.1 用 japaneseutf 言語ファイル群を収録させていただいたものです。EUCメッセージカタログに修正が入った場合に同期するよう一応チェックしていますが、不都合があればフォーラムで報告をお願いします。 mbstring が必須になります。

        以下、GIJOEさんが説明されている「既存の EUC-JP サイトを切り替える場合」の使用方法です。

        1. サイト内容を記録しているデータベースをバックアップします。
        2. そのファイル全体を UTF-8 へ返還します。
        3. サイト一般設定で言語を japaneseutf に切り替えます。
        4. 2で変換したファイルを用いてリストアします。

        XOOPS 日本版は長い間 EUC が用いられており、日本製モジュールも多くが EUC 環境を対象に作られているため、 UTF-8 稼働は導入モジュール次第では EUC ほど安定しないと思われます。注意して使ってください。

        また、国際化関係で Legacy 自体の仕様も微妙に変化し、 japaneseutf へのフォローアップ状況が変わることもあると思います。精力的なチェックとフィードバックをお願いします。

        (加えて、 japaneseutf が EUC 側の japanese と齟齬を起こしていないかチェックをお願いします)

        最後になりましたが、ファイルを作成配布されている GIJOE さんにこの場を借りてお礼申し上げます。

        GIJOE さんのサイト: http://xoops.peak.ne.jp/

         
    • wanikoo
      wanikoo
      2007-05-16

      Hi^^//

      Korean language files for XC Legacy is already available!!
      You can download them here!
      -----
      #Korean
      xoopscube-2.1.0-lang-kr-euckrdiff.zip
      http://dev.xoops.org/modules/xfmod/project/showfiles.php?group_id=1189&release_id=944&dl=3219
      #Korean UTF-8
      xoopscube-2.1.0-lang-kr-utf8diff.zip
      http://dev.xoops.org/modules/xfmod/project/showfiles.php?group_id=1189&release_id=945&dl=3220
      ------

      Language: Korean and Korean UTF-8
      Need the Commit Privilege: YES

      from wanikoo!
      ^^//

       
      • minahito
        minahito
        2007-05-17

        Welcome wanikoo!

        I've added your account to this project. Please check that you can access our CVS directly.

        Now, we have to decide that Legacy contains which EUC-KR or UTF-8 under the standard language directory. Japanese puts EUC-JP under the standard language directoy, and put UTF-8(JP) under the extras directory.

        Example)

        - /languages/japanese/  <--- EUC-JP
        - /extras/japanese_utf/ <--- UTF-8(JP)

        Because there are many Japanese users who are using EUC-JP now. And, most modules have only Japanese language files.

        What do you do Korean files?

        [Pattern A] (The same pattern as JP)
        - /languages/korean/  <--- EUC-KR
        - /extras/korean_utf/ <--- UTF-8(KR)

        [Pattern B]
        - /languages/korean/  <--- UTF-8(KR)
        - /extras/korean_euc/ <--- EUC-KR

         
    • wanikoo
      wanikoo
      2007-05-17

      Hi, minahito!
      [quote]
      I've added your account to this project.
      [/quote]
      ^^;;
      Thanks!
      [quote]
      [Pattern A] (The same pattern as JP)
      - /languages/korean/ <--- EUC-KR
      - /extras/korean_utf/ <--- UTF-8(KR)
      [/quote]
      Umm...
      Still
      most Korean are more familiar with EUC-KR than UTF-8
      and XC Legacy doesn't adopt UTF-8 as default encoding...
      So...
      I think Pattern A is better than Pattern B considering current situation!
       

       
      • minahito
        minahito
        2007-05-18

        > most Korean are more familiar with EUC-KR than UTF-8
        > and XC Legacy doesn't adopt UTF-8 as default encoding...
        > So...
        > I think Pattern A is better than Pattern B considering current situation!

        OK! Japan has the same situation. Do you have prepared your CVS client to commit files to CVS? If you have not prepared it, I will commit Korean language files with pattern A as first runner.

        Because Legacy 2.11 will not change language definitions, it's possible to release.

        And, I think that korean_utf directory may need "README.kr.txt" which expains "how to use this language directory".

        japanese_utf directory has the following README.ja.txt
        http://sourceforge.net/forum/message.php?msg_id=4315232

        ------
        If you will change your existing site from EUC-JP to UTF-8.

        1) Back up the database which contains contents of the site.
        2) Convert the backup file to UTF-8.
        3) Change the language to japaneseutf in the XOOPS config.
        4) Restore by the converted backup file in 2)

        XOOPS Japanese Edition uses EUC for a long time. So most modules which made in Japan have been developed for EUC environment. Therefore, you may encounter some troubles under UTF-8 language settings. Pay attention, please.
        ------

        I can't write a such README in Korean. Could you write README.kr.txt?

         
    • wanikoo
      wanikoo
      2007-05-19

      [code]
      If you have not prepared it, I will commit Korean language files with pattern A as first runner.
      [/code]
      Please!!
      Umm..
      anyway...
      I will reinstall it on my notebook soon!
      [code]
      Could you write README.kr.txt?
      [/code]
      Sure!
      I will translate README.ja.txt into README.kr.txt by Monday!

      PS:
      ^^;;
      Sorry for my late reply!

       
      • minahito
        minahito
        2007-05-19

        Ok, I'll commit these files! ^^

        > Sorry for my late reply!

        Never mind. This is open source. So you may do it when you get enough free time.

         
    • wanikoo
      wanikoo
      2007-05-20

      [quote]
      I will translate README.ja.txt into README.kr.txt by Monday!
      [/quote]
      Here is README.kr.txt !
      Downlaod:
      http://www.wanisys.net/data/README.kr.txt
      ^^//
      [ko]
      현재
      XOOPS Cube Legacy는
      UTF-8을 기본 인코딩으로 채택하고 있지 않습니다.
      일부 국가/지역에서 아직 UTF-8 이 널리사용되고 있지 않는 점 등등
      그 이유는 여러가지가 있습니다만...

      아무튼 이러한 사정으로 인해
      한국어 언어팩도
      현재 EUC-KR 을 기본 인코딩으로 채택하고 있습니다만
      필요하신 분들을 위해 UTF-8 버전도 추가적으로 제공하고 있습니다.

      EUC-KR: ~/language/korean/*.*
      UTF-8: ~/language/koreanutf/*.*

      <한국어 UTF-8 언어팩 사용법>
      1,해당 언어팩을 다운받으신 후 XOOPS Cube Legacy Package에 추가/복사합니다.
      2,언어파일용 디렉토리에 koreanutf 디렉토리가 성공적으로 추가되었는지 확인합니다.
      3.INSTALL.ko.html 을 참고하여 설치를 진행합니다.
      ( 설치언어로 koreanutf 을 선택하는 것 이외엔 EUC-KR 과 동일합니다.)

      한국어 UTF-8 언어팩으로 사이트를 운영하실 경우엔
      사이트구축단계에서부터 위와 같이 UTF-8로 설치하실 것을 권합니다.
      기존 EUC-KR 로 운영중인 사이트를 UTF-8 로 변환하여 사용하시는 것은
      별로 추천하지는 않습니다만 방법을 간단히 설명드리면 다음과 같습니다.
      1, 한국어 UTF-8 언어팩을 사이트에 추가합니다.
      (복사하신 후 koreanutf 디렉토리가 정상적으로 복사되었는지 꼭 확인하시기 바랍니다.)
      2, 사이트일반설정에서 사용언어를 korean 에서 koreanutf 로 변환합니다.
      3, DB 를 Backup 받습니다.
      4, 백업받은 내용을 UTF-8 로 변환처리합니다.
      5, 기존 DB를 변환처리한 DB 로 치환합니다.
      <주의>
      2의 방법은 비추천입니다.
      가능하시면 config 테이블에서 해당 항목(language)을
      직접 korean에서 koreanutf로 변경하실 것을 권합니다.

      기타 자세한 사항은
      XOOPS Cube 한국어 지원사이트의 포럼을
      참고하시기 바랍니다.

      PS:
      일부 모듈의 경우 UTF-8 환경에서
      정상적으로 작동하지 않을 수도 있으니 주의바랍니다.

      ------------------------------------------
      XOOPS Cube  Korean Support Site
      http://www.xoops.ne.kr/xoopscube/
      [/ko]

       
      • minahito
        minahito
        2007-05-21

        Thank you very much!

        I'll commit this README.kr.txt to CVS soon.

        And, we have to consider about new language files' directoy name;
        http://sourceforge.net/forum/message.php?msg_id=4321803

        If you are OK, tell me your ideas, please.

         
    • wanikoo
      wanikoo
      2007-05-21

      [quote]
      Here is README.kr.txt !
      Downlaod:
      http://www.wanisys.net/data/README.kr.txt
      [/quote]
      Sorry! Broken Link by my mistake!
      T.T
      Here is another download link!
      http://www.xoops.ne.kr/data/README.kr.txt

       
      • nobunobu
        nobunobu
        2007-06-26

        Hi, wanikoo!!

        Thank you very much for your Korean language file contribution.
        There is a few request for you , about your contribution.

        1. We placed Korean translated GPL and LGPL license document, now.
           I know these file exist just for helping korean speakers.
           But, as you know, GPL is a very nervous to make a strict interpretation
           of this license document.
           So we don't want bundle any unofficial translated GPL document.
           If you want to introduce License document in your language,
           would you make a link in a docs/INSTALL.xx.html.

        2. You add license comment lines in every language files.
           And adding specifing copyright notice.
           under /html/language/korean/ directory, you added following lines.
           > //  ------------------------------------------------------------------------ //
           > //                XOOPS - PHP Content Management System                      //
           > //                    Copyright (c) 2000 XOOPS.org                           //
           > //                       <http://www.xoops.org/>                             //
           > //  ------------------------------------------------------------------------ //
           It is collect.

           But under /html/modules/legacy/language/korean/ directory, you added following lines.
           > //  ------------------------------------------------------------------------ //
           > //                XOOPS Cube - PHP Content Management System                 //
           > //                    Copyright (c) 2006 XOOPSCube.org                       //
           > //                       <http://www.xoopscube.org/>                         //
           > //  ------------------------------------------------------------------------ //
           You may think all legacy modules language files are newly written by XOOPSCube.org.
           But in strict sense, some language files in Package Legacy modules are derived from
           XOOPS2 language files. It's very gray zone. But, at least following language files'
           copyright belong to XOOPS.org

           - /html/modules/legacy/language/xxxxx/global.php
                (Moved from /html/language/xxxxx/global.php and change some lines)
           - /html/modules/legacy/language/xxxxx/block.php
                (Block logic is almost same as X2 now)
           - /html/modules/user/language/xxxxx/block.php
                (Block logic is almost same as X2 now)

           So, please change copyright line in these file to
           > //  ------------------------------------------------------------------------ //
           > //                XOOPS - PHP Content Management System                      //
           > //                    Copyright (c) 2000 XOOPS.org                           //
           > //                       <http://www.xoops.org/>                             //
           > //  ------------------------------------------------------------------------ //

        Regards.

         
    • gigamaster
      gigamaster
      2007-05-22

      Hi,

      Since XC beta release everything works fine for Latin languages,
      here's the beta french translation. It should go with Pattern A

      http://xoopserver.com/uploads/xoops_cube_21_beta_french.zip

      Language: French
      Need the Commit Privilege: YES

      I hope to finish final translation this week.

      Thanks

       
    • plusangel
      plusangel
      2007-06-01

      My warm regards to all my friends in xoops cube!

      I have also the greek utf translation ready.
      I want to fix a couples of typos and make it available.

      I don't know it is wise to wait for the 2.1.1 version but probably will not contain any lang diffs.

       
      • minahito
        minahito
        2007-06-01

        Hi plusangel,

        > I don't know it is wise to wait for the 2.1.1 version but probably will not contain any lang diffs.

        Because 2.11 is just minor change, it will not have any diffs. But, the installer may have a new message;

        http://sourceforge.net/tracker/index.php?func=detail&aid=1729299&group_id=159211&atid=943472

        If Legacy installer will have this, I will report it here.

        I'm looking forward to receive French & Greek files! :D

         
    • gigamaster
      gigamaster
      2007-06-01

      Hi,

      I'm on the way !
      Just get some free time and start 2.1 fr_utf8

      =)

       
    • plusangel
      plusangel
      2007-06-11

      Dear friends,

      In this place (http://www.xoopscube.gr/repository/greekutf.zip) you can find the greek utf translation of Xoops Cube 2.1.

      Language: Greek 
      Need the Commit Privilege: YES 

      Probably I need to have the ability to update the language files with typos corrections' or added constants. (You will explain me the way :))

      Sorry for the delay!

       
    • Alfred
      Alfred
      2007-06-16

      the german language is in progress :-)

      Alfred

       
  • jogeto gore
    jogeto gore
    2010-11-12

    I've added your annual to this project. Please analysis that you can admission our CVS directly.

    Now, we accept to adjudge that Legacy contains which EUC-KR or UTF-8 beneath the accepted accent directory. Japanese puts EUC-JP beneath the accepted accent directoy, and put UTF-8(JP) beneath the annual directory.

    Example)

    - /languages/japanese/ <-- EUC-JP

    - /extras/japanese_utf/ <-- UTF-8(JP)

    Because there are abounding Japanese users\Checkpoint certificationwho are application EUC-JP now. And, a lot of modules accept alone Japanese accent files.

    What do you do Korean files?

    (The aforementioned arrangement as JP)

    - /languages/korean/ <-- EUC-KR

    - /extras/korean_utf/ <-- UTF-8(KR)

    - /languages/korean/ <-- UTF-8(KR)

    - /extras/korean_euc/ <-- EUC-KR

    #

    wanikoo

    2007-05-17 23:50:06 GMT

    Hi, minahito!

    I've added your annual to this project.

    ^^;;

    Thanks!

    (The aforementioned arrangement as JP)

    - /languages/korean/ <-- EUC-KR

    - /extras/korean_utf/ <-- UTF-8(KR)

    Umm…

    Still

    most Korean are added accustomed with EUC-KR than UTF-8

    and XCAdobe certificationLegacy doesn't accept UTF-8 as absence encoding…

    So…

    I anticipate 3COM certificationArrangement A is bigger than Arrangement B because accepted situation!
    Apple certification

     
  • jogeto gore
    jogeto gore
    2010-11-12

    Hi, minahito!

    I've added your HP certification  annual to this project.

    ^^;;

    Thanks!

    EXIN certification  (The aforementioned arrangement as JP)

    - /languages/korean/ <-- EUC-KR

    - /extras/korean_utf/ <-- UTF-8(KR)

    Umm…

    Still

    most Korean are added accustomed with EUC-KR than UTF-8

    and XC Legacy doesn't accept UTF-8 as absence encoding…

    So…

    I anticipate Arrangement A is bigger than Arrangement BISC certification because accepted situation!