From javad.kouhi at gmail.com Wed Apr 1 04:17:55 2020 From: javad.kouhi at gmail.com (Javad Kouhi) Date: Wed, 1 Apr 2020 08:47:07 +0430 Subject: Self-introduction: Javad Kouhi In-Reply-To: <20200331204305.gyq2mlh4mv7lykob@t480.local> References: <20200331.124527.1078840241867193092.hrs@FreeBSD.org> <20200331170132.gyjlo7nel3cajidf@t480.local> <20200401.035204.1608271793023335727.hrs@FreeBSD.org> <20200331204305.gyq2mlh4mv7lykob@t480.local> Message-ID: Hello and thank you for the replies. > Could I suggest starting with small documents, like > articles/leap-seconds or articles/ipsec-must ? I'll prepare a small article, so we would have something to start with, will let you know when I'm finished. > The UI is doing something because the string is saved differently in the > repository: > https://people.freebsd.org/~dbaio/weblate/2020-03-31-093415_747x699_scrot.png The UI is showing the code in RTL format. In this form, the Persian text is shown correctly, but the tags are not. On the other hand, in this screenshot: https://people.freebsd.org/~dbaio/weblate/2020-03-31-093415_747x699_scrot.png The code is shown in LTR format. In this form, the tags are shown correctly, but the Persian text looks messy. If one is shown correctly, the other would look messy. They can't be shown correctly at the same time. This is a universal problem with RTL languages and is not specific to Weblate, which in that case, we could have simply do the translation somewhere else and commit them here when they're ready. The problem is that, even if we take the source code somewhere else like a desktop text editor, it will still suffer from the same problem (I'm yet to see a document/text editor that can handle it correctly). Sometimes it doesn't matter (as in most web pages which are usually generated automatically), sometimes it does matter, when people have to directly deal with the tags. > I've built these initial translations you made, without any > modification, see the results here: > https://dbaio.bs2cloud.com.br/doc/fa01/fa_FA.UTF-8/books/handbook/ Although this initial build is based on just some test sentences, it looks very promising. So, the compiled form seems to be already OK, the main problem is with the source code. > Does "translating tags" mean replacing the tag name of with > Parisian counterpart in RTL, or the whole tag including <> in RTL? I mean something like http://www.FreeBSD.org instead of http://www.FreeBSD.org. This is the solution adopted by similar projects, such as the Persian Wikipedia and the xepersian package for LaTeX. I don't know if that's possible here, I guess it requires fundamental modifications to the docproj infrastructures. I could do the translation in the case those modifications to the infrastructures are not a concern. > Could you show a typical HTML file in UTF-8 Persian? I would like to > know what tags look like. Is this good enough? https://kouhi.org/sample.html On Wed, Apr 1, 2020 at 1:13 AM Danilo G. Baio wrote: > > On Wed, Apr 01, 2020 at 03:52:04AM +0900, Hiroki Sato wrote: > > "Danilo G. Baio" wrote > > in <20200331170132.gyjlo7nel3cajidf at t480.local>: > > > > db> > Could you show a typical HTML file in UTF-8 Persian? I would like to > > db> > know what tags look like. > > db> > > db> I would like to see some examples as well. > > db> > > db> Persian was already marked as RTL on Weblate. > > > > Yes, but it still needs direction attributes in the DocBook results > > even if editors and input fields on the web browsers support RTL in > > the user interface. We have options such as "RTL by default and > > marking up the LTR parts" and vice versa. And RTL and LTR in the > > same #PCDATA with no tag will not be rendered correctly. Probably we > > need to take care of them in the XSLTs after checking what "natural > > way" to write a marked-up document in HTML or XML is. > > > Thank you both for the explanations. > > So, this will be an interesting issue to fix, let's check some real > issues in our documents and the best way of fixing it. > > We will need your help Javad. > > Could I suggest starting with small documents, like > articles/leap-seconds or articles/ipsec-must ? > > > > > > db> I've built these initial translations you made, without any > > db> modification, see the results here: > > db> https://dbaio.bs2cloud.com.br/doc/fa01/fa_FA.UTF-8/books/handbook/ > > db> > > db> If this is good, I can go forward and add a Jenkins job to build it regularly. > > > > The LANG_TERRITORY part must be fa_IR, not fa_FA. > > I'll fix that, thank you. > > -- > Danilo G. Baio (dbaio) From javad.kouhi at gmail.com Wed Apr 1 11:02:55 2020 From: javad.kouhi at gmail.com (Javad Kouhi) Date: Wed, 1 Apr 2020 15:26:48 +0430 Subject: Self-introduction: Javad Kouhi In-Reply-To: References: <20200331.124527.1078840241867193092.hrs@FreeBSD.org> <20200331170132.gyjlo7nel3cajidf@t480.local> <20200401.035204.1608271793023335727.hrs@FreeBSD.org> <20200331204305.gyq2mlh4mv7lykob@t480.local> Message-ID: I just finished articles_ipsec-must. On Wed, Apr 1, 2020 at 8:47 AM Javad Kouhi wrote: > > Hello and thank you for the replies. > > > Could I suggest starting with small documents, like > > articles/leap-seconds or articles/ipsec-must ? > > I'll prepare a small article, so we would have something to start > with, will let you know when I'm finished. > > > The UI is doing something because the string is saved differently in the > > repository: > > https://people.freebsd.org/~dbaio/weblate/2020-03-31-093415_747x699_scrot.png > > The UI is showing the code in RTL format. In this form, the Persian > text is shown correctly, but the tags are not. On the other hand, in > this screenshot: > > https://people.freebsd.org/~dbaio/weblate/2020-03-31-093415_747x699_scrot.png > > The code is shown in LTR format. In this form, the tags are shown > correctly, but the Persian text looks messy. > > If one is shown correctly, the other would look messy. They can't be > shown correctly at the same time. This is a universal problem with RTL > languages and is not specific to Weblate, which in that case, we could > have simply do the translation somewhere else and commit them here > when they're ready. The problem is that, even if we take the source > code somewhere else like a desktop text editor, it will still suffer > from the same problem (I'm yet to see a document/text editor that can > handle it correctly). Sometimes it doesn't matter (as in most web > pages which are usually generated automatically), sometimes it does > matter, when people have to directly deal with the tags. > > > I've built these initial translations you made, without any > > modification, see the results here: > > https://dbaio.bs2cloud.com.br/doc/fa01/fa_FA.UTF-8/books/handbook/ > > Although this initial build is based on just some test sentences, it > looks very promising. So, the compiled form seems to be already OK, > the main problem is with the source code. > > > Does "translating tags" mean replacing the tag name of with > > Parisian counterpart in RTL, or the whole tag including <> in RTL? > > I mean something like http://www.FreeBSD.org instead of > http://www.FreeBSD.org. This is the solution adopted by > similar projects, such as the Persian Wikipedia and the xepersian > package for LaTeX. I don't know if that's possible here, I guess it > requires fundamental modifications to the docproj infrastructures. I > could do the translation in the case those modifications to the > infrastructures are not a concern. > > > Could you show a typical HTML file in UTF-8 Persian? I would like to > > know what tags look like. > > Is this good enough? > https://kouhi.org/sample.html > > On Wed, Apr 1, 2020 at 1:13 AM Danilo G. Baio wrote: > > > > On Wed, Apr 01, 2020 at 03:52:04AM +0900, Hiroki Sato wrote: > > > "Danilo G. Baio" wrote > > > in <20200331170132.gyjlo7nel3cajidf at t480.local>: > > > > > > db> > Could you show a typical HTML file in UTF-8 Persian? I would like to > > > db> > know what tags look like. > > > db> > > > db> I would like to see some examples as well. > > > db> > > > db> Persian was already marked as RTL on Weblate. > > > > > > Yes, but it still needs direction attributes in the DocBook results > > > even if editors and input fields on the web browsers support RTL in > > > the user interface. We have options such as "RTL by default and > > > marking up the LTR parts" and vice versa. And RTL and LTR in the > > > same #PCDATA with no tag will not be rendered correctly. Probably we > > > need to take care of them in the XSLTs after checking what "natural > > > way" to write a marked-up document in HTML or XML is. > > > > > > Thank you both for the explanations. > > > > So, this will be an interesting issue to fix, let's check some real > > issues in our documents and the best way of fixing it. > > > > We will need your help Javad. > > > > Could I suggest starting with small documents, like > > articles/leap-seconds or articles/ipsec-must ? > > > > > > > > > > db> I've built these initial translations you made, without any > > > db> modification, see the results here: > > > db> https://dbaio.bs2cloud.com.br/doc/fa01/fa_FA.UTF-8/books/handbook/ > > > db> > > > db> If this is good, I can go forward and add a Jenkins job to build it regularly. > > > > > > The LANG_TERRITORY part must be fa_IR, not fa_FA. > > > > I'll fix that, thank you. > > > > -- > > Danilo G. Baio (dbaio) From dbaio at FreeBSD.org Wed Apr 1 11:52:33 2020 From: dbaio at FreeBSD.org (Danilo G. Baio) Date: Wed, 1 Apr 2020 08:52:20 -0300 Subject: Self-introduction: Javad Kouhi In-Reply-To: References: <20200331.124527.1078840241867193092.hrs@FreeBSD.org> <20200331170132.gyjlo7nel3cajidf@t480.local> <20200401.035204.1608271793023335727.hrs@FreeBSD.org> <20200331204305.gyq2mlh4mv7lykob@t480.local> Message-ID: <20200401115220.o7wnabejl2diojdg@t480.local> On Wed, Apr 01, 2020 at 03:26:48PM +0430, Javad Kouhi wrote: > I just finished articles_ipsec-must. Great, thank you! The output is already on our Jenkins: https://doc.fugbr.org/jenkins/weblate-fa_IR-5/fa_IR/articles/ipsec-must/ Besides those code blocks, what else needs to be LTR? Are there other issues? > On Wed, Apr 1, 2020 at 8:47 AM Javad Kouhi wrote: > > > > Hello and thank you for the replies. > > > > > Could I suggest starting with small documents, like > > > articles/leap-seconds or articles/ipsec-must ? > > > > I'll prepare a small article, so we would have something to start > > with, will let you know when I'm finished. > > > > > The UI is doing something because the string is saved differently in the > > > repository: > > > https://people.freebsd.org/~dbaio/weblate/2020-03-31-093415_747x699_scrot.png > > > > The UI is showing the code in RTL format. In this form, the Persian > > text is shown correctly, but the tags are not. On the other hand, in > > this screenshot: > > > > https://people.freebsd.org/~dbaio/weblate/2020-03-31-093415_747x699_scrot.png > > > > The code is shown in LTR format. In this form, the tags are shown > > correctly, but the Persian text looks messy. > > > > If one is shown correctly, the other would look messy. They can't be > > shown correctly at the same time. This is a universal problem with RTL > > languages and is not specific to Weblate, which in that case, we could > > have simply do the translation somewhere else and commit them here > > when they're ready. The problem is that, even if we take the source > > code somewhere else like a desktop text editor, it will still suffer > > from the same problem (I'm yet to see a document/text editor that can > > handle it correctly). Sometimes it doesn't matter (as in most web > > pages which are usually generated automatically), sometimes it does > > matter, when people have to directly deal with the tags. > > > > > I've built these initial translations you made, without any > > > modification, see the results here: > > > https://dbaio.bs2cloud.com.br/doc/fa01/fa_FA.UTF-8/books/handbook/ > > > > Although this initial build is based on just some test sentences, it > > looks very promising. So, the compiled form seems to be already OK, > > the main problem is with the source code. > > > > > Does "translating tags" mean replacing the tag name of with > > > Parisian counterpart in RTL, or the whole tag including <> in RTL? > > > > I mean something like http://www.FreeBSD.org instead of > > http://www.FreeBSD.org. This is the solution adopted by > > similar projects, such as the Persian Wikipedia and the xepersian > > package for LaTeX. I don't know if that's possible here, I guess it > > requires fundamental modifications to the docproj infrastructures. I > > could do the translation in the case those modifications to the > > infrastructures are not a concern. > > > > > Could you show a typical HTML file in UTF-8 Persian? I would like to > > > know what tags look like. > > > > Is this good enough? > > https://kouhi.org/sample.html > > > > On Wed, Apr 1, 2020 at 1:13 AM Danilo G. Baio wrote: > > > > > > On Wed, Apr 01, 2020 at 03:52:04AM +0900, Hiroki Sato wrote: > > > > "Danilo G. Baio" wrote > > > > in <20200331170132.gyjlo7nel3cajidf at t480.local>: > > > > > > > > db> > Could you show a typical HTML file in UTF-8 Persian? I would like to > > > > db> > know what tags look like. > > > > db> > > > > db> I would like to see some examples as well. > > > > db> > > > > db> Persian was already marked as RTL on Weblate. > > > > > > > > Yes, but it still needs direction attributes in the DocBook results > > > > even if editors and input fields on the web browsers support RTL in > > > > the user interface. We have options such as "RTL by default and > > > > marking up the LTR parts" and vice versa. And RTL and LTR in the > > > > same #PCDATA with no tag will not be rendered correctly. Probably we > > > > need to take care of them in the XSLTs after checking what "natural > > > > way" to write a marked-up document in HTML or XML is. > > > > > > > > > Thank you both for the explanations. > > > > > > So, this will be an interesting issue to fix, let's check some real > > > issues in our documents and the best way of fixing it. > > > > > > We will need your help Javad. > > > > > > Could I suggest starting with small documents, like > > > articles/leap-seconds or articles/ipsec-must ? > > > > > > > > > > > > > > db> I've built these initial translations you made, without any > > > > db> modification, see the results here: > > > > db> https://dbaio.bs2cloud.com.br/doc/fa01/fa_FA.UTF-8/books/handbook/ > > > > db> > > > > db> If this is good, I can go forward and add a Jenkins job to build it regularly. > > > > > > > > The LANG_TERRITORY part must be fa_IR, not fa_FA. > > > > > > I'll fix that, thank you. -- Danilo G. Baio (dbaio) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From javad.kouhi at gmail.com Fri Apr 3 19:09:51 2020 From: javad.kouhi at gmail.com (Javad Kouhi) Date: Fri, 3 Apr 2020 23:30:27 +0430 Subject: Self-introduction: Javad Kouhi In-Reply-To: <20200401115220.o7wnabejl2diojdg@t480.local> References: <20200331.124527.1078840241867193092.hrs@FreeBSD.org> <20200331170132.gyjlo7nel3cajidf@t480.local> <20200401.035204.1608271793023335727.hrs@FreeBSD.org> <20200331204305.gyq2mlh4mv7lykob@t480.local> <20200401115220.o7wnabejl2diojdg@t480.local> Message-ID: > Besides those code blocks, what else needs to be LTR? Are there other > issues? Sorry for the late reply. Everything else is in order, thank you very much! On Wed, Apr 1, 2020 at 4:22 PM Danilo G. Baio wrote: > > On Wed, Apr 01, 2020 at 03:26:48PM +0430, Javad Kouhi wrote: > > I just finished articles_ipsec-must. > > Great, thank you! > > The output is already on our Jenkins: > https://doc.fugbr.org/jenkins/weblate-fa_IR-5/fa_IR/articles/ipsec-must/ > > Besides those code blocks, what else needs to be LTR? Are there other > issues? > > > > On Wed, Apr 1, 2020 at 8:47 AM Javad Kouhi wrote: > > > > > > Hello and thank you for the replies. > > > > > > > Could I suggest starting with small documents, like > > > > articles/leap-seconds or articles/ipsec-must ? > > > > > > I'll prepare a small article, so we would have something to start > > > with, will let you know when I'm finished. > > > > > > > The UI is doing something because the string is saved differently in the > > > > repository: > > > > https://people.freebsd.org/~dbaio/weblate/2020-03-31-093415_747x699_scrot.png > > > > > > The UI is showing the code in RTL format. In this form, the Persian > > > text is shown correctly, but the tags are not. On the other hand, in > > > this screenshot: > > > > > > https://people.freebsd.org/~dbaio/weblate/2020-03-31-093415_747x699_scrot.png > > > > > > The code is shown in LTR format. In this form, the tags are shown > > > correctly, but the Persian text looks messy. > > > > > > If one is shown correctly, the other would look messy. They can't be > > > shown correctly at the same time. This is a universal problem with RTL > > > languages and is not specific to Weblate, which in that case, we could > > > have simply do the translation somewhere else and commit them here > > > when they're ready. The problem is that, even if we take the source > > > code somewhere else like a desktop text editor, it will still suffer > > > from the same problem (I'm yet to see a document/text editor that can > > > handle it correctly). Sometimes it doesn't matter (as in most web > > > pages which are usually generated automatically), sometimes it does > > > matter, when people have to directly deal with the tags. > > > > > > > I've built these initial translations you made, without any > > > > modification, see the results here: > > > > https://dbaio.bs2cloud.com.br/doc/fa01/fa_FA.UTF-8/books/handbook/ > > > > > > Although this initial build is based on just some test sentences, it > > > looks very promising. So, the compiled form seems to be already OK, > > > the main problem is with the source code. > > > > > > > Does "translating tags" mean replacing the tag name of with > > > > Parisian counterpart in RTL, or the whole tag including <> in RTL? > > > > > > I mean something like http://www.FreeBSD.org instead of > > > http://www.FreeBSD.org. This is the solution adopted by > > > similar projects, such as the Persian Wikipedia and the xepersian > > > package for LaTeX. I don't know if that's possible here, I guess it > > > requires fundamental modifications to the docproj infrastructures. I > > > could do the translation in the case those modifications to the > > > infrastructures are not a concern. > > > > > > > Could you show a typical HTML file in UTF-8 Persian? I would like to > > > > know what tags look like. > > > > > > Is this good enough? > > > https://kouhi.org/sample.html > > > > > > On Wed, Apr 1, 2020 at 1:13 AM Danilo G. Baio wrote: > > > > > > > > On Wed, Apr 01, 2020 at 03:52:04AM +0900, Hiroki Sato wrote: > > > > > "Danilo G. Baio" wrote > > > > > in <20200331170132.gyjlo7nel3cajidf at t480.local>: > > > > > > > > > > db> > Could you show a typical HTML file in UTF-8 Persian? I would like to > > > > > db> > know what tags look like. > > > > > db> > > > > > db> I would like to see some examples as well. > > > > > db> > > > > > db> Persian was already marked as RTL on Weblate. > > > > > > > > > > Yes, but it still needs direction attributes in the DocBook results > > > > > even if editors and input fields on the web browsers support RTL in > > > > > the user interface. We have options such as "RTL by default and > > > > > marking up the LTR parts" and vice versa. And RTL and LTR in the > > > > > same #PCDATA with no tag will not be rendered correctly. Probably we > > > > > need to take care of them in the XSLTs after checking what "natural > > > > > way" to write a marked-up document in HTML or XML is. > > > > > > > > > > > > Thank you both for the explanations. > > > > > > > > So, this will be an interesting issue to fix, let's check some real > > > > issues in our documents and the best way of fixing it. > > > > > > > > We will need your help Javad. > > > > > > > > Could I suggest starting with small documents, like > > > > articles/leap-seconds or articles/ipsec-must ? > > > > > > > > > > > > > > > > > > db> I've built these initial translations you made, without any > > > > > db> modification, see the results here: > > > > > db> https://dbaio.bs2cloud.com.br/doc/fa01/fa_FA.UTF-8/books/handbook/ > > > > > db> > > > > > db> If this is good, I can go forward and add a Jenkins job to build it regularly. > > > > > > > > > > The LANG_TERRITORY part must be fa_IR, not fa_FA. > > > > > > > > I'll fix that, thank you. > > -- > Danilo G. Baio (dbaio) From orders at referee-equipment.co.uk Sat Apr 4 15:47:15 2020 From: orders at referee-equipment.co.uk (A&H International) Date: Sat, 4 Apr 2020 15:46:46 +0000 Subject: Your A&H International account has been created! Message-ID: <5cac0e597a98bcec12940afe019fb270@referee-equipment.co.uk> From weblate at fugspbr.org Fri Apr 10 12:07:40 2020 From: weblate at fugspbr.org (weblate at fugspbr.org) Date: Fri, 10 Apr 2020 07:02:48 -0500 (CDT) Subject: [Weblate Jenkins] Build failed weblate-zh_CN #136 Message-ID: <32289901.5.1586520169728.JavaMail.jenkins@raven.fugbr.org> Check console output at http://doc.fugbr.org:8180/jenkins/job/weblate-zh_CN/136/ From weblate at fugspbr.org Fri Apr 10 13:18:09 2020 From: weblate at fugspbr.org (weblate at fugspbr.org) Date: Fri, 10 Apr 2020 08:13:17 -0500 (CDT) Subject: [Weblate Jenkins] Build failed weblate-zh_CN #137 In-Reply-To: <32289901.5.1586520169728.JavaMail.jenkins@raven.fugbr.org> References: <32289901.5.1586520169728.JavaMail.jenkins@raven.fugbr.org> Message-ID: <1301938355.7.1586524398294.JavaMail.jenkins@raven.fugbr.org> Check console output at http://doc.fugbr.org:8180/jenkins/job/weblate-zh_CN/137/ From weblate at fugspbr.org Fri Apr 10 17:33:04 2020 From: weblate at fugspbr.org (weblate at fugspbr.org) Date: Fri, 10 Apr 2020 12:28:12 -0500 (CDT) Subject: [Weblate Jenkins] weblate-zh_CN back to normal In-Reply-To: <1301938355.7.1586524398294.JavaMail.jenkins@raven.fugbr.org> References: <1301938355.7.1586524398294.JavaMail.jenkins@raven.fugbr.org> Message-ID: <1339913005.9.1586539692708.JavaMail.jenkins@raven.fugbr.org> Check console output at http://doc.fugbr.org:8180/jenkins/job/weblate-zh_CN/138/ From weblate at fugspbr.org Sun Apr 12 07:58:17 2020 From: weblate at fugspbr.org (weblate at fugspbr.org) Date: Sun, 12 Apr 2020 02:53:20 -0500 (CDT) Subject: [Weblate Jenkins] Build failed weblate-zh_CN #141 Message-ID: <903738260.1.1586678001224.JavaMail.jenkins@raven.fugbr.org> Check console output at http://doc.fugbr.org:8180/jenkins/job/weblate-zh_CN/141/ From weblate at fugspbr.org Mon Apr 13 09:58:52 2020 From: weblate at fugspbr.org (weblate at fugspbr.org) Date: Mon, 13 Apr 2020 04:53:52 -0500 (CDT) Subject: [Weblate Jenkins] weblate-zh_CN back to normal In-Reply-To: <903738260.1.1586678001224.JavaMail.jenkins@raven.fugbr.org> References: <903738260.1.1586678001224.JavaMail.jenkins@raven.fugbr.org> Message-ID: <1146849702.3.1586771633579.JavaMail.jenkins@raven.fugbr.org> Check console output at http://doc.fugbr.org:8180/jenkins/job/weblate-zh_CN/142/ From kfv at irbug.org Tue Apr 14 15:29:48 2020 From: kfv at irbug.org (Faraz Vahedi) Date: Tue, 14 Apr 2020 15:29:37 +0000 Subject: Self-Introduction: Faraz Vahedi - Farsi/Persian Message-ID: <20200414152937.fhdzvlmllwmgkr3e@kai> Name: Faraz Vahedi Location: Teheran, Iran Login: kfv at irbug.org Language: Farsi/Persian Profession or student status: System Architect and Political Science student About: Aspiring FreeBSD src developer and founder/organiser at IRBUG Website: kfv.io Note: We have just begun Farsi/Persian translation of Handbooks at IRBUG and when finished, we will surely go for other documents and the website itself. I would like to announce and see if we can use Weblate and also seek guidance if there is anything we should know before submitting a diff. It would also be great if we can list Farsi/Persian in https://www.freebsd.org/docproj/translations.html so that if anyone likes to cooperate can easily contact and join the team to speed up the translation. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From carlavilla at mailbox.org Tue Apr 14 15:33:34 2020 From: carlavilla at mailbox.org (Sergio Carlavilla) Date: Tue, 14 Apr 2020 17:33:18 +0200 Subject: Self-Introduction: Faraz Vahedi - Farsi/Persian In-Reply-To: <20200414152937.fhdzvlmllwmgkr3e@kai> References: <20200414152937.fhdzvlmllwmgkr3e@kai> Message-ID: <661E6030-3800-47E8-9E3D-3860C6FFB493@mailbox.org> Hi, I?ll add your contact to ? https://www.freebsd.org/docproj/translations.html? Can you pass me a website/mailing list and/or contact? Bye and thanks for your work. > On 14 Apr 2020, at 17:30, Faraz Vahedi via freebsd-translators wrote: > > ?Name: Faraz Vahedi > Location: Teheran, Iran > Login: kfv at irbug.org > Language: Farsi/Persian > Profession or student status: System Architect and Political Science student > About: Aspiring FreeBSD src developer and founder/organiser at IRBUG > Website: kfv.io > Note: We have just begun Farsi/Persian translation of Handbooks at IRBUG and when finished, we will surely go for other documents and the website itself. I would like to announce and see if we can use Weblate and also seek guidance if there is anything we should know before submitting a diff. It would also be great if we can list Farsi/Persian in https://www.freebsd.org/docproj/translations.html so that if anyone likes to cooperate can easily contact and join the team to speed up the translation. From kfv at irbug.org Tue Apr 14 17:33:11 2020 From: kfv at irbug.org (K Faraz Vahedi) Date: Tue, 14 Apr 2020 22:03:05 +0430 Subject: Self-Introduction: Faraz Vahedi - Farsi/Persian In-Reply-To: <661E6030-3800-47E8-9E3D-3860C6FFB493@mailbox.org> References: <20200414152937.fhdzvlmllwmgkr3e@kai> <661E6030-3800-47E8-9E3D-3860C6FFB493@mailbox.org> Message-ID: Hello Sergio, I mistakenly only replied to you and forgot to group-reply the message so freebsd-translators at freebsd.org was not CC'd and therefore I resend my response: Thank you very much. For contact, my email address could be fine: kfv at irbug.org. And for the website, I think the main page of our user group is good for now, https://www.irbug.org. I will notify you if we anytime want to add any further information or make any change. Cheers, Faraz From dbaio at FreeBSD.org Wed Apr 15 00:10:15 2020 From: dbaio at FreeBSD.org (Danilo G. Baio) Date: Tue, 14 Apr 2020 21:10:10 -0300 Subject: Self-Introduction: Faraz Vahedi - Farsi/Persian In-Reply-To: <20200414152937.fhdzvlmllwmgkr3e@kai> References: <20200414152937.fhdzvlmllwmgkr3e@kai> Message-ID: <20200415001010.dpjhwpf7o2xx4qpm@t480.local> On Tue, Apr 14, 2020 at 03:29:37PM +0000, Faraz Vahedi via freebsd-translators wrote: > Name: Faraz Vahedi > Location: Teheran, Iran > Login: kfv at irbug.org > Language: Farsi/Persian > Profession or student status: System Architect and Political Science student > About: Aspiring FreeBSD src developer and founder/organiser at IRBUG > Website: kfv.io > Note: We have just begun Farsi/Persian translation of Handbooks at > IRBUG and when finished, we will surely go for other documents and the > website itself. I would like to announce and see if we can use Weblate > and also seek guidance if there is anything we should know before > submitting a diff. Welcome. I've added your username to the fa_Persian team on our Weblate. if you are translating through a PO file, you could submit it to the Weblate directly. https://wiki.freebsd.org/DocTranslationOnWeblate#Translating_offline And if you want, you can use it to your ongoing translations, we already have a Jenkins building all translations daily, it's very helpful. We still need to fix some issues about RTL and LTR, but we already have this POC which Javad Kouhi translated. https://dbaio.bs2cloud.com.br/doc/fa04/fa_IR.UTF-8/articles/ipsec-must/article.html -- Danilo G. Baio (dbaio) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From kfv at irbug.org Wed Apr 15 01:18:43 2020 From: kfv at irbug.org (Faraz Vahedi) Date: Wed, 15 Apr 2020 01:18:36 +0000 Subject: Self-Introduction: Faraz Vahedi - Farsi/Persian In-Reply-To: <20200415001010.dpjhwpf7o2xx4qpm@t480.local> References: <20200414152937.fhdzvlmllwmgkr3e@kai> <20200415001010.dpjhwpf7o2xx4qpm@t480.local> Message-ID: <20200415011836.y66rvko2qrd3usnw@kai> On Tue, Apr 14, 2020 at 09:10:10PM -0300, Danilo G. Baio wrote: > Welcome. > > I've added your username to the fa_Persian team on our Weblate. > > if you are translating through a PO file, you could submit it to the > Weblate directly. > https://wiki.freebsd.org/DocTranslationOnWeblate#Translating_offline > > And if you want, you can use it to your ongoing translations, we already > have a Jenkins building all translations daily, it's very helpful. > > We still need to fix some issues about RTL and LTR, but we already have > this POC which Javad Kouhi translated. > https://dbaio.bs2cloud.com.br/doc/fa04/fa_IR.UTF-8/articles/ipsec-must/article.html > > -- > Danilo G. Baio (dbaio) Hello Danilo, Amazing, thank you very much. Yes, I saw his great help in Weblate and it seems that fortunately, RTL and LTR issues are about to be fixed. In the meanwhile, I will tell our volunteer translators to send their self-introduction email and register to the Weblate so as to begin the work. Cheers, Faraz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From somayeh at irbug.org Fri Apr 17 11:18:58 2020 From: somayeh at irbug.org (Somayeh Kdarami) Date: Fri, 17 Apr 2020 15:48:49 +0430 Subject: Introduction Message-ID: <493YVm6fKrz26B0@mail.irbug.org> Name: Somayeh Karami Location: Teheran, Iran Login: somayeh at irbug.org Language: Farsi/Persian Profession or student status: Programmer ,Project Manager About: FreeBSD enthusiastic and a member of IRBUG Note: I am a Software programmer and project manager, recently I?ve joined IRBUG and I am trying to learn FreeBSD and also gain a better understanding of the inner working of an OS. IRBUG aims to translate the Handbooks and also documents and website of FreeBSD to Farsi/Persian. As a member of the team I like to contribute to the translations. We want to use Weblate for translation, So it would be very helpful if there is anything I should know before submitting a diff. Best Regards Somayeh Karami Sent from Mail for Windows 10 From dbaio at FreeBSD.org Fri Apr 17 11:58:12 2020 From: dbaio at FreeBSD.org (Danilo G. Baio) Date: Fri, 17 Apr 2020 08:58:07 -0300 Subject: Introduction In-Reply-To: <493YVm6fKrz26B0@mail.irbug.org> References: <493YVm6fKrz26B0@mail.irbug.org> Message-ID: <20200417115807.t7ka7m5zaln5ee2q@t480.local> On Fri, Apr 17, 2020 at 03:48:49PM +0430, Somayeh Kdarami via freebsd-translators wrote: > > Name: Somayeh Karami > Location: Teheran, Iran > Login: somayeh at irbug.org > Language: Farsi/Persian > Profession or student status: Programmer ,Project Manager > About: FreeBSD enthusiastic and a member of IRBUG > > Note: I am a Software programmer and project manager, recently I?ve > joined IRBUG and I am trying to learn FreeBSD and also gain a better > understanding of the inner working of an OS. IRBUG aims to translate > the Handbooks and also documents and website of FreeBSD to > Farsi/Persian. As a member of the team I like to contribute to the > translations. We want to use Weblate for translation, So it would be > very helpful if there is anything I should know before submitting a > diff. Hello and be welcome. I've added your username to the fa_Persian team on our Weblate. Regards. -- Danilo G. Baio (dbaio) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From qps at irbug.org Sat Apr 18 12:44:10 2020 From: qps at irbug.org (Parsa Samet) Date: Sat, 18 Apr 2020 17:13:52 +0430 Subject: Self-Introduction: Parsa Samet, Persian Message-ID: <5AF0F61B-320D-420E-9577-093618C074CA@irbug.org> Name: Parsa Samet Location: Teheran, Iran Login: qps (qps at irbug.org ) Language: Persian Profession or student status: Political Science Student and System Administrator About: I?m a system administrator and a FreeBSD enthusiast. As a member of Iran BSD User Group (IRBUG) I?d like to contribute to FreeBSD project in any possible way and also advocate the project in my own country by making the official documents accessible in Persian language. From dbaio at FreeBSD.org Sat Apr 18 17:50:00 2020 From: dbaio at FreeBSD.org (Danilo G. Baio) Date: Sat, 18 Apr 2020 14:49:54 -0300 Subject: Self-Introduction: Parsa Samet, Persian In-Reply-To: <5AF0F61B-320D-420E-9577-093618C074CA@irbug.org> References: <5AF0F61B-320D-420E-9577-093618C074CA@irbug.org> Message-ID: <20200418174954.5kfd3vdz3gsh7x74@t480.local> On Sat, Apr 18, 2020 at 05:13:52PM +0430, Parsa Samet via freebsd-translators wrote: > Name: Parsa Samet > Location: Teheran, Iran > Login: qps (qps at irbug.org ) > Language: Persian > Profession or student status: Political Science Student and System Administrator > About: I?m a system administrator and a FreeBSD enthusiast. As a > member of Iran BSD User Group (IRBUG) I?d like to contribute to > FreeBSD project in any possible way and also advocate the project in > my own country by making the official documents accessible in Persian > language. Hello. Be welcome. I've added your username to the fa_Persian team on our Weblate. -- Danilo G. Baio (dbaio) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From dbaio at FreeBSD.org Sat Apr 18 20:38:32 2020 From: dbaio at FreeBSD.org (Danilo G. Baio) Date: Sat, 18 Apr 2020 17:38:28 -0300 Subject: [Weblate] Update source files (.pot) from r53979 to r54061 - translate-dev Message-ID: <20200418203828.pbuglbayyzi7v3cw@t480.local> Sync with r54061, latest commit in the tree. Last update was r53979 (2020-03-14). Documents that has changed: articles/ - committers-guide: https://github.com/doc-br/translate/commit/bc1e2c26cddb4f8f793512c19a7a0189a3f2bd2e - contributors: https://github.com/doc-br/translate/commit/907f5debeaab51e19ca89e6e224e50476685c3fc - freebsd-releng: https://github.com/doc-br/translate/commit/1512b52cfd896c3df047a851d7976737e03b77af - releng: https://github.com/doc-br/translate/commit/a048d1154dc4016944b0824e45127407c549dac0 books/ - faq: https://github.com/doc-br/translate/commit/2506b0095dc9e75b889dbb6836663f8359b8946f - books/fdp-primer: https://github.com/doc-br/translate/commit/9329c82a33ec74299a2f8c2291e05630230147bc - handbook: https://github.com/doc-br/translate/commit/1e260e99657a27608b2d6487124ae02ea1cb5e8e - porters-handbook: https://github.com/doc-br/translate/commit/38d95737b6ef8e644c57fd6784eb828788399239 Others documents were changed (minimal changes) on Weblate but they weren't changed upstream, example: https://github.com/doc-br/translate/commit/6801e08162dbc7434524d7f26770021bb40f91a5 What happens is that affected/changed strings are marked as fuzzy, and an action is necessary on those strings. if it has a translation, just uncheck the [Needs editing] checkbox and save it, otherwise you don't need to do anything. Still don't know if this a Weblate or Itstool issue, but we will keep an eye in the following updates. This is the list of affected documents and languages: articles/cups (es_ES and pt_BR) articles/serial-uart (pt_BR) articles/contributing (es_ES and pt_BR) articles/explaining-bsd (es_ES and pt_BR) articles/freebsd-questions (es_ES and pt_BR) articles/vinum (pt_BR) articles/vm-design (pt_BR) articles/freebsd-update-server (es_ES and pt_BR) articles/gjournal-desktop (es_ES and pt_BR) articles/linux-emulation (es_ES and pt_BR) articles/linux-users (es_ES and pt_BR) books/arch-handbook (pt_BR and zh_CN) books/dev-model (pt_BR) books/developers-handbook (pt_BR) books/fdp-primer (pt_BR) There is a pending Weblate update, but we will wait for version 4.0.2 before update our instance, which is running on version 3.11.3. https://docs.weblate.org/en/latest/changes.html Maybe next week we will update it. https://translate-dev.freebsd.org/ -- Danilo G. Baio (dbaio) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: