From owner-freebsd-doc@freebsd.org Fri Aug 10 15:46:18 2018 Return-Path: Delivered-To: freebsd-doc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63DEB106E86C for ; Fri, 10 Aug 2018 15:46:18 +0000 (UTC) (envelope-from yzgyyang@gmail.com) Received: from mail-lf1-f51.google.com (mail-lf1-f51.google.com [209.85.167.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF2D77078F; Fri, 10 Aug 2018 15:46:17 +0000 (UTC) (envelope-from yzgyyang@gmail.com) Received: by mail-lf1-f51.google.com with SMTP id g6-v6so6881881lfb.11; Fri, 10 Aug 2018 08:46:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=sgoCz31mJM+7q8sOP1qWwygotWFFLzyLXbVN3D3dFMw=; b=lu9Ikq8QTkSDhQ1464r1+8yxTkSQ44usO6get10GG/rHk1Va07DlWiXsb7TTHcJ8Hc /rA9aHkaO+mKLnQ0Gh7YVzlG4DhGcmu7tLjUBoKqQZAxB3ZQPUrb5sQEjoKXcY9BLbls oj6psZo8LDSGN6Y75m52vGjYm2rCj8Q1dDb4SzdXqH//KRRiUzHzMQIHlLaido4jdXuK pIGX+aLT16fPeux8XxQRcC3n33luqQPCC4GheSI5bL3HW6QW256Jvxl50n3lnQxRgGw5 QKCPXUoZC5S8mu8nZvuOJBizt7VPFNUR6AIbIgerXEwKREFBT9o0WUrCYg2Km0eTw+YT jKtw== X-Gm-Message-State: AOUpUlG2OE19ERE18W5XHF50tr2H1boI6C2B7iD2IR5x7XbZjFNtqA4S msrLwFY/vilZ/PzrYXMp/JgJgWRobcA= X-Google-Smtp-Source: AA+uWPyVMwOTjnpm/NkNmHmydob32Yv7P8n2u7hy4lDgFaPp3OC3l7QvfjPxYOm7VN8U37cQ+DiSBQ== X-Received: by 2002:a19:a2d5:: with SMTP id l204-v6mr4945974lfe.65.1533914577633; Fri, 10 Aug 2018 08:22:57 -0700 (PDT) Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com. [209.85.208.175]) by smtp.gmail.com with ESMTPSA id j191-v6sm1936977lfj.91.2018.08.10.08.22.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Aug 2018 08:22:57 -0700 (PDT) Received: by mail-lj1-f175.google.com with SMTP id p10-v6so7498257ljg.2; Fri, 10 Aug 2018 08:22:57 -0700 (PDT) X-Received: by 2002:a2e:350b:: with SMTP id z11-v6mr5313217ljz.55.1533914577375; Fri, 10 Aug 2018 08:22:57 -0700 (PDT) MIME-Version: 1.0 References: <018ed56d-4f1c-107b-1c58-047cd3c22fa7@FreeBSD.org> <1b890517-b2b0-efd7-9cb0-0da0241487a2@FreeBSD.org> In-Reply-To: <1b890517-b2b0-efd7-9cb0-0da0241487a2@FreeBSD.org> From: Guangyuan Yang Date: Fri, 10 Aug 2018 11:22:45 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: The Italian translation has not been updated since 2008 To: madpilot@freebsd.org Cc: Groff TheBSDGoat , freebsd-doc@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 15:46:18 -0000 Guido Falsi =E4=BA=8E2018=E5=B9=B48=E6=9C=8810=E6=97= =A5=E5=91=A8=E4=BA=94 =E4=B8=8A=E5=8D=884:38=E5=86=99=E9=81=93=EF=BC=9A > > Looks like we will also need some central repository for partial work to > be shared for collaboration and review. Would you agree that forking > freebsd-doc repo on github and creating a branch from a random revision > (to get a stable target to start with) would be the easiest way to get > started without needing further infrastructure? > > As far as I have understood documentation the suggested way to start > translating is to generate the po file and translate with poedit, am I > correct? > As far as I know, books and articles are being transformed to use PO, while htdocs still use xml for translation. So if you only wish to start with PO files, I think just generate the files and translate with poedit is fine (or even better, work with some online platforms). Just to add my two cents here. Here's some of my previous effort for zh_CN translation: A repo mainly for keeping track of po files and work with volunteers using issues / PR (outdated): https://github.com/yzgyyang/freebsd-doc-cn A Jenkins CI that builds from my fork of freebsd-doc and deploy for preview= : https://jenkins.ygy.io https://charlieyang.me/freebsd-doc-web-deploy/ A monitoring tool for xml translations (in beta): https://docmon.ygy.io Let me know if you need help using any of these personal services above :) Books and articles take huge amount of time and attention to details. I cannot achieve this myself, and in my previous experience, we definitely need some web service setting up for casual translators (I've tried Zanata and Pootle - more investigation is needed). Or Github workflow should work just fine, since po files are just plain text and can be reviewed and merged. Cheers, ygy