Re: Unbalanced tag
Hi Ilmari, Ilmari Lauhakangas schrieb am 18.06.2023 um 20:53: I've now cleaned up the page. Thank you. The reason why we want to break up individual bullet points into translation units is that otherwise translators may end up with a giant pile of text in a single unit. It's not very fun trying to wrestle that in a small text box in the translation interface. That makes sense. If there is ever a problem with the tags, Save Changes will point out the area that has the problem (while blocking you from saving). That happens to me. One bad habit we have to kick for release notes pages is the use of thumbnailed images with captions. Unfortunately this breaks our newly acquired mobile friendliness. Instead we should use elements. You can see an example in this edit: https://wiki.documentfoundation.org/index.php?title=ReleaseNotes%2F7.4=revision=642340=642284 I have written a document which is linked in the release notes. That document contains screenshots. I have mainly used a separate document to make the example shapes copyable. I think that should be OK. Kind regards, Regina
Re: Unbalanced tag
On 18.6.2023 21.34, Regina Henschel wrote: Hi Julien, Julien Nabet schrieb am 18.06.2023 um 18:59: On 18/06/2023 18:48, Regina Henschel wrote: ... This is the text which produces the problem: ... I'm not an expert but I think you need a "translate" start tag and a "translate" end tag at each line. It seems I do not need it for each line but one pair is enough. [..] Perhaps there's another way but when taking a look at the existing page, it seemed the right way to do it. Also I tested it in Core section by using Preview and it seemed ok to me. "look at the existing page" was the helpful hint. My error was this: I have only edit a section. I saw a at the bottom in the edit window and had removed it. I was not aware that it belongs to the following heading, which is not included in the edit window. Looking at the complete page makes it visible. I've now cleaned up the page. The reason why we want to break up individual bullet points into translation units is that otherwise translators may end up with a giant pile of text in a single unit. It's not very fun trying to wrestle that in a small text box in the translation interface. If there is ever a problem with the tags, Save Changes will point out the area that has the problem (while blocking you from saving). One bad habit we have to kick for release notes pages is the use of thumbnailed images with captions. Unfortunately this breaks our newly acquired mobile friendliness. Instead we should use elements. You can see an example in this edit: https://wiki.documentfoundation.org/index.php?title=ReleaseNotes%2F7.4=revision=642340=642284 Ilmari
Re: Unbalanced tag
Hi Julien, Julien Nabet schrieb am 18.06.2023 um 18:59: On 18/06/2023 18:48, Regina Henschel wrote: ... This is the text which produces the problem: ... I'm not an expert but I think you need a "translate" start tag and a "translate" end tag at each line. It seems I do not need it for each line but one pair is enough. [..] Perhaps there's another way but when taking a look at the existing page, it seemed the right way to do it. Also I tested it in Core section by using Preview and it seemed ok to me. "look at the existing page" was the helpful hint. My error was this: I have only edit a section. I saw a at the bottom in the edit window and had removed it. I was not aware that it belongs to the following heading, which is not included in the edit window. Looking at the complete page makes it visible. If you're still stuck, I can submit it if you want (at worst, it's always possible to modify afterwards) Thank you for your help. Kind regards, Regina
Re: Unbalanced tag
On 18/06/2023 18:48, Regina Henschel wrote: ... This is the text which produces the problem: * Added support for multicolor gradients (Armin Le Grand) ** LibreOffice 7.6 has a new feature called "multicolor gradients" (MCGR) implemented by Armin Le Grand. A multicolor gradient still goes from a starting color to final color, but now additional colors are possible in between. ** Although the ''Gradient'' tab in the ''Area'' dialog has not yet been adapted to the new feature, you can use such gradients. The document ... lists hints on what you can already do, and the ''Gradient'' list in the dialog contains two "Rainbow" examples. ** You can create and modify multicolor gradients using macros, see the ''Gradient2'' struct and the associated ''ColorStop'' struct in the SDK API reference https://api.libreoffice.org/docs/idl/ref/index.html. ** Since this is a new feature, you might find errors. In this case, please help improve the feature by reporting the issue in our bug tracking system "Bugzilla" https://wiki.documentfoundation.org/Bugzilla. When doing so, mention 'MCGR' in the subject line. ** Some notes: *** LibreOffice versions prior to 7.6 cannot interpret multicolor gradients. They will display a gradient made from the first and last color. *** You need to use "1.3 Extended (recommended)" file format. This is the default setting, so don't worry. *** Some gradient properties in ODF (LibreOffice) and OOXML (Microsoft Office) are basically incompatible. This problem is not solved by multicolor gradients. ... I'm not an expert but I think you need a "translate" start tag and a "translate" end tag at each line. I tried with: * Added support for multicolor gradients (Armin Le Grand) ** LibreOffice 7.6 has a new feature called "multicolor gradients" (MCGR) implemented by Armin Le Grand. A multicolor gradient still goes from a starting color to final color, but now additional colors are possible in between. ** Although the ''Gradient'' tab in the ''Area'' dialog has not yet been adapted to the new feature, you can use such gradients. The document ... lists hints on what you can already do, and the ''Gradient'' list in the dialog contains two "Rainbow" examples. ** You can create and modify multicolor gradients using macros, see the ''Gradient2'' struct and the associated ''ColorStop'' struct in the SDK API reference https://api.libreoffice.org/docs/idl/ref/index.html. ** Since this is a new feature, you might find errors. In this case, please help improve the feature by reporting the issue in our bug tracking system "Bugzilla" https://wiki.documentfoundation.org/Bugzilla. When doing so, mention 'MCGR' in the subject line. ** Some notes: *** LibreOffice versions prior to 7.6 cannot interpret multicolor gradients. They will display a gradient made from the first and last color. *** You need to use "1.3 Extended (recommended)" file format. This is the default setting, so don't worry. *** Some gradient properties in ODF (LibreOffice) and OOXML (Microsoft Office) are basically incompatible. This problem is not solved by multicolor gradients. Perhaps there's another way but when taking a look at the existing page, it seemed the right way to do it. Also I tested it in Core section by using Preview and it seemed ok to me. If you're still stuck, I can submit it if you want (at worst, it's always possible to modify afterwards) Julien.
Re: Unbalanced tag
Julien Nabet schrieb am 18.06.2023 um 17:57: Hello Regina, Would it be possible you attach the raw text you're trying to include ? Indeed, except to ask you to check that each tag is well closed (especially "translate"), it's difficult to help. Julien This is text I want to finally get: LibreOffice 7.6 has a new feature called "multicolor gradients" (MCGR) implemented by Armin Le Grand. A multicolor gradient still goes from a starting color to final color, but now additional colors are possible in between. Although the 'Gradient' tab in the 'Area' dialog has not yet been adapted to the new feature, you can use such gradients. The document ... lists hints on what you can already do, and the 'Gradient' list in the dialog contains two "Rainbow" examples. You can create and modify multicolor gradients using macros, see the 'Gradient2' struct and the associated 'ColorStop' struct in the SDK API reference https://api.libreoffice.org/docs/idl/ref/index.html. Since this is a new feature, you might find errors. In this case, please help improve the feature by reporting the issue in our bug tracking system "Bugzilla" https://wiki.documentfoundation.org/Bugzilla. When doing so, mention 'MCGR' in the subject line. Some notes: LibreOffice versions prior to 7.6 cannot interpret multicolor gradients. They will display a gradient made from the first and last color. You need to use "1.3 Extended (recommended)" file format. This is the default setting, so don't worry. Some gradient properties in ODF (LibreOffice) and OOXML (Microsoft Office) are basically incompatible. This problem is not solved by multicolor gradients. The ellipses in document... will be filled with the link after I have uploaded the file. This is the text which produces the problem: * Added support for multicolor gradients (Armin Le Grand) ** LibreOffice 7.6 has a new feature called "multicolor gradients" (MCGR) implemented by Armin Le Grand. A multicolor gradient still goes from a starting color to final color, but now additional colors are possible in between. ** Although the ''Gradient'' tab in the ''Area'' dialog has not yet been adapted to the new feature, you can use such gradients. The document ... lists hints on what you can already do, and the ''Gradient'' list in the dialog contains two "Rainbow" examples. ** You can create and modify multicolor gradients using macros, see the ''Gradient2'' struct and the associated ''ColorStop'' struct in the SDK API reference https://api.libreoffice.org/docs/idl/ref/index.html. ** Since this is a new feature, you might find errors. In this case, please help improve the feature by reporting the issue in our bug tracking system "Bugzilla" https://wiki.documentfoundation.org/Bugzilla. When doing so, mention 'MCGR' in the subject line. ** Some notes: *** LibreOffice versions prior to 7.6 cannot interpret multicolor gradients. They will display a gradient made from the first and last color. *** You need to use "1.3 Extended (recommended)" file format. This is the default setting, so don't worry. *** Some gradient properties in ODF (LibreOffice) and OOXML (Microsoft Office) are basically incompatible. This problem is not solved by multicolor gradients. Kind regards Regina
Re: Unbalanced tag
Hello Regina, Would it be possible you attach the raw text you're trying to include ? Indeed, except to ask you to check that each tag is well closed (especially "translate"), it's difficult to help. Julien
Unbalanced tag
Hi, I want to add "multicolor gradient" to https://wiki.documentfoundation.org/WikiAction/submit/ReleaseNotes/7.6 But I get an error Unbalanced tag and don't know how to solve it. Kind regards, Regina
