Re: [Inkscape-translator] Website Update: Changes for editors and translators
Also, it is still not possible to edit/update the Front Shield (which is out of date in French). Sylvain Le 21/03/2016 13:26, Sylvain Chiron a écrit : >> - I had just a few minutes ago received a mail from Brynn where she >> told me about the missing permissions for editing the new plugin. They are >> available now. > > Nice. > >> About the nesting: Can you give some more details (or maybe make a bug >> report with screenshots when you're certain it's a bug at >> bugs.launchpad.net/inkscape-web)? > > It looks flagrant to me but if you want… Here is a screenshot (made > with GIMP — :P): http://i.imgur.com/qBq3GYx.png > Looks like a title cannot unnest twice at once (e.g. h5 then h2 causes > the h2 to be nested in the previous h2). > >> - That's at least 20 times less than it was before! :D > > Oh! I thought the button didn't work at all before. This explains that. > >> - The title looks great - only the page was empty. The gallery (like the >> board page) is a special case. In such cases, look at how things are >> done in the advanced settings for the page in languages where it works, >> then do it the same way in your language. It's fixed now for French. > > Thanks. > But I cannot access the advanced settings of the page in the other > languages… The menu is not present. > > Another remark: if https://inkscape.org/fr/news/ is translated to e.g. > https://inkscape.org/fr/actu/ then the ‘Read more’ links don't work. It > is also strange that ‘Read more’ is not translated. And we can't either > translate the title ‘Latest news’. And the news are sorted by date of > translation, not date of publication (which is bad because I lastly > translated the Hackfest 2015 article)… And I can't access the articles' > translation anymore. (Should I open bug reports for all that?) > > I see that now plugins can be edited by a single click. That's not > really helpful… The previous double-click allowed to select the text for > Link plugins, and to edit it avoiding any bug. > > And the dialog to edit a plugin is sometimes too big and I cannot access > the validation buttons! (Try when your edit dialog is maximized.) That's > bad. > -- > Sylvain -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351=/4140 ___ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator
[Inkscape-translator] Wrong manipulation
Hello, Big mistake today: I wanted to import the current version of https://inkscape.org/en/develop/next-release/ from English to French but my favorite method is always to delete and copy… But in fact I deleted the content for all languages! Could you restore it, please? -- Sylvain -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140 ___ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator
Re: [Inkscape-translator] Wrong manipulation
Le 26/01/2016 20:34, Maren Hachmann a écrit : > Hi Sylvain, > > it was only the drafts that were gone, the published pages looked okay > all the time (so nobody but us noticed ;) ). > > I've reverted your changes from today now, and added a copy of the > current English to your French draft (at the bottom). > > Do you happen to remember which steps exactly led to the loss of all > draft contents? (I'm trying to understand if this is a bug or really > just a wrong click on 'Empty all' - happened to me once, too...) > > Kind regards, > Maren It's a wrong click on ‘Empty all’. Sylvain > Am 26.01.2016 um 19:09 schrieb Sylvain Chiron: >> Hello, >> >> Big mistake today: I wanted to import the current version of >> https://inkscape.org/en/develop/next-release/ from English to French but >> my favorite method is always to delete and copy… But in fact I deleted >> the content for all languages! >> >> Could you restore it, please? >> > > > -- > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140 > ___ > Inkscape-translator mailing list > Inkscape-translator@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-translator > -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140 ___ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator
Re: [Inkscape-translator] Introducing myself
Hello. Le 17/09/2015 12:04, Maren Hachmann a écrit : > Sorry, real answer below! (One shouldn't eat while reading mails...) It bit me but I quickly threw it to the trash. >> 1. For an end-user system, I prefer saying GNU/Linux rather than Linux. >> It was already called ‘GNU/Linux’ in the English page Download > >> GNU/Linux, so I also used this name at other places instead of only Linux. >> You may see here what that means: >> https://en.wikipedia.org/wiki/GNU/Linux_naming_controversy >> 2. For most controversed typography conventions, follow Wikipedia: >> * 32-bit rather than 32bit; >> * Red Hat (or RHEL?) instead of Redhat; >> * APT and Yum instead of apt and yum; >> * openSUSE instead of OpenSUSE; >> * … (see as I'm picky — ;)) > > - These make sense, I think. Do you have a list of pages that are > concerned by these? Please also coordinate with people on inkscape-docs > for these kinds of changes. The download pages are concerned: https://inkscape.org/en/download/ https://inkscape.org/en/download/linux/ https://inkscape.org/en/download/windows/ The FAQ is probably too. > - Draw Freely is a trademarked slogan. This will not be translated. > The other strings of the web site are translatable, but there's no > obvious place to do so. Please open a bug report on launchpad, at > https://bugs.launchpad.net/inkscape-web, so we can generate the files, > and attach them for you. I can do so next week, if you like. Be aware > that it's a constantly moving target ;) I sent the translations to Martin and he replied: ‘All these translations are done via po files. Keep them safe until the website's next version is available to translate and we'll make sure you have the po file to do all the strings.’ So I will wait the next version. OK for the slogan. >> French-specific choices/discussions: > >> 6. Importez les contenus anglais même sans les traduire. Comme je l'ai >> dit en intro de mon courriel, mieux vaut avoir du contenu non traduit >> que de ne pas voir le contenu… Ainsi, j'ai importé des pages que j'ai >> lasisées en anglais. J'imagine n'est pas forcément naturel pour un >> visiteur de regarder le site dans une autre langue pour avoir plus de >> détails ! > > - If you do that, Sylvain, please add the copied, but non-translated > pages to this list: > https://bugs.launchpad.net/inkscape-web/+bug/1421202 > > In the next version of the website, pages that are missing in a > language, will automatically be replaced by their English counterparts. > This means that all *really* very outdated or just copied (and maybe > also outdated) contents will have to be deleted, so we will have the > most current version that shows. OK. I will probably translate everything soon (at least partly on every page), so not sure it will be so useful — ;). >> 7. J'ai vu que la FAQ est peu traduite et ce qui est traduit l'est sans >> rigueur (dans le rythme et l'orthotypo). Soyez précis car j'aime >> vraiment que tout soit parfait, et relire une page juste pour corriger >> la typographie, ce n'est pas super passionnant (même si je le fais très >> souvent sur Wikipédia et d'autres plateformes collaboratives). > > - Sylvain, please, be careful to not discourage your fellow translators, > we need them all and we appreciate their work. We are not aiming for > perfection, but for a community that makes people feel welcome, and > happy to contribute. My numerous demands make me stressing, sure. Sorry. Lack of perfection in something that can be so precise (digital data and linguistics) has always looked weird to me. > You can improve the FAQ, and that's good - but some people may have less > time for this than you do. The English FAQ has changed very much in the > last 9 months, so it is to be expected that the French one is quite > different if people don't have time to help. Yes. It was not fully translated. I'll work on it. Thanks and bye, -- Sylvain -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140 ___ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator
[Inkscape-translator] Introducing myself
Hello to the Inkscape translators' team. I was previously an Inkscape user, using the software to make diagrams with a very customized style. Then I was not satisfied of the features I used and I questionned myself about the ergonomy. Finally (after months of occasional usage), I decided to discover what the community was doing. On the website, one of my first notices was that the website is only partly translated. However, it's not cool when the website shows in your browser's language and you don't have content unless you have this miraculous idea to show the English version. As I am not used to tell people that they must work, I wanted to do the work myself; I already translated parts of the website in my mother-language (which is French). I had already liked to translate software (without coordinating with anyone), and I am a student in computing technology. I am nearly 20, and I practise computer programming since I've been 12 in an association in Bordeaux. So I may even touch the code one day. Also, I would certainly love developing a passion for vector graphics since I find a nice mathematic sense in it: it is able to explain things with rigour and precision, and to be nice to the eyes. I like brilliant pictures but my current very first interest is in pedagogy and information. A few ads here: * you can see this website I'm making with a cousin to present his art: http://www.abstractluminary.com/ (that is ‘brilliant’) * I'm implied in two French associations that teach science: http://www.jeunes-science.asso.fr/ and computer science: http://www.france-ioi.org/ (that is ‘pedadogy and information’) Last, I never promote software that's not open source (I even avoid to promote non-copyleft soft). Then I think Inkscape can be very interesting for me. As I was translating pages on the website, Martin and Maren (the website administrator and the translators' leader if I remember well) told me I need to inform you what choices I make in the translations. So here are the choices. So here are some choices/changes I already began to apply, or I think they should be applied: 1. For an end-user system, I prefer saying GNU/Linux rather than Linux. It was already called ‘GNU/Linux’ in the English page Download > GNU/Linux, so I also used this name at other places instead of only Linux. You may see here what that means: https://en.wikipedia.org/wiki/GNU/Linux_naming_controversy 2. For most controversed typography conventions, follow Wikipedia: * 32-bit rather than 32bit; * Red Hat (or RHEL?) instead of Redhat; * APT and Yum instead of apt and yum; * openSUSE instead of OpenSUSE; * … (see as I'm picky — ;)) Of course, you may suggest other conventions if you have arguments. (You might try to convince the Wikipedia community before.) Question: Is it possible to translate ‘Draw Freely.’ and ‘Follow us on:’ in the website header? French-specific choices/discussions: 1. Accordez-vous avec Wikipédia aussi ! N'oubliez pas d'utiliser /toujours/ les bons guillemets : « », de mettre les espaces avant les symboles de ponctuation à deux composantes (ce qui ne se fait pas en anglais). Pour les architectures, on écrit « 32 bits ». 2. Pas de majuscules à chaque mot dans les titres comme c'est fait en anglais. De mon expérience, c'est généralement une recherche compliquée et désagréable en français. On se contentera généralement d'une majuscule au début et aux noms propres. 3. « Vue d'ensemble » (traduction d'‘Overview’) ne se dit pas trop en français ; je l'ai laissé dans la page À propos, mais dans la page enfant, j'ai préféré utiliser Présentation. J'ai fait d'autres choix que vous pourrez voir en visitant la version française ; libre à vous de proposer autre chose ; je serai certainement moi-même amené à revenir sur certains nommages. 4. Aussi : Télécharger plutôt que Téléchargement. C'est plus sympa d'utiliser un verbe quand c'est possible, car ça encourage le visiteur à agir, plutôt qu'à être spectateur ; et ça lui correspond mieux quand il veut déjà agir. 5. Pour les bugs, je parle généralement de « bogues » à la québécoise — j'apprécie peu les anglicismes (pourtant, Wikipédia dit « bugs » !). On peut aussi parler de problèmes et de défauts. 6. Importez les contenus anglais même sans les traduire. Comme je l'ai dit en intro de mon courriel, mieux vaut avoir du contenu non traduit que de ne pas voir le contenu… Ainsi, j'ai importé des pages que j'ai lasisées en anglais. J'imagine n'est pas forcément naturel pour un visiteur de regarder le site dans une autre langue pour avoir plus de détails ! 7. J'ai vu que la FAQ est peu traduite et ce qui est traduit l'est sans rigueur (dans le rythme et l'orthotypo). Soyez précis car j'aime vraiment que tout soit parfait, et relire une page juste pour corriger la typographie, ce n'est pas super passionnant (même si je le fais très souvent sur Wikipédia et d'autres plateformes collaboratives). Here are my first remarks. Tell what you think and what you plan; I will continue for
