Glossary entry (derived from question below)
Spanish term or phrase:
Sin perjuicio de lo anteriormente expuesto
English translation:
Notwithstanding the aforementioned,
Spanish term
Sin perjuicio de lo anteriormente expuesto
Sin perjuicio de lo anteriormente expuesto, "EL COMPRADOR" quedará liberado de todas sus obligaciones derivadas del Compromiso de Inversión acordado, en el caso que
cumpliese con pagar anticipadamente a "EL PROVEEDOR", el importe total
correspondiente al precio pactado entre ambos por el valor de Ia concesion minera Abundia-1 ($500,000) QUINIENTOS MIL DÓLARES AMERICANOS.
4 +1 | Notwithstanding the aforementioned, | Déborah Gelardi |
4 +1 | Without prejudice to the above | David Hollywood |
4 | However | philgoddard |
4 | notwithstanding anything herein to the contrary | Robert Copeland |
Jul 18, 2020 11:37: patinba changed "Level" from "PRO" to "Non-PRO"
PRO (3): Toni Castano, Déborah Gelardi, Robert Carter
Non-PRO (3): Joshua Parker, TechLawDC, patinba
When entering new questions, KudoZ askers are given an opportunity* to classify the difficulty of their questions as 'easy' or 'pro'. If you feel a question marked 'easy' should actually be marked 'pro', and if you have earned more than 20 KudoZ points, you can click the "Vote PRO" button to recommend that change.
How to tell the difference between "easy" and "pro" questions:
An easy question is one that any bilingual person would be able to answer correctly. (Or in the case of monolingual questions, an easy question is one that any native speaker of the language would be able to answer correctly.)
A pro question is anything else... in other words, any question that requires knowledge or skills that are specialized (even slightly).
Another way to think of the difficulty levels is this: an easy question is one that deals with everyday conversation. A pro question is anything else.
When deciding between easy and pro, err on the side of pro. Most questions will be pro.
* Note: non-member askers are not given the option of entering 'pro' questions; the only way for their questions to be classified as 'pro' is for a ProZ.com member or members to re-classify it.
Proposed translations
Notwithstanding the aforementioned,
Without prejudice to the above
--------------------------------------------------
Note added at 57 mins (2020-07-17 22:35:34 GMT)
--------------------------------------------------
The use of notwithstanding might result in (unintended) ambiguities; when a third contract clause refers to a section that is itself subordinate to another clause, which uses notwithstanding: in that case it might be uncertain whether the prevailing clause (i.e. in which the reference notwithstanding was made) is intended to be captured by such third contract clause. If the section referred to in the third contract clause is subordinated to another clause by using subject to, the ambiguity does not occur because in that case it is clear that the subordinated section is limited by that other clause as well (since the subordinated clause says so itself).
--------------------------------------------------
Note added at 1 hr (2020-07-17 22:39:08 GMT)
--------------------------------------------------
“Notwithstanding” looks back to the main rule.
It is used in a clause that is to take priority over
another clause. It tells the reader that the subject
clause overrides the clause(s) to which it refers.
It is, in effect, the opposite of “subject to”.
--------------------------------------------------
Note added at 1 hr (2020-07-17 22:41:06 GMT)
--------------------------------------------------
"without prejudice to"
This expression is used in a clause where
there is to be no priority given over another
clause. It tells the reader that the clause in
which the expression appears does not affect
the clause to which it refers.
agree |
Robert Carter
: Spot on with those references. "Notwithstanding" (i.e., overriding the above) is actually the opposite of "Sin perjuicio de" (subordinate to the above).
7 hrs
|
well used to this Robert so no worries... thanks for the confirmation though :)
|
Something went wrong...