Skip to content

Conversation

@UkoeHB
Copy link
Contributor

@UkoeHB UkoeHB commented Jul 24, 2025

@netlify
Copy link

netlify bot commented Jul 24, 2025

Deploy Preview for barolo-time-757cf9 ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit b5eca1a
🔍 Latest deploy log https://app.netlify.com/projects/barolo-time-757cf9/deploys/6882bd17d535430008aa3db7
😎 Deploy Preview https://deploy-preview-2502--barolo-time-757cf9.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

@nahuhh nahuhh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't read Italian (supposedly), but the PR LGTM

@baro77
Copy link
Contributor

baro77 commented Jul 25, 2025

Hi! I'm Italian mother-tongue. I haven't enough spare time to read everything, but I spot-checked it.
Of course translating always conveys style and register choices, especially from a dry language as English to a rich-of-flavours-one as Italian, and I do not agree with everything: for example I'm not sure if I would have translated some "keywords" often occurring in bibliography, e.g. "Range proofs" becoming "Prove di intervallo" in 5.5. The rationale for this idea of mine is that I think translations should help to understand glueing concepts linking the many elements, not to find an Italian word for everything, because you will always find "Range proofs" around the Internet but I'm not sure -even limiting the research to Italian contents- that every Italian would translate it as "Prove di intervallo" instead of -e.g.- "Dimostrazione di intervallo". In the end, it's a matter of lack (as far as I know) of official recognized translation of cuting-edge tech terms, and I would keep them in English: but given there are no best practices it's definitely a matter of tastes and not a @everoddandeven fault. Even because overall Italian translation is definitely ok and understandable given the technical nature of the document. Formatting as well seems consistent with original english document, so my opinion is that the PR can be merged, and my point could be evaluated for future versions of the translation. BTW, I haven't checked: of course translation (in other languages as well) inherit original document version, but I wonder if -generally speaking- it would be useful to have a translation versioning as well
Always happy to see (new?) Italian contributors :-) (y)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants