Re: [docs] [PATCH 4/4] recipe-style-guide: Prune unicode from code example
Niko Mauno <[email protected]> Tue, 28 Jul 2026 09:07:45 +0300
| Newsgroups | org.yoctoproject.lists.docs |
|---|---|
| Message-ID | <[email protected]> |
Hi Quentin, On 7/27/26 8:18 PM, Quentin Schulz wrote: > Hi Niko, >=20 > On 7/27/26 6:35 PM, Niko Mauno via lists.yoctoproject.org wrote: >> [You don't often get email from=20 >> [email protected]. Learn why this is important= =20 >> at https://aka.ms/LearnAboutSenderIdentification ] >> >> From: Niko Mauno <[email protected]> >> >> Copy-pasting example segment containing unicode characters causes >> breakage like: >> >> =C2=A0=C2=A0 ERROR: ParseError at .../foobar.bb:158: unparsed line: 'RDE= PENDS:=20 >> ${PN} =3D =E2=80=9Cfoo=E2=80=9D' >> >> therefore replace the unicode characters in the example with regular >> ASCII characters. >> >=20 > There's one additional location where we use those special characters,=20 > in documentation/contributor-guide/identify-component.rst, would you=20 > mind sending a patch for this as well please? Certainly, I have now submitted a new patch for fixing that particular=20 issue also >=20 > I think it'd be nice to add a check in pre-commit such that those=20 > characters never (well, if one runs pre-commit :) ) make it to the docs=20 > again. Is this something you'd be interested in looking into maybe? >=20 This sounds interesting, let me see if I could whip up such new=20 pre-commit feature with LLM. -Niko > Reviewed-by: Quentin Schulz <[email protected]> >=20 > Thanks! > Quentin