Re: draft followup Re: [needs proofread and translation] March newsletter
Francisco de Asis Fernandez Miser <[email protected]> Tue, 10 Mar 2026 11:00:27 +0100
| Newsgroups | gmane.org.fsf.europe.translators |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============1862851631429451227== Content-Type: multipart/alternative; boundary="------------LGBAZDvOGKNFRS0WTwLPjM1B" Content-Language: es-AR This is a multi-part message in MIME format. --------------LGBAZDvOGKNFRS0WTwLPjM1B Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hola, Ana: I still see some weird stuff around "Maintainers Matter", and "Thank Your". Regards! El 10/03/2026 a las 9:48, Ana Galan escribió: > > Dear all, > > sorry for all the garbage characters. I have no idea how this happened > as my original file is clean of those. Our system hackers are checking > our system so it won't happen again. > > I was today working on adding all the proofreading suggestions and > fixing it: https://webpreview.fsfe.org/cgi/fsfe.pl?pad=1594 > > We will publish it today > > Best, > > Ana > > On 09/03/2026 06:06, Richard L. Schmeidler wrote: >> You sent the March newsletter for proofreading and translation on >> Friday, March 6. That day, and on Saturday, March 7, I proofread the >> webpreview that you identified in your email. Just after noon my >> time (early evening your time) I sent my suggestions, with my version >> of the xhtml that I had downloaded from the webpreview. My hope was >> that it would be useful to any of you who were working over the weekend. >> >> Many of the suggestions I made related to garbage characters. I was >> not the first one to see them. Just 68 minutes after you sent your >> message, Francisco de Asis Humberto Fernandez Miser wrote in >> response: "Reading the newsletter in a Mo illa Firefox I have found >> sometimes this character †(in ™"you’re", for instance)." >> >> A webpreview seems to be inherently a moving target. This is not a >> complaint, just an observation of the process as I see it. It is now >> Monday, March 9 (just after midnight for me, early morning in >> Europe). When I look at the webpreview now, >> >> The garbage characters have now gotten worse. I have done a diff >> between the xhtml of the version of the webpreview that I downloaded >> on Friday and the current version. Here are the first few differences: >> >> 6c6 >> < <title>It’s about our community</title> >> --- >> > <title>It’s about our community</title> >> 11c11 >> < <h1>It’s about our community</h1> >> --- >> > <h1>It’s about our community</h1> >> 28c28 >> < <h3>I Love Free Software Day 2026†</h3> >> --- >> > <h3>I Love Free Software Day 2026†</h3> >> 37c37 >> < <p>For the 2026 celebration, and under the motto “Maintainers Matter†, >> --- >> > <p>For the 2026 celebration, and under the motto “Maintainers Matter†, >> All the differences seem to be this kind of expansion. >> >> ===== >> >> But it gets worse. The same kind of garbage characters seem to have >> infected the email in which I made my suggestions on Saturday. I am >> noting these infections in the copy of that email below. (It is >> conceivable that a few of these may be my fault, but I am confident >> that most of them are not, that they are mistranscriptions of special >> characters that are not what I typed.) >> >> I hope that you will send out a new draft (or make improvements to >> the webpreview) so that I will be able to do additional proofreading >> before you publish the newsletter on Tuesday. >> >> On Sat, Mar 7, 2026 at 12:40 PM Richard L. Schmeidler >> <[email protected]> wrote: >> >> I have proofread the webpreview, and attach a version with my >> suggestions. My file is generated from the xhtml generated by the >> webpreview, but it is in .odt format to get the benefit of >> highlighting my suggestions with the LibreOffice Track Changes >> feature. >> >> I am making the effort to do this quickly enough that you and the >> translators will be able to work on it over the weekend as well as >> on Monday, before it is published on Tuesday. >> >> >> 1. (BOTH Title and Heading) "It’s about our community" >> Replace "It’s" with "It's" BOTH times. >> >> 2. Figure alt text: "Graphic for the FSFE newsletter with the >> FSFE logo, a I Love Free Software collage that includes thank you >> cards, comic panels, a group photo and on the bottom, a picture >> with books of Ada and Zangemann and the Router Freedom icon" >> Replace the first occurrence of "a" (before "I") with "an." >> English grammar. >> >> 3. Heading: "I Love Free Software Day 2026â" Remove "â". >> >> 4. "Every year on 14 February and in the days around it, we come >> together, online and in person, to express their appreciation to >> everyone part of the Free Software communities." >> >> (a) Replace "their" with "our." Since the pronoun used as the >> subject of the verb "come" is "we," the corresponding possessive >> pronoun should be used for "appreciation." >> >> (b) Insert "who is" after "everyone." English usage. >> >> >> I think that the versions of the special characters around the phrase >> Maintainers Matter may be corrupted, but I can't tell. >> >> 5. "For the 2026 celebration, and under the motto “Maintainers >> Matter†, our communities organised 22 events across 12 >> different European countries, reaching more than 300 people >> offline." >> >> >> I see several corruptions in the sentence that follows. The first >> quoted character that now is shown with a TM in it is corrupted, and >> the quoted phrase should have zero or two corrupted characters >> shown. But this latter may be an error on my part. >> >> Replace "’" with a single quotation mark BOTH times, before and >> after "€œMaintainers Matter." A single quotation mark can look >> like an apostrophe, or can be curved -- subtly different for the >> beginning and ending quotation marks. >> >> >> The corrupted characters in the text that I quoted and my suggestion >> are clearly inconsistent, so that there has been further corruption. >> >> 6. "For the first time, the celebration also reached the front >> page of Hacker News, thanks to a “thank you†blog post by >> Matthias Kirschner" >> >> (a) This is just a suggertion. Do you want to put in a link to >> the front page of Hacker News? I an not attempting to do this in >> my version. >> >> (b) Replace "’" with a single quotation mark BOTH times, >> before and after "thank you." See my #5, above, for a discussion >> of single quotation marks. >> >> 7. 'For our I Love Free Software Day podcast episode w<a >> href="/news/podcast/2026/episode-47.html">e have spoken with >> Lorenz Kästle from the monitoring plugins</a>.' >> >> (a) The link covers text starting in the middle of the word "we" >> and continuing to the end of the sentence. I suggest having the >> link just on the words "podcast episode." I hope that I have >> done this correctly in my version. Other corrections are possible. >> >> (b) I have no idea what "monitoring plugins" means, nor how Mr. >> Kastle can be "from . . .plugins." I think this should be >> rewritten, but I have not attempted to rewrite this in my >> version, which would require me to listen to the podcast. That is >> not an appropriate task for a proofreader working against a deadline. >> >> (c) Replace "ä" with "a". I hope that this is the correct >> spelling of the name. If not, do it correctly. >> >> 8. [this is the link text] "interoperability compliance under >> the EU’s Digital Markets Act (DMA) and mobile phones" Replace >> "EU’s" with "EU's". >> >> 9. "During FOSDEM 2026, we also held a Q&A session on the >> Cyber Resilience Act together with a representative of the German >> market >> surveillance authority and the European Commission as there are >> still uncertainties and recurring questions." >> >> (a) I suggest adding commas before and after "together with a >> representative of the German market surveillance authority and >> the European Commission." (These commas are not compulsory, but >> I think that they make the sentence clearer.) >> >> (b) This is a question, not a suggestion, since I have not tried >> to research the FOSDEM session. Was the Q&A session held with one >> person who represented both organizations, or with two >> representatives, one from each organization? The present text >> says that there was just one representative. If there were two >> representatives, you should replace "a representative" with >> "representatives." >> >> 10. "There, we talked about the role of the steward as people >> are still unsure whether and under what circumstances they should >> or want to become a steward." I suggest replacing "or want to" >> with "- or might want to -" (I have used hyphens as short >> dashes). I think that this makes the sentence clearer, both by >> indicating the uncertainty as to desiring to take on the work, >> and as more clearly distinguishing mandatory from voluntary work. >> >> >> Obviously, the replacement should have an apostrophe, rather than the >> corrupted character. >> >> 11. "Google’s plan would mean that all personal data of Free >> Software app developers on Android would end up with Google" >> Replace "Google’s" with "Google'€™s." >> >> >> Obviously, the replacement should have a hyphen, rather than the >> corrupted character. >> >> 12. "arbitrary bans against privacy‑protecting and critical >> apps" Replace "privacy‑protecting" with "privacy-€‘protecting." >> >> 13. "What the letter asks Google is to rescind the mandatory >> developer registration for all third‑party distribution, to >> engage in transparent dialogue with civil society, Free Software >> communities, and regulators on improving security without >> sacrificing openness, and committing to platform neutrality so >> that Google’s role as Android steward does not conflict with >> its commercial interests." >> >> >> Obviously, the replacement should have a hyphen, rather than the >> corrupted character. >> >> (a) Replace "third‑party" with "third-€‘party." >> >> (b) Replace "committing" with "to commit." This rather long >> sentence combines clauses that have different forms. >> >> >> Obviously, the replacement should have an apostrophe, rather than the >> corrupted character. >> >> (c) Replace "Google’s" with "Google'€'s." >> >> 14. Heading: "From Ada’s workshop" Replace "Ada’s" with >> "Ada'€'s >> >> 15. "Ada og Zangemann – En fortelling om programvare, >> rullebrett og bringebæris" I suspect that the same sort of >> corruption of punctuation and spelling that I have been >> encountering has affected this Norwegian title, as it has >> affected so much of this webpreview. In particular, I have doubts >> about "â" and "bringebæris." However, I have no idea what the >> correct punctuation and spelling should be. Someone who has >> access to the Norwegian title should correct this. >> >> 16. "an Ada & Zangemann reading session in Frech took place >> alongside a small Ada-themed game." Replace "Frech" with "French." >> >> 17. Last but not least, if you are in Germany and coming to >> Chemnitzer Linux-Tage 2026 >> <https://fsfe.org/events/index.en.html#event-20260328-01> , come >> by to say hi!" I suggest replacing 'hi!' with ' "Hi!" ' >> >> (a) Since you are quoting the greeting, it is customary in >> English to enclose it in quotation marks. (There is a discussion >> of quotation marks in my #5, above.) >> >> (b) It is customary in English to capitalize the first word of a >> quoted full sentence, even if the sentence is just a one-word >> greeting. (Here "hi!" is clearly a quoted full sentence, not >> just a single quoted word, since the terminating punctuation of >> the sentence is quoted.} >> >> >> Obviously, the replacement should have an apostrophe, rather than the >> corrupted character. >> >> 18. "We may be behind the wheel, but you’re the ones keeping >> us moving forward." Replace "you’re" with "you'€™re." >> >> >> On Fri, Mar 6, 2026 at 8:51 AM Ana Galan <[email protected]> wrote: >> >> Dear translators, >> >> our newsletter is ready for your proofreading and translation: >> >> https://webpreview.fsfe.org/cgi/fsfe.pl?pad=1594 >> >> We will publish it next Tuesday. >> >> Best and have a great weekend! >> >> Ana >> >> -- >> >> _______________________________________________ >> Translators mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> >> This mailing list is covered by the FSFE's Code of Conduct. All >> participants are kindly asked to be excellent to each other: >> https://fsfe.org/about/codeofconduct >> >> >> >> -- >> "The problem with quotes on the internet is that it is difficult >> to determine whether or not they are genuine." -- Abraham Lincoln >> >> >> >> -- >> "The problem with quotes on the internet is that it is difficult to >> determine whether or not they are genuine." -- Abraham Lincoln > -- > > Ana Galan (she/her) - Senior Project Manager Communications > Free Software Foundation Europe > Revaler Str. 19, 10245 Berlin, Germany | t:+49 157 92 34 72 12 > Registered at Amtsgericht Hamburg, VR 17030 > > > Support the FSFE:https://my.fsfe.org/donate > Stay in the loop! Subscribe for updates:https://fsfe.org/subscribe > Follow us on the Fediverse: @[email protected] > > _______________________________________________ > Translators mailing list [email protected] > To unsubscribe send an email [email protected] > > This mailing list is covered by the FSFE's Code of Conduct. All > participants are kindly asked to be excellent to each other: > https://fsfe.org/about/codeofconduct --------------LGBAZDvOGKNFRS0WTwLPjM1B Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <p>Hola, Ana:</p> <p>I still see some weird stuff around <span style="color: rgb(51, 51, 51); font-family: roboto, "noto emoji", "noto sans symbols", "noto sans symbols 2", sans-serif; font-size: 17.6px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">"Maintainers Matter", and "Thank Your".</span></p> <p><span style="color: rgb(51, 51, 51); font-family: roboto, "noto emoji", "noto sans symbols", "noto sans symbols 2", sans-serif; font-size: 17.6px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">Regards!</span></p> <div class="moz-cite-prefix">El 10/03/2026 a las 9:48, Ana Galan escribió:<br> </div> <blockquote type="cite" cite="mid:[email protected]"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <p>Dear all,</p> <p>sorry for all the garbage characters. I have no idea how this happened as my original file is clean of those. Our system hackers are checking our system so it won't happen again.</p> <p>I was today working on adding all the proofreading suggestions and fixing it: <a class="moz-txt-link-freetext" href="https://webpreview.fsfe.org/cgi/fsfe.pl?pad=1594" moz-do-not-send="true">https://webpreview.fsfe.org/cgi/fsfe.pl?pad=1594</a></p> <p>We will publish it today</p> <p>Best,</p> <p>Ana</p> <div class="moz-cite-prefix">On 09/03/2026 06:06, Richard L. Schmeidler wrote:<br> </div> <blockquote type="cite" cite="mid:CAKbK2ayqeNPLnQJdTO8P7UJb37A5LYbrbn9uBrtHO6c2NMoSzg@mail.gmail.com"> <div dir="ltr"> <div dir="ltr">You sent the March newsletter for proofreading and translation on Friday, March 6. That day, and on Saturday, March 7, I proofread the webpreview that you identified in your email. Just after noon my time (early evening your time) I sent my suggestions, with my version of the xhtml that I had downloaded from the webpreview. My hope was that it would be useful to any of you who were working over the weekend.</div> <div dir="ltr"><br> </div> <div>Many of the suggestions I made related to garbage characters. I was not the first one to see them. Just 68 minutes after you sent your message, Francisco de Asis Humberto Fernandez Miser wrote in response: "Reading the newsletter in a Mo illa Firefox I have found sometimes this character †(in ™"you’re", for instance)."</div> <div><br> </div> <div>A webpreview seems to be inherently a moving target. This is not a complaint, just an observation of the process as I see it. It is now Monday, March 9 (just after midnight for me, early morning in Europe). When I look at the webpreview now, <br> </div> <br> <div>The garbage characters have now gotten worse. I have done a diff between the xhtml of the version of the webpreview that I downloaded on Friday and the current version. Here are the first few differences:</div> <div><br> </div> <div> <pre>6c6 < <title>It’s about our community</title> --- > <title>It’s about our community</title> 11c11 < <h1>It’s about our community</h1> --- > <h1>It’s about our community</h1> 28c28 < <h3>I Love Free Software Day 2026†</h3> --- > <h3>I Love Free Software Day 2026†</h3> 37c37 < <p>For the 2026 celebration, and under the motto “Maintainers Matter†, --- > <p>For the 2026 celebration, and under the motto “Maintainers Matter†,</pre> </div> <div>All the differences seem to be this kind of expansion. <br> </div> <div><br> </div> <div>=====</div> <div><br> </div> <div>But it gets worse. The same kind of garbage characters seem to have infected the email in which I made my suggestions on Saturday. I am noting these infections in the copy of that email below. (It is conceivable that a few of these may be my fault, but I am confident that most of them are not, that they are mistranscriptions of special characters that are not what I typed.)<br> </div> <div><br> </div> <div>I hope that you will send out a new draft (or make improvements to the webpreview) so that I will be able to do additional proofreading before you publish the newsletter on Tuesday.<br> </div> <div><br> </div> <div class="gmail_quote gmail_quote_container"> <div dir="ltr" class="gmail_attr">On Sat, Mar 7, 2026 at 12:40 PM Richard L. Schmeidler <<a href="mailto:[email protected]" moz-do-not-send="true" class="moz-txt-link-freetext">[email protected]</a>> wrote:<br> </div> <blockquote class="gmail_quote"> <div dir="ltr"> <div dir="ltr">I have <span>proofread</span> the webpreview, and attach a version with my<br> suggestions. My file is generated from the xhtml generated by the<br> webpreview, but it is in .odt format to get the benefit of<br> highlighting my suggestions with the LibreOffice Track Changes<br> feature.<br> <br> I am making the effort to do this quickly enough that you and the<br> translators will be able to work on it over the weekend as well as </div> <div dir="ltr">on Monday, before it is published on Tuesday. <br> </div> <div dir="ltr"><br> <div><br> </div> <div>1. (BOTH Title and Heading) "It’s about our community" Replace "It’s" with "It's" BOTH times. </div> <div><br> </div> <div>2. Figure alt text: "Graphic for the FSFE newsletter with the FSFE logo, a I Love Free Software collage that includes thank you cards, comic panels, a group photo and on the bottom, a picture with books of Ada and Zangemann and the Router Freedom icon" Replace the first occurrence of "a" (before "I") with "an." English grammar. <br> </div> <div><br> 3. Heading: "I Love Free Software Day 2026â" Remove "â".</div> <div><br> </div> <div>4. "Every year on 14 February and in the days around it, we come together, online and in person, to express their appreciation to everyone part of the Free Software communities."</div> <div><br> </div> <div>(a) Replace "their" with "our." Since the pronoun used as the subject of the verb "come" is "we," the corresponding possessive pronoun should be used for "appreciation."<br> </div> <div><br> </div> <div>(b) Insert "who is" after "everyone." English usage.</div> <div><br> </div> </div> </div> </blockquote> <div><br> </div> <div>I think that the versions of the special characters around the phrase Maintainers Matter may be corrupted, but I can't tell.<br> </div> <div> </div> <blockquote class="gmail_quote"> <div dir="ltr"> <div dir="ltr"> <div>5. "For the 2026 celebration, and under the motto “Maintainers Matter†, our communities organised 22 events across 12 different European countries, reaching more than 300 people offline." </div> </div> </div> </blockquote> <div><br> </div> <div>I see several corruptions in the sentence that follows. The first quoted character that now is shown with a TM in it is corrupted, and the quoted phrase should have zero or two corrupted characters shown. But this latter may be an error on my part.<br> </div> <div> </div> <blockquote class="gmail_quote"> <div dir="ltr"> <div dir="ltr"> <div>Replace "’" with a single quotation mark BOTH times, before and after "€œMaintainers Matter." A single quotation mark can look like an apostrophe, or can be curved -- subtly different for the beginning and ending quotation marks. <br> </div> <div><br> </div> </div> </div> </blockquote> <div><br> </div> <div>The corrupted characters in the text that I quoted and my suggestion are clearly inconsistent, so that there has been further corruption.<br> </div> <div> </div> <blockquote class="gmail_quote"> <div dir="ltr"> <div dir="ltr"> <div>6. "For the first time, the celebration also reached the front page of Hacker News, thanks to a “thank you†blog post by Matthias Kirschner"</div> <div><br> </div> <div>(a) This is just a suggertion. Do you want to put in a link to the front page of Hacker News? I an not attempting to do this in my version.</div> <div><br> </div> <div>(b) Replace "’" with a single quotation mark BOTH times, before and after "thank you." See my #5, above, for a discussion of single quotation marks.</div> <div><br> </div> <div>7. 'For our I Love Free Software Day podcast episode w<a href="/news/podcast/2026/episode-47.html">e have spoken with Lorenz Kästle from the monitoring plugins</a>.' <br> </div> <div><br> </div> <div>(a) The link covers text starting in the middle of the word "we" and continuing to the end of the sentence. I suggest having the link just on the words "podcast episode." I hope that I have done this correctly in my version. Other corrections are possible.<br> </div> <div><br> </div> <div>(b) I have no idea what "monitoring plugins" means, nor how Mr. Kastle can be "from . . .plugins." I think this should be rewritten, but I have not attempted to rewrite this in my version, which would require me to listen to the podcast. That is not an appropriate task for a proofreader working against a deadline.</div> <div><br> </div> <div>(c) Replace "ä" with "a". I hope that this is the correct spelling of the name. If not, do it correctly.<br> </div> <br> 8. [this is the link text] "interoperability compliance under the EU’s Digital Markets Act (DMA) and mobile phones" Replace "EU’s" with "EU's".</div> <div dir="ltr"><br> </div> <div dir="ltr">9. "During FOSDEM 2026, we also held a Q&amp;A session on the Cyber Resilience Act together with a representative of the German market<br> <div>surveillance authority and the European Commission as there are still uncertainties and recurring questions."</div> <div><br> </div> <div>(a) I suggest adding commas before and after "together with a representative of the German market surveillance authority and the European Commission." (These commas are not compulsory, but I think that they make the sentence clearer.)</div> <div><br> </div> <div>(b) This is a question, not a suggestion, since I have not tried to research the FOSDEM session. Was the Q&A session held with one person who represented both organizations, or with two representatives, one from each organization? The present text says that there was just one representative. If there were two representatives, you should replace "a representative" with "representatives."</div> <div><br> </div> <div>10. "There, we talked about the role of the steward as people are still unsure whether and under what circumstances they should or want to become a steward." I suggest replacing "or want to" with "- or might want to -" (I have used hyphens as short dashes). I think that this makes the sentence clearer, both by indicating the uncertainty as to desiring to take on the work, and as more clearly distinguishing mandatory from voluntary work. </div> <br> </div> </div> </blockquote> <div><br> </div> <div>Obviously, the replacement should have an apostrophe, rather than the corrupted character.<br> </div> <div> </div> <blockquote class="gmail_quote"> <div dir="ltr"> <div dir="ltr">11. "Google’s plan would mean that all personal data of Free Software app developers on Android would end up with Google" Replace "Google’s" with "Google'€™s."</div> <div dir="ltr"><br> </div> </div> </blockquote> <div><br> </div> <div>Obviously, the replacement should have a hyphen, rather than the corrupted character.</div> <div> </div> <blockquote class="gmail_quote"> <div dir="ltr"> <div dir="ltr">12. "arbitrary bans against privacy‑protecting and critical apps" Replace "privacy‑protecting" with "privacy-€‘protecting." <div><br> </div> <div>13. "What the letter asks Google is to rescind the mandatory developer registration for all third‑party distribution, to engage in transparent dialogue with civil society, Free Software communities, and regulators on improving security without sacrificing openness, and committing to platform neutrality so that Google’s role as Android steward does not conflict with its commercial interests."</div> <div><br> </div> </div> </div> </blockquote> <div><br> </div> <div>Obviously, the replacement should have a hyphen, rather than the corrupted character.</div> <div> </div> <blockquote class="gmail_quote"> <div dir="ltr"> <div dir="ltr"> <div>(a) Replace "third‑party" with "third-€‘party."</div> <div><br> </div> <div>(b) Replace "committing" with "to commit." This rather long sentence combines clauses that have different forms.<br> </div> <div><br> </div> </div> </div> </blockquote> <div><br> </div> <div>Obviously, the replacement should have an apostrophe, rather than the corrupted character.</div> <div> </div> <blockquote class="gmail_quote"> <div dir="ltr"> <div dir="ltr"> <div>(c) Replace "Google’s" with "Google'€'s."<br> </div> <div><br> </div> 14. Heading: "From Ada’s workshop" Replace "Ada’s" with "Ada'€'s</div> <br> 15. "Ada og Zangemann – En fortelling om programvare, rullebrett og bringebæris" I suspect that the same sort of corruption of punctuation and spelling that I have been encountering has affected this Norwegian title, as it has affected so much of this webpreview. In particular, I have doubts about "â" and "bringebæris." However, I have no idea what the correct punctuation and spelling should be. Someone who has access to the Norwegian title should correct this.<br> <div dir="ltr"><br> </div> <div dir="ltr">16. "an Ada &amp; Zangemann reading session in Frech took place alongside a small Ada-themed game." Replace "Frech" with "French."</div> <div dir="ltr"><br> </div> <div dir="ltr">17. Last but not least, if you are in Germany and coming to <a href="https://fsfe.org/events/index.en.html#event-20260328-01" target="_blank" moz-do-not-send="true">Chemnitzer Linux-Tage 2026</a> , come by to say hi!" I suggest replacing 'hi!' with ' "Hi!" '<br> </div> <div dir="ltr"><br> </div> <div>(a) Since you are quoting the greeting, it is customary in English to enclose it in quotation marks. (There is a discussion of quotation marks in my #5, above.) <br> </div> <div><br> </div> <div>(b) It is customary in English to capitalize the first word of a quoted full sentence, even if the sentence is just a one-word greeting. (Here "hi!" is clearly a quoted full sentence, not just a single quoted word, since the terminating punctuation of the sentence is quoted.}<br> </div> <div dir="ltr"> <div><br> </div> </div> </div> </blockquote> <div><br> </div> <div>Obviously, the replacement should have an apostrophe, rather than the corrupted character.</div> <div> </div> <blockquote class="gmail_quote"> <div dir="ltr"> <div dir="ltr"> <div>18. "We may be behind the wheel, but you’re the ones keeping us moving forward." Replace "you’re" with "you'€™re."</div> <div><br> </div> </div> <br> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Fri, Mar 6, 2026 at 8:51 AM Ana Galan <<a href="mailto:[email protected]" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">[email protected]</a>> wrote:<br> </div> <blockquote class="gmail_quote"> <div> <p>Dear translators,</p> <p>our newsletter is ready for your proofreading and translation:</p> <p><a href="https://webpreview.fsfe.org/cgi/fsfe.pl?pad=1594" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://webpreview.fsfe.org/cgi/fsfe.pl?pad=1594</a></p> <p>We will publish it next Tuesday.</p> <p>Best and have a great weekend!</p> <p>Ana</p> <pre cols="72">-- </pre> </div> _______________________________________________<br> Translators mailing list -- <a href="mailto:[email protected]" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">[email protected]</a><br> To unsubscribe send an email to <a href="mailto:[email protected]" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">[email protected]</a><br> <br> This mailing list is covered by the FSFE's Code of Conduct. All<br> participants are kindly asked to be excellent to each other:<br> <a href="https://fsfe.org/about/codeofconduct" rel="noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://fsfe.org/about/codeofconduct</a></blockquote> </div> <div><br> </div> <br> <span class="gmail_signature_prefix">-- </span><br> <div dir="ltr" class="gmail_signature">"The problem with quotes on the internet is that it is difficult to determine whether or not they are genuine." -- Abraham Lincoln</div> </div> </blockquote> </div> <div><br> </div> <br> <span class="gmail_signature_prefix">-- </span><br> <div dir="ltr" class="gmail_signature">"The problem with quotes on the internet is that it is difficult to determine whether or not they are genuine." -- Abraham Lincoln</div> </div> </blockquote> <pre class="moz-signature" cols="72">-- Ana Galan (she/her) - Senior Project Manager Communications Free Software Foundation Europe Revaler Str. 19, 10245 Berlin, Germany | t:+49 157 92 34 72 12 Registered at Amtsgericht Hamburg, VR 17030 Support the FSFE: <a class="moz-txt-link-freetext" href="https://my.fsfe.org/donate" moz-do-not-send="true">https://my.fsfe.org/donate</a> Stay in the loop! Subscribe for updates: <a class="moz-txt-link-freetext" href="https://fsfe.org/subscribe" moz-do-not-send="true">https://fsfe.org/subscribe</a> Follow us on the Fediverse: @[email protected]</pre> <lt-container></lt-container> <br> <fieldset class="moz-mime-attachment-header"></fieldset> <pre wrap="" class="moz-quote-pre">_______________________________________________ Translators mailing list -- <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> To unsubscribe send an email to <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> This mailing list is covered by the FSFE's Code of Conduct. All participants are kindly asked to be excellent to each other: <a class="moz-txt-link-freetext" href="https://fsfe.org/about/codeofconduct">https://fsfe.org/about/codeofconduct</a></pre> </blockquote> </body> </html> --------------LGBAZDvOGKNFRS0WTwLPjM1B-- --===============1862851631429451227== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Translators mailing list -- [email protected] To unsubscribe send an email to [email protected] This mailing list is covered by the FSFE's Code of Conduct. All participants are kindly asked to be excellent to each other: https://fsfe.org/about/codeofconduct --===============1862851631429451227==--