Re: [Inkscape-translator] Inkscape-translator Digest, Vol 66, Issue 7
by aidjai
Hello everybody,
Yes I could help on french translation.
Best regards,
alain
Le 20/01/2015 17:28, inkscape-translator-request(a)lists.sourceforge.net a
écrit :
> Send Inkscape-translator mailing list submissions to
> inkscape-translator(a)lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/inkscape-translator
> or, via email, send a message with subject or body 'help' to
> inkscape-translator-request(a)lists.sourceforge.net
>
> You can reach the person managing the list at
> inkscape-translator-owner(a)lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Inkscape-translator digest..."
>
>
> Today's Topics:
>
> 1. Re: Website translation updates (Maren Hachmann)
> 2. Re: Website translation updates (Victor Westmann)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 20 Jan 2015 17:24:29 +0100
> From: Maren Hachmann <maren@...325...>
> Subject: Re: [Inkscape-translator] Website translation updates
> To: translators <inkscape-translator(a)lists.sourceforge.net>
> Message-ID: <54BE813D.1050208@...325...>
> Content-Type: text/plain; charset=utf-8
>
> Hi Victor,
>
> the news translation is really the easiest way to translate something on
> the website, as it doesn't have all those plugins and stuff. It would
> have been a really good beginner's job ;)
>
> - The updated FAQ is currently not yet on the real website, but you can
> start translating to pt-br at staging.inkscape.org instead (choose any
> language you like for filling it in), and copy over later (there are
> only very few link plugins, so copying will be possible without very
> much hassle). Much of it is already translated, as the new FAQ also
> contains parts from the old FAQ, and Duarte has already invested a lot
> of work into translating the old FAQ.
>
> The English new FAQ is here:
> http://staging.inkscape.org/en/brynns-user-faq/ .
> Duarte's translation of the old FAQ is here:
> https://inkscape.org/pt/aprender/perguntas-frequentes
>
> Always make sure that you do *not edit the English FAQ* by looking at
> the url! (In fact, please don't edit any page starting with 'brynn...'
> in English.)
>
> Also make sure you have a backup of the source from your translation of
> the FAQ on your own computer, as on staging, people practice, and they
> may accidentally change your work.
>
> You will also need an account on staging.inkscape.org for this, and some
> permissions. I need to know your username there so I can grant you
> permissions on staging.
>
> - The official tutorials for Inkscape are translated in the inkscape
> trunk, ask Nicolas Dufour (jazzynico) about this (I think you have
> already contacted him earlier). For the next release, though, this may
> be too late. Bryce Harrington wrote something about next week...
>
> - The fixed parts of the site can be translated from the files for the
> website at launchpad. I will append a current po file to this message, BUT:
> - the file currently contains too many entries (for many of those,
> translations do already exist, but are not automatically added to the file)
> - the contents of the file is still changing heavily
> - there is a better system for translating those on the way, but not yet
> fully implemented.
>
> So you *can* work on it, but:
> - we may not need everything, because some of it already is translated
> - it will still change
> - there will be a better way for doing this soon
>
> All in all, I think Duarte's suggestion of starting with the news (after
> you have practiced on staging) is really a very good idea ;)
>
> Regards,
> Maren
>
> PS: I had to remove the attachment, because the mailing-list refused to
> accept it. Contact me directly, if you want the .po file ;)
>
>
>
>
> Am 20.01.2015 um 16:39 schrieb Victor Westmann:
>> How can I start translating fixed parts of the site?
>>
>> Not very much interested in the news right now. But in the FAQ and
>> maybe tutorials. :)
>>
>> Cheers from Brazil.
>>
>>
>>
>> --Victor Westmann
>>
>> 2015-01-19 23:55 GMT-02:00 Duarte Ramos <duarte.framos@...5...
>> <mailto:duarte.framos@...5...>>:
>>
>> Thank you very much for the explanation, Portuguese Downloads page
>> updated. Also fixed all the links and reconnected them back to the CMS
>> plugin so it can be correctly copied as base again.
>>
>> On a side note, if Pablo, Victor are full of energy and want to
>> help out
>> lets not waste human power. :)
>> While the site update doesn't go live and they can't start translating
>> the BR version maybe they can help with the PT one. If they are
>> available they could start out with the "news" section and help
>> translate the latest 2014 and 2015 news since they are generally
>> smaller
>> content and easy to start with . I was saving them for last but it's
>> probably gonna take me a while o get there and that way when the
>> Brazilian site goes live those can be ported there and no effort is
>> wasted. Eventually after that happens I'll then update the PT news if
>> needed.
>>
>> Thanks again, Duarte
>>
>>
>> On 20-01-2015 01:32, Maren Hachmann wrote:
>> > Hi Duarte,
>> >
>> > plugin links cannot be copied directly by going to the source
>> and using
>> > Ctrl+V and then pasting them.
>> >
>> > They have unique ids and can't be used on different pages,
>> especially if
>> > their contents changes.
>> >
>> > You may want to translate the link's text ;) - but if it is the same
>> > object with the same id in the database, you would also change the
>> > original link's text, this is prevented by cleaning them out in
>> > published pages.
>> >
>> > So, you need to copy the text from English by copying from the page
>> > directly (not from source, but from the 'real' page) into the
>> > non-source-mode editor window. This will magically insert the
>> contents
>> > in a formatted way.
>> >
>> > Then, if you want to turn the link into a plugin again (which may be
>> > useful if other people want to copy your page completely as a
>> start for
>> > their own translation, because in that case, the plugins are
>> *really*
>> > duplicated, with their new, own id):
>> >
>> > 1.) right-click on the link in the editor to select
>> > 2.) choose 'edit' to be able to copy the target
>> > 3.) Select CMS plugin -> Link
>> > 4.) add http:// or https:// manually, paste target behind
>> > 5.) Save
>> >
>> > Hope this helps, please ask back if my explanation wasn't clear
>> enough.
>> >
>> > Regards,
>> > Maren
>> >
>> > Am 20.01.2015 um 01:53 schrieb Duarte Ramos:
>> >> No problem I misread too, I am currently using the pre release 3, I
>> >> must have misread and thought it was the official 0.91.
>> >>
>> >> I still can't copy the plugins but I have got another weird
>> issue. I
>> >> just updated the downloads page with the part about pre4. Manually
>> >> copied the updated text from the from the English page and
>> translated
>> >> all strings, but whenever I hit publish the text with links simply
>> >> vanishes. If I edit the page again translated text displays fine
>> >> again, but on the published version the links are removed.
>> >>
>> >
>>
>>
>>
> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in
>> Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely
>> compliant.
>> http://p.sf.net/sfu/gigenet
>> _______________________________________________
>> Inkscape-translator mailing list
>> Inkscape-translator(a)lists.sourceforge.net
>> <mailto:Inkscape-translator@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/inkscape-translator
>>
>>
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 20 Jan 2015 14:27:44 -0200
> From: Victor Westmann <victor.westmann@...5...>
> Subject: Re: [Inkscape-translator] Website translation updates
> To: Maren Hachmann <maren@...325...>
> Cc: translators <inkscape-translator(a)lists.sourceforge.net>
> Message-ID:
> <CAPOH7=aj8LcMLKBckUSGZM7G-NuFuvemzPTaLSU_j_KOx-10FQ@...6...>
> Content-Type: text/plain; charset="utf-8"
>
> Maren,
>
> I have bought the full version of PoEdit to help the developer of the app.
> Will it help me on this work then? If the file I`ll have to work will be a
> po file? :)
>
>
>
> --Victor Westmann
>
> 2015-01-20 14:24 GMT-02:00 Maren Hachmann <maren@...325...>:
>
>> Hi Victor,
>>
>> the news translation is really the easiest way to translate something on
>> the website, as it doesn't have all those plugins and stuff. It would
>> have been a really good beginner's job ;)
>>
>> - The updated FAQ is currently not yet on the real website, but you can
>> start translating to pt-br at staging.inkscape.org instead (choose any
>> language you like for filling it in), and copy over later (there are
>> only very few link plugins, so copying will be possible without very
>> much hassle). Much of it is already translated, as the new FAQ also
>> contains parts from the old FAQ, and Duarte has already invested a lot
>> of work into translating the old FAQ.
>>
>> The English new FAQ is here:
>> http://staging.inkscape.org/en/brynns-user-faq/ .
>> Duarte's translation of the old FAQ is here:
>> https://inkscape.org/pt/aprender/perguntas-frequentes
>>
>> Always make sure that you do *not edit the English FAQ* by looking at
>> the url! (In fact, please don't edit any page starting with 'brynn...'
>> in English.)
>>
>> Also make sure you have a backup of the source from your translation of
>> the FAQ on your own computer, as on staging, people practice, and they
>> may accidentally change your work.
>>
>> You will also need an account on staging.inkscape.org for this, and some
>> permissions. I need to know your username there so I can grant you
>> permissions on staging.
>>
>> - The official tutorials for Inkscape are translated in the inkscape
>> trunk, ask Nicolas Dufour (jazzynico) about this (I think you have
>> already contacted him earlier). For the next release, though, this may
>> be too late. Bryce Harrington wrote something about next week...
>>
>> - The fixed parts of the site can be translated from the files for the
>> website at launchpad. I will append a current po file to this message, BUT:
>> - the file currently contains too many entries (for many of those,
>> translations do already exist, but are not automatically added to the file)
>> - the contents of the file is still changing heavily
>> - there is a better system for translating those on the way, but not yet
>> fully implemented.
>>
>> So you *can* work on it, but:
>> - we may not need everything, because some of it already is translated
>> - it will still change
>> - there will be a better way for doing this soon
>>
>> All in all, I think Duarte's suggestion of starting with the news (after
>> you have practiced on staging) is really a very good idea ;)
>>
>> Regards,
>> Maren
>>
>> PS: I had to remove the attachment, because the mailing-list refused to
>> accept it. Contact me directly, if you want the .po file ;)
>>
>>
>>
>>
>> Am 20.01.2015 um 16:39 schrieb Victor Westmann:
>>> How can I start translating fixed parts of the site?
>>>
>>> Not very much interested in the news right now. But in the FAQ and
>>> maybe tutorials. :)
>>>
>>> Cheers from Brazil.
>>>
>>>
>>>
>>> --Victor Westmann
>>>
>>> 2015-01-19 23:55 GMT-02:00 Duarte Ramos <duarte.framos@...5...
>>> <mailto:duarte.framos@...5...>>:
>>>
>>> Thank you very much for the explanation, Portuguese Downloads page
>>> updated. Also fixed all the links and reconnected them back to the
>> CMS
>>> plugin so it can be correctly copied as base again.
>>>
>>> On a side note, if Pablo, Victor are full of energy and want to
>>> help out
>>> lets not waste human power. :)
>>> While the site update doesn't go live and they can't start
>> translating
>>> the BR version maybe they can help with the PT one. If they are
>>> available they could start out with the "news" section and help
>>> translate the latest 2014 and 2015 news since they are generally
>>> smaller
>>> content and easy to start with . I was saving them for last but it's
>>> probably gonna take me a while o get there and that way when the
>>> Brazilian site goes live those can be ported there and no effort is
>>> wasted. Eventually after that happens I'll then update the PT news if
>>> needed.
>>>
>>> Thanks again, Duarte
>>>
>>>
>>> On 20-01-2015 01:32, Maren Hachmann wrote:
>>> > Hi Duarte,
>>> >
>>> > plugin links cannot be copied directly by going to the source
>>> and using
>>> > Ctrl+V and then pasting them.
>>> >
>>> > They have unique ids and can't be used on different pages,
>>> especially if
>>> > their contents changes.
>>> >
>>> > You may want to translate the link's text ;) - but if it is the
>> same
>>> > object with the same id in the database, you would also change the
>>> > original link's text, this is prevented by cleaning them out in
>>> > published pages.
>>> >
>>> > So, you need to copy the text from English by copying from the page
>>> > directly (not from source, but from the 'real' page) into the
>>> > non-source-mode editor window. This will magically insert the
>>> contents
>>> > in a formatted way.
>>> >
>>> > Then, if you want to turn the link into a plugin again (which may
>> be
>>> > useful if other people want to copy your page completely as a
>>> start for
>>> > their own translation, because in that case, the plugins are
>>> *really*
>>> > duplicated, with their new, own id):
>>> >
>>> > 1.) right-click on the link in the editor to select
>>> > 2.) choose 'edit' to be able to copy the target
>>> > 3.) Select CMS plugin -> Link
>>> > 4.) add http:// or https:// manually, paste target behind
>>> > 5.) Save
>>> >
>>> > Hope this helps, please ask back if my explanation wasn't clear
>>> enough.
>>> >
>>> > Regards,
>>> > Maren
>>> >
>>> > Am 20.01.2015 um 01:53 schrieb Duarte Ramos:
>>> >> No problem I misread too, I am currently using the pre release 3,
>> I
>>> >> must have misread and thought it was the official 0.91.
>>> >>
>>> >> I still can't copy the plugins but I have got another weird
>>> issue. I
>>> >> just updated the downloads page with the part about pre4. Manually
>>> >> copied the updated text from the from the English page and
>>> translated
>>> >> all strings, but whenever I hit publish the text with links simply
>>> >> vanishes. If I edit the page again translated text displays fine
>>> >> again, but on the published version the links are removed.
>>> >>
>>> >
>>>
>>>
>>>
>> ------------------------------------------------------------------------------
>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>> GigeNET is offering a free month of service with a new server in
>>> Ashburn.
>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>> Higher redundancy.Lower latency.Increased capacity.Completely
>>> compliant.
>>> http://p.sf.net/sfu/gigenet
>>> _______________________________________________
>>> Inkscape-translator mailing list
>>> Inkscape-translator(a)lists.sourceforge.net
>>> <mailto:Inkscape-translator@lists.sourceforge.net>
>>> https://lists.sourceforge.net/lists/listinfo/inkscape-translator
>>>
>>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>> http://p.sf.net/sfu/gigenet
>> _______________________________________________
>> Inkscape-translator mailing list
>> Inkscape-translator(a)lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/inkscape-translator
>>
>
8 years, 10 months
Re: [Inkscape-translator] Website translation updates
by Maren Hachmann
Hi Victor,
the news translation is really the easiest way to translate something on
the website, as it doesn't have all those plugins and stuff. It would
have been a really good beginner's job ;)
- The updated FAQ is currently not yet on the real website, but you can
start translating to pt-br at staging.inkscape.org instead (choose any
language you like for filling it in), and copy over later (there are
only very few link plugins, so copying will be possible without very
much hassle). Much of it is already translated, as the new FAQ also
contains parts from the old FAQ, and Duarte has already invested a lot
of work into translating the old FAQ.
The English new FAQ is here:
http://staging.inkscape.org/en/brynns-user-faq/ .
Duarte's translation of the old FAQ is here:
https://inkscape.org/pt/aprender/perguntas-frequentes
Always make sure that you do *not edit the English FAQ* by looking at
the url! (In fact, please don't edit any page starting with 'brynn...'
in English.)
Also make sure you have a backup of the source from your translation of
the FAQ on your own computer, as on staging, people practice, and they
may accidentally change your work.
You will also need an account on staging.inkscape.org for this, and some
permissions. I need to know your username there so I can grant you
permissions on staging.
- The official tutorials for Inkscape are translated in the inkscape
trunk, ask Nicolas Dufour (jazzynico) about this (I think you have
already contacted him earlier). For the next release, though, this may
be too late. Bryce Harrington wrote something about next week...
- The fixed parts of the site can be translated from the files for the
website at launchpad. I will append a current po file to this message, BUT:
- the file currently contains too many entries (for many of those,
translations do already exist, but are not automatically added to the file)
- the contents of the file is still changing heavily
- there is a better system for translating those on the way, but not yet
fully implemented.
So you *can* work on it, but:
- we may not need everything, because some of it already is translated
- it will still change
- there will be a better way for doing this soon
All in all, I think Duarte's suggestion of starting with the news (after
you have practiced on staging) is really a very good idea ;)
Regards,
Maren
PS: I had to remove the attachment, because the mailing-list refused to
accept it. Contact me directly, if you want the .po file ;)
Am 20.01.2015 um 16:39 schrieb Victor Westmann:
> How can I start translating fixed parts of the site?
>
> Not very much interested in the news right now. But in the FAQ and
> maybe tutorials. :)
>
> Cheers from Brazil.
>
>
>
> --Victor Westmann
>
> 2015-01-19 23:55 GMT-02:00 Duarte Ramos <duarte.framos@...5...
> <mailto:duarte.framos@...5...>>:
>
> Thank you very much for the explanation, Portuguese Downloads page
> updated. Also fixed all the links and reconnected them back to the CMS
> plugin so it can be correctly copied as base again.
>
> On a side note, if Pablo, Victor are full of energy and want to
> help out
> lets not waste human power. :)
> While the site update doesn't go live and they can't start translating
> the BR version maybe they can help with the PT one. If they are
> available they could start out with the "news" section and help
> translate the latest 2014 and 2015 news since they are generally
> smaller
> content and easy to start with . I was saving them for last but it's
> probably gonna take me a while o get there and that way when the
> Brazilian site goes live those can be ported there and no effort is
> wasted. Eventually after that happens I'll then update the PT news if
> needed.
>
> Thanks again, Duarte
>
>
> On 20-01-2015 01:32, Maren Hachmann wrote:
> > Hi Duarte,
> >
> > plugin links cannot be copied directly by going to the source
> and using
> > Ctrl+V and then pasting them.
> >
> > They have unique ids and can't be used on different pages,
> especially if
> > their contents changes.
> >
> > You may want to translate the link's text ;) - but if it is the same
> > object with the same id in the database, you would also change the
> > original link's text, this is prevented by cleaning them out in
> > published pages.
> >
> > So, you need to copy the text from English by copying from the page
> > directly (not from source, but from the 'real' page) into the
> > non-source-mode editor window. This will magically insert the
> contents
> > in a formatted way.
> >
> > Then, if you want to turn the link into a plugin again (which may be
> > useful if other people want to copy your page completely as a
> start for
> > their own translation, because in that case, the plugins are
> *really*
> > duplicated, with their new, own id):
> >
> > 1.) right-click on the link in the editor to select
> > 2.) choose 'edit' to be able to copy the target
> > 3.) Select CMS plugin -> Link
> > 4.) add http:// or https:// manually, paste target behind
> > 5.) Save
> >
> > Hope this helps, please ask back if my explanation wasn't clear
> enough.
> >
> > Regards,
> > Maren
> >
> > Am 20.01.2015 um 01:53 schrieb Duarte Ramos:
> >> No problem I misread too, I am currently using the pre release 3, I
> >> must have misread and thought it was the official 0.91.
> >>
> >> I still can't copy the plugins but I have got another weird
> issue. I
> >> just updated the downloads page with the part about pre4. Manually
> >> copied the updated text from the from the English page and
> translated
> >> all strings, but whenever I hit publish the text with links simply
> >> vanishes. If I edit the page again translated text displays fine
> >> again, but on the published version the links are removed.
> >>
> >
>
>
>
------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in
> Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely
> compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Inkscape-translator mailing list
> Inkscape-translator(a)lists.sourceforge.net
> <mailto:Inkscape-translator@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/inkscape-translator
>
>
8 years, 10 months
Re: [Inkscape-translator] Translation team for Inkscape website
by Egor Panfilov
Good day, Maren and others!
My name is Egor Panfilov. Currently I translate Inkscape website into
Russian.
Just informing about myself :).
Maren, I already have all permissions to modify live website I need.
Have a nice day, everyone!
Regards,
Egor Panfilov
2015-01-17 19:07 GMT+03:00 Maren Hachmann <maren@...325...>:
> Hi translators,
>
> I'm Maren, one of the people who work on improving the Inkscape website.
>
> I'd like to invite you to officially join the website translation team,
> if you are not part of it already (and if you are, to say so, because
> I'm not at all sure that everyone I send this message is really a
> translator).
>
> Some of you already have translated parts of the website, but as the
> website evolves, there's always something to be done - we need your
> expertise in your language!
>
> The last months have brought a lot of change to the website inside and
> outside. There are new features, and there is a lot of new contents (and
> some new bugs, too...).
>
> If you want to help, I would like to ask you to primarily focus on three
> things:
>
> 1.) The Support Us page and subpages (we are planning a Donation
> campaign to start soon, and especially need French and Spanish
> translations)
>
> 2.) The About section (The board plugin can't currently be translated.
> If you want to translate the biographies, copy from German, where I
> made a html source copy of the board plugin.)
>
> 3.) The Download section (so it is prepared for the next release - when
> that comes, you will only need to exchange some numbers and links)
> Many of the other pages, especially the FAQ and the Community, Learn and
> Contribute pages, are currently being changed and edited a lot, so those
> may need to wait until they are 'stable'.
>
> Django-CMS is, unfortunately, a bit delicate about its revert, undo and
> history functions - and there have been changes to the system some of
> you may not be aware of.
>
> This is why it's suggested to first read the guide I made for you:
>
> http://wiki.inkscape.org/wiki/index.php/WebSite
>
> and then to get yourself an account at http://staging.inkscape.org, and
> play a bit around to try it all out (don't edit pages with names
> starting with 'Brynn', please, they are drafts for the main website).
>
> Some of you may not have all the permissions necessary - please send a
> message to the translators' mailing list (containing your user name!) if
> you need permissions for staging / for the live website.
>
> It would be good to know who translates to which language, so we can
> coordinate who is working on which page, to avoid simultaneous editing
> and loss of people's work ;)
>
> Also, if you have any questions, encounter problems or have suggestions,
> just write to the translators' mailing list - it's been far too calm
> there for a while, and we should change that :)
>
> Hope to hear from as many of you as possible ;) ,
> Regards,
> Maren
>
>
8 years, 10 months
Re: [Inkscape-translator] Translation team for Inkscape website
by Duarte Ramos
Hello everyone, following the mail from Maren I am reporting to the
translators mailing list to which I believe I never got to subscribed in
the past.
My name is Duarte Ramos and I am currently the only (at least to my
knowlege) website translator for the Portuguese language.
I have been more or less active with the translation depending on the
free time I can spare, although I have to admit that I have been
"loosing steam" as time goes by. That doesn't mean I have stopped
completely, as I plan to keep going until I all is done, and maintain it
afterwards as changes come up.
It would definitely be nice to know which pages are "static" or which
pages are being worked on or undergoing changes so that no translation
effort is lost on out of date content. I have been going through the
(very ) long FAQ page for quite some month now, but a lot of it looks
like really out of date content.
Many are about very old versions of Inkscape I doubt anyone still uses,
and workarounds for old operating systems and past bugs that are
probably no longer relevant today .
On 17-01-2015 16:07, Maren Hachmann wrote:
> Hi translators,
>
> I'm Maren, one of the people who work on improving the Inkscape website.
>
> I'd like to invite you to officially join the website translation team,
> if you are not part of it already (and if you are, to say so, because
> I'm not at all sure that everyone I send this message is really a
> translator).
>
> Some of you already have translated parts of the website, but as the
> website evolves, there's always something to be done - we need your
> expertise in your language!
>
> The last months have brought a lot of change to the website inside and
> outside. There are new features, and there is a lot of new contents (and
> some new bugs, too...).
>
> If you want to help, I would like to ask you to primarily focus on three
> things:
>
> 1.) The Support Us page and subpages (we are planning a Donation
> campaign to start soon, and especially need French and Spanish translations)
>
> 2.) The About section (The board plugin can't currently be translated.
> If you want to translate the biographies, copy from German, where I
> made a html source copy of the board plugin.)
>
> 3.) The Download section (so it is prepared for the next release - when
> that comes, you will only need to exchange some numbers and links)
> Many of the other pages, especially the FAQ and the Community, Learn and
> Contribute pages, are currently being changed and edited a lot, so those
> may need to wait until they are 'stable'.
>
> Django-CMS is, unfortunately, a bit delicate about its revert, undo and
> history functions - and there have been changes to the system some of
> you may not be aware of.
>
> This is why it's suggested to first read the guide I made for you:
>
> http://wiki.inkscape.org/wiki/index.php/WebSite
>
> and then to get yourself an account at http://staging.inkscape.org, and
> play a bit around to try it all out (don't edit pages with names
> starting with 'Brynn', please, they are drafts for the main website).
>
> Some of you may not have all the permissions necessary - please send a
> message to the translators' mailing list (containing your user name!) if
> you need permissions for staging / for the live website.
>
> It would be good to know who translates to which language, so we can
> coordinate who is working on which page, to avoid simultaneous editing
> and loss of people's work ;)
>
> Also, if you have any questions, encounter problems or have suggestions,
> just write to the translators' mailing list - it's been far too calm
> there for a while, and we should change that :)
>
> Hope to hear from as many of you as possible ;) ,
> Regards,
> Maren
>
>
>
8 years, 10 months
Website: Donation pages updated
by Maren Hachmann
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello website translators,
we've got two new pages on the website asking for your translating
attention ;) (German translators, relax, no work for you ;) ) :
https://inkscape.org/en/donate/hackfest/
(about the donation campaign for the Inkscape Hackfest in April in Toronto)
and
https://inkscape.org/en/donate/sponsors/
(about the sponsors of our website)
There are two important things you should know:
1. The menu might not update right away. Don't worry, if you created a
page it *is* there. Just go to the English page and exchange the "en" in
the URL with your own language's abbreviation.
2. Please, avoid using any page reset / history / undo function. These
are buggy and can cause the work of other people to be LOST (they 'undo'
everything, not only changes to your own language).
For a newly updated guide on how to go about translating a page, please
visit our wiki page:
http://wiki.inkscape.org/wiki/index.php/WebSite#Translations
If you've got any questions, please ask on the list or send me a mail.
(I'm not sure if I'm allowed to tell you this: something *big* is in the
making for making translating the website a lot easier... ;) )
Thank you all for your help,
Maren (Moini)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iF4EAREIAAYFAlSoIGcACgkQKoYx0uUjpE2VuQD/ReBCErz3sg7oAPJldM+bvE2m
I9SeepjNWpcABhg7SSQA/RwXZPKQrWdsBO9v4nvY/YRDK7hMgrbNTzl33FvUUNaY
=ZYFw
-----END PGP SIGNATURE-----
8 years, 10 months