Added Romanian translations.

[jladage]

Just added translations for Romanian language.

[icemac]

Thank you for your contribution.

According to the contributing policies of the zopefoundation organization you need to sign a contributor agreement before any non-trivial change can be merged. For details please consult the Contributing guidelines for zopefoundation projects.

[icemac]

@MrTango Is your Romanian good enough to review these translations?

[jladage]

Hi Micheal,I signed a contributing license for Plone in 2007. Will that do? Or do you want a new one just for Zope which uses Plone’s as I understand.Kind regards,Jean-Paul LadageOn 13 Aug 2024, at 07:08, Michael Howitz ***@***.***> wrote: @MrTango Is your Romanian good enough to review these translations? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[icemac]

@jladage When you sign a Zope contributor agreement, you will get a Member of the zopefoundation project, this is the way I see that the agreement was signed and it will allow you to merge yout PR after successful review.

So I cannot answer your question. I'd suggest either to ask someone of the Plone Foundation or just sign a contributor agreement for Zope.

[icemac]

@jladage You are now listed as Member are you also able to merge yourself?

[jladage]

@icemac nope, at least not if nobody is able to review the Romanian translations I created with deepl.

[davisagli]

@avoinea Would you like to help review this or ask someone else to?

[jladage]

Hi @avoinea, I merged your translation suggestions. Could you please review once more so I can merge?

[jladage]

@icemac the test coverage is currently blocking this request from merging. I'm not familiar enough with the code to understand why. Do we test translations? Are our changes the result of the test coverage problem?

[icemac]

@jladage The translations are not part of the coverage and are not tested. I saw a drop in coverage on serveral packages, probably because of a new version of the coverage package.

I'll merge this PR now and tackle the coverage problem later on.