Re: [libreoffice-website] Italian translation of LO website - is something stuck?
Hi Emiliano, *, On Fri, May 19, 2023 at 10:33 PM Emiliano Vavassori wrote: > Il 19/05/23 12:13, Christian Lohmaier ha scritto: > […] > > To have translated sidebar buttons you > > need to provide translated content in silverstipe backend on the > > download page. > > the "Sidebar Button" field labeled "Sidebar buttons, see > > https://redmine.documentfoundation.org/issues/1023; the ticket shows > > sample syntax > > Thanks for the information. I will involve the translation group on this > specific snippet and get back to the list/to you in private when ready. No need for me here - it is treated as regular page content, so just saving the file in the backend will do the trick. (if the content box is empty, it defaults to the English sidebar, if there is content, that will be used instead - there's no need to use the button style, but since the css/html for that might not be obvious the sample syntax for those is provided in the redmine ticket) > > but for some > > reason the exported files on the website server do not have the string > > for italian (but for a couple of others) > > In the meantime Marina did a quick check for other languages and it > seems Italian is indeed not the only one (for sure we know of partial > translations on Spanish, French and Chinese zh-cn). But I am sure you > have a better understanding of its impact as of now. While I don't know exactly why the strings were missing, at least now the export did work as expected. > > Not problems like that - the translations aren't synced regularly > > (then again strings also change very rarely), but I was not aware of > > incomplete transfer of strings. > > Yeah, well, it doesn't make sense to check each week for translations, > indeed. I hoped there was a simple, less manual way to deal with it, but > no need for it if complicates too much and doesn't give much of an > advantage. When I write manual it is not so bad as having to copy each string manually, but to do some cleanup of the files. For example remove entries with no/empty translation so that the content will not just disappear and similar stuff. And the strings completely missing from the old export/showing up in only some just has been not reported/missed earlier - Last time when German team mentioned the missing GPG strings I naturally only focused on them, and those were there... So automated mechanism wouldn't really have helped here. > […] > Is there an easy way to recognize which parts are still managed in > Silverstripe and the ones that are in Weblate, apart of the obvious > "check in Weblate, if the string is not there then it is managed in > Silverstripe"? It can be summarized as such: If it is not a simple page type, but for example a page of type DownloadPage or DonatePage, then chances are high that large parts of those come from weblate/are autogenerated. everything else is is in silverstripe directly > Do you think it is feasible to have some backups for that work and/or a > responsible person on each NLP, that are able to verify and in case > deploy modifications to the website or it will be mostly > useless/painful? I think the Italian NLP project already had someone, > but I think he is not so much present anymore. If you mean people maintaining localized websites? Nope, no fallback for those, and I guess having the pages handled automatically / not having an incentive to log in to the site to update it for each release along with the content of the English page also not changing often/at all didn't help in having active people. Basically you only have to create a localized page once, and then don't have to care anymore... If you mean backups of the translations: weblate stores them in a git repository. > With "Git managed site" you meant similar to what happens/have happened > with TDF website (so based on Hugo)? Is there any foreseeable time-span > in which you think that could land? Yes, so far the development on the sample site has been done with hugo, but I currently don't know a concrete date, but I'd certainly hope it will be completed this year/in the next months. > >> What's the expected workflow around > >> updating NLP pages? > > > > That's still manual, introducing new strings into the system would > > require manual update of the strings that are available in weblate, > > and then exporting strings from weblate to silverstripe is also manual > > since the yaml file needs to meet certain formatting standards/cannot > > be used directly. > > Ah, that's quite a bummer - but I guess it is something we can live with > for as long as needed to move to a new platform, also given the low > frequency of the task. Yes, and as written above: the steps are manual, but not overly complex... And we didn't have any new NL-sites in quite a while/everything is already settled in... > […] > Thank you again so much for the answers and having unblocked the issue, Thanks for bringing it to the list/to my attention - that is really the only reason why
Re: [libreoffice-website] Italian translation of LO website - is something stuck?
Hi Christian, Many thanks for your answers; allow me another bunch of (quite stupid, indeed) questions, just to understand the matter. Il 19/05/23 12:13, Christian Lohmaier ha scritto: check out what happens on the download page in italian [1]; the right-sided buttons are not translated and I see their values are in the HTML code not translated. That is expected/by design. Ok, good to know. To have translated sidebar buttons you need to provide translated content in silverstipe backend on the download page. the "Sidebar Button" field labeled "Sidebar buttons, see https://redmine.documentfoundation.org/issues/1023; the ticket shows sample syntax Thanks for the information. I will involve the translation group on this specific snippet and get back to the list/to you in private when ready. Or the donations page [2] [...] Oh, should not have been a problem for years. Maybe a problem years back when the strings were added to the website but were not available on weblate, but that's long fixed since then. I have the impression this has been left as it is now since then. No one to blame, here - possibly missed communication from the translation team. We'll try to get better in communicating from our side (NLP project, I mean). but for some reason the exported files on the website server do not have the string for italian (but for a couple of others) In the meantime Marina did a quick check for other languages and it seems Italian is indeed not the only one (for sure we know of partial translations on Spanish, French and Chinese zh-cn). But I am sure you have a better understanding of its impact as of now. Are you aware of any issues in applying new translation efforts on the website? Not problems like that - the translations aren't synced regularly (then again strings also change very rarely), but I was not aware of incomplete transfer of strings. Yeah, well, it doesn't make sense to check each week for translations, indeed. I hoped there was a simple, less manual way to deal with it, but no need for it if complicates too much and doesn't give much of an advantage. Sparing you from tedious and manual operations was another clear goal, but that depends on the push to have that in place - which seems very low to me, with the current status-quo, and quite risky, while not requiring your efforts for a lot of time. Is Weblate the right tool to source for website translations, then, or this is still Silverstripe? A clear "it depends" (see above) - some parts are translated in weblate (mostly the static downlaod page and donate page strings), but other parts like project-specific stuff like sidebar buttons where each NL project might have different coverage/focus is done in silverstripe. Thanks for clarification. Is there an easy way to recognize which parts are still managed in Silverstripe and the ones that are in Weblate, apart of the obvious "check in Weblate, if the string is not there then it is managed in Silverstripe"? Do you think it is feasible to have some backups for that work and/or a responsible person on each NLP, that are able to verify and in case deploy modifications to the website or it will be mostly useless/painful? I think the Italian NLP project already had someone, but I think he is not so much present anymore. And honestly the migration to new website took/takes longer than expected, it was already decided long ago that the website system will change to the git managed site, so no real work was done on the old site.. Indeed, no need nor point to have the whole website sorted out in haste. With "Git managed site" you meant similar to what happens/have happened with TDF website (so based on Hugo)? Is there any foreseeable time-span in which you think that could land? What's the expected workflow around updating NLP pages? That's still manual, introducing new strings into the system would require manual update of the strings that are available in weblate, and then exporting strings from weblate to silverstripe is also manual since the yaml file needs to meet certain formatting standards/cannot be used directly. Ah, that's quite a bummer - but I guess it is something we can live with for as long as needed to move to a new platform, also given the low frequency of the task. I think it might have been a bug in one of weblate's dependencies that got updated meanwhile, at least when I export the italian website file now I get the DonateTimeHeader string... As said, it is totally possible the results of the bug was there since long, but the bug isn't around anymore. Thank you again so much for the answers and having unblocked the issue, cheers, -- Emiliano Vavassori syntaxerror...@libreoffice.org -- To unsubscribe e-mail to: website+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more:
Re: [libreoffice-website] Italian translation of LO website - is something stuck?
Hi *, On Fri, May 19, 2023 at 12:13 PM Christian Lohmaier wrote: > […] > I think it might have been a bug in one of weblate's dependencies that > got updated meanwhile, at least when I export the italian website file > now I get the DonateTimeHeader string... FYI: update the live site with the translations from weblate and from what I can see it worked as expected this time/brought over all translations from weblate. (that the german legal text is not translated on the donate text also is by design, that's why a placeholder is used for that in the string) As for Hugo: similar translation system will likely be used for the download page and donate pages - just makes sense to have translation mechanism for automatically generated pages. ciao Christian -- To unsubscribe e-mail to: website+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/website/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-website] Italian translation of LO website - is something stuck?
Hi Emiliano, *, On Wed, May 17, 2023 at 10:40 PM Emiliano Vavassori wrote: > > It has been brought to my attention by Italian NLP leaders that the > LibreOffice website, when viewed in Italian, breaks on translations (for > example, check out what happens on the download page in italian [1]; the > right-sided buttons are not translated and I see their values are in the > HTML code not translated. That is expected/by design. To have translated sidebar buttons you need to provide translated content in silverstipe backend on the download page. the "Sidebar Button" field labeled "Sidebar buttons, see https://redmine.documentfoundation.org/issues/1023; the ticket shows sample syntax System Requirements Join The Project! Do More with LibreOffice Good looking documents > Or the donations page [2]: the second part of > the page is not translated at all). This seems to be a long standing > problem (probably years) and we would like to ascertain there is no > misunderstanding in the understanding between TDF and the volunteers, here. Oh, should not have been a problem for years. Maybe a problem years back when the strings were added to the website but were not available on weblate, but that's long fixed since then. > Translators affirm that the untranslated parts of the website are indeed > available and translated inside Weblate. I honestly cannot judge if this > is true or not ATM, but it is quite evident there are some not > particularly nice partial translations there. I can confirm that e.g the donateyour time string is translated in weblate (and while a recent change was done only a few days ago for italian, it already was translated prior to that) - but for some reason the exported files on the website server do not have the string for italian (but for a couple of others) > Are you aware of any issues in applying new translation efforts on the > website? Not problems like that - the translations aren't synced regularly (then again strings also change very rarely), but I was not aware of incomplete transfer of strings. > Is Weblate the right tool to source for website translations, > then, or this is still Silverstripe? A clear "it depends" (see above) - some parts are translated in weblate (mostly the static downlaod page and donate page strings), but other parts like project-specific stuff like sidebar buttons where each NL project might have different coverage/focus is done in silverstripe. And honestly the migration to new website took/takes longer than expected, it was already decided long ago that the website system will change to the git managed site, so no real work was done on the old site.. > What's the expected workflow around > updating NLP pages? Does the same issue occur also on other NLP > projects' websites? Is there an automation pipeline to get newer > translations applied directly from Weblate to the NLP-specific website > or it is still manual work? That's still manual, introducing new strings into the system would require manual update of the strings that are available in weblate, and then exporting strings from weblate to silverstripe is also manual since the yaml file needs to meet certain formatting standards/cannot be used directly. I think it might have been a bug in one of weblate's dependencies that got updated meanwhile, at least when I export the italian website file now I get the DonateTimeHeader string... ciao Christian -- To unsubscribe e-mail to: website+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/website/ Privacy Policy: https://www.documentfoundation.org/privacy
