Spanish readme v0.9.1 clean - #80
Conversation
|
OMG, this is fantastic!!! 🍻 Thanks for the rework. The formatting problems from the last one are gone: no leftover conversion markers, no duplicated sections, and the section count now matches the English README. CI is green. I am also going to close #75, since this replaces it. Two changes I would like before it goes in. Terminology. The Spanish already on main uses "peluca" for wig and "Armario" for Closet. This version uses "perfil" and "Colección" throughout. I get why, since profile and collection are plainer words, but the hair vocabulary is the product's naming rather than decoration, and I would rather keep it. Same thing in the Fitting section, which is headed "Validación" here. Fitting and combing are two different things in HAIR, and one word covering both will confuse people later. Section order. Combing comes before Fitting in the English, lines 330 and 350. In this file they are reversed: line 831 is the fitting section and 903 is combing. The headings match their own text so nothing reads wrong, I would just like the two files in the same order so they stay easy to compare. Now the bigger thing, and I want to be straight with you about it rather than have you find out later that I signed you up for more than you expected. HAIR moves fast. Eleven releases between July 20 and July 31, and the English README changed five times in the last four days. Up to now the translated READMEs have been short summaries, which is why I have been able to keep all ten in sync myself as part of each release. A full Spanish translation is a different commitment. It becomes the one language of the ten that I cannot maintain on my own. I still want to take it, but only on terms that do not quietly turn into a second job for you. The file gets a line at the top saying which English version it was translated from, so when Spanish is behind, the reader knows and nobody is misled. Translation never blocks a release. I ship, and Spanish catches up when it catches up. When English changes I will drop the new English text into the Spanish file in place, marked as pending, rather than machine-translating it. You would be translating fresh text instead of cleaning up after a machine, and it keeps the hair vocabulary intact, which is the first thing automatic translation gets wrong. You translate in batches on your own schedule, not per release. Monthly, at version boundaries, whatever fits around your life. I will set up one tracking issue that collects the English changes so you have a single place to look instead of watching the whole repo. And the part people usually leave unsaid: if you get busy or lose interest, say so or just go quiet, and I will fall back to the short summary. No hard feelings and no explanation needed. I would rather agree to that now than have it be awkward in six months. Does that work for you, and what cadence suits you? If it sounds like more than you want to take on, say so and I will go the short-summary route instead. The work you have already done is good and I am not trying to talk you out of anything. I just want you going in with clear eyes. Thoughts? ~ DAB |
Release 0.10.0, Remotes Have Been Buffed. Branch trigger-styling onto main, squash merge. What is in it: Devices and Remotes as two sections; USE on every set of codes to make a Device or a Remote; Make a Remote from a Device and Make a Device from a Remote; each Remote is its own Home Assistant device with device triggers; pinning a Remote to Devices with echo defense, loop breaker and coalescing; air-conditioner Remotes with the STATE MATRIX card in listen mode, LAST HEARD, state triggers and the "State heard" device trigger; the climate preset star; the add tile with file drop; the Mirror emitter filter; settings and header alignment; ten languages. Behind it: one identity form for wig cells (wire form, backfilled); a persisted cell index; receiver-tolerant matching for file-sourced codes (normalized fingerprint as a lowest tier for cells, wig, Clipper and Plucker triggers, and wig-adopted commands; echo ticket carries it too); trigger dedup anchored at 300 ms keyed on trigger id with allow and suppress log lines; Clipper and Plucker triggers stamped clip and plucked and treated as file-sourced, with a load-time backfill. Docs: README, CHANGELOG 0.10.0 entry, info.md, llms.txt, nine translated README stamps, manifest and panel footer 0.10.0 with the bundle rebuilt. Verification: full suites green (3.12: 2998 passed, 34 skipped; 3.14: 3061 passed, 1 skipped), ruff clean; a real-air regression bench on the release candidate with an ESPHome transmitter and an Athom receiver, thirty presses through a pinned pair with zero echo leaks, three restarts, two receivers one press, zero HAIR warnings; eight-hour soak running. No community issue closed by this release. PR #80 (Spanish README) is unrelated and stays open.
2 participants
What
Updates
README.es.mdwith the full Spanish README, brought up to date with HAIR v0.9.1.Includes the documentation added for v0.9.1 while preserving the previously reviewed Spanish translation.
Why
The Spanish README was still based on v0.8.9 and needed to catch up with the current release.
How
Updated only
README.es.md, keeping the structure and GitHub Markdown formatting aligned with the English README and incorporating the new v0.9.1 documentation.Type of Change
Checklist
pytestpasses locallyruff check .passes locallynpm run buildinfrontend/)llms.txtaccordingly.Screenshots
Not applicable.
Related Issues
None.