This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
Freelance translator and/or interpreter, Verified site user
Data security
This person has a SecurePRO™ card. Because this person is not a ProZ.com Plus subscriber, to view his or her SecurePRO™ card you must be a ProZ.com Business member or Plus subscriber.
Affiliations
This person is not affiliated with any business or Blue Board record at ProZ.com.
Romanian to English: Model teoretic de reprezentare a domeniului de instruire
Source text - Romanian Din punct de vedere logic, intre conceptele din cadrul unui domeniu de cunoastere pot exista mai multe tipuri de relatii: de ordine ierarhica, de implicatie, de echivalenta, de influenta, etc. Din punct de vedere pedagogic si din perspectiva unui sistem de instruire asistata, doua relatii sunt interesante:
1. relatia de precedenta a conceptelor, care se refera la ordinea de prezentare a acestora in cadrul unui curs interactiv;
2. realtia de contributie dintre concepte, care se refera la contributia (referirea) explicita a unui concept in prezentrea unui alt concept.
Formalizarea matematica a relatiilor pedagogice de mai sus, cu transformarea lor in relatii de incidenta (Pecheanu, 2003), permite contruirea unui model ierarhic de tip latice de concepte formale, pe baza tehnicilor Analizei Formale a Conceptelor (Ganter, 1999).
Modelul rezultat, de tip latice de concepte (formale) exprima relatiile dintre conceptele cursului si relatia de generalizare-specializare, implicita pentru structura matematica de latice completa. Laticea completa conceptelor formale este isomorfica cu o latice completa de Unitati Conceptuale (Pecheanu, 2003), care este structura (modelul) de agregare a conceptelor inrudite din cadrul domeniului de instruire. Acest model de agregare, de tip latice, constituie o Structura de Tranzitie Conceptuala pentru domeniul de instruire (Pecheanu, 2003).
Translation - English From a logical point of view, several types of relations can exist among the concepts within a domain knowledge: hierarchical order, implication, equivalence, influence etc. From a pedagogical point of view and from the point of view of an assisted training system, two such relations are of interest:
1. the concept precedence relation, which refers to the order of presenting the concepts within an interactive course;
2. the relation of contribution between objects, which refers to the contribution (participation) of a concept in the presentation of another concept.
The mathematical formalization of the pedagogical relations above, combined with their transformation into incidence relations (Pecheanu, 2003), allows for the building of a hierarchical lattice-like model of formal concepts, based on Formal Concept Analysis techniques (Ganter, 1999).
The resulting model, a type of (formal) concept lattice, expresses the relations among the course concepts and the generalization-specialization relation, implied by the complete lattice mathematical structure. The formal concept lattice is isomorphic to a complete lattice of Conceptual Units (Pecheanu, 2003), which is the structure (model) of aggregating the related concepts within the domain knowledge. This aggregation, lattice-like, model constitutes a Conceptual Transition Structure for the domain knowledge. (Pecheanu, 2003).
English to Romanian: Database
Source text - English Overview
Ultegra Personal is a single-user, object/relational database designed for mobile and distributed applications. Optimized for small-footprint devices, Ultegra Personal runs in under one megabyte of memory, and can be installed in as little as three megabytes of hard disk space.
With its Ultegra 2000 Navigator interface, data replication functionality, Java support, and compatibility with Ultegra 2000 and popular development tools like DevStudio 2000, Visual Basic, Delphi, and PowerBuilder, Ultegra Personal offers a wide range of options for developing and implementing distributed solutions.
The Ultegra Personal development environment supports seamless interoperability on objects across both SQL and object databases. You can use Ultegra Personal to create compact mobile applications that can access and manipulate SQL data from within an object-oriented GUI, or query instances of a C++ or Java class as if they were rows in a SQL table. The development environment supports Windows NT 3.51 (or higher), Windows 95, Windows 98, and Windows CE.
Translation - Romanian Prezentare generalĺ
Ultegra Personal este o bazĺ de date obiect-rela?ionalĺ mono-utilizator, proiectatĺ pentru aplica?ii mobile ?i distribuite. Optimizatĺ pentru dispozitive cu capacitĺ?i limitate, Ultegra Personal ruleazĺ în mai pu?in de un megaoctet de memorie ?i poate fi instalatĺ în doar trei megaocte?i de spa?iu disc.
Cu interfa?a sa Ultegra 2000 Navigator, cu func?iile de replicare a datelor, cu suportul Java ?i cu compatibilitatea cu Ultegra 2000 ?i cu instrumentele de dezvoltare larg rĺspândite ca DevStudio 2000, Visual Basic, Delphi ?i PowerBuilder, Ultegra Personal oferĺ o gamĺ largĺ de op?iuni pentru dezvoltarea ?i implementarea solu?iilor distribuite.
Mediul de dezvoltare Ultegra Personal suportĺ interoperabilitatea fĺrĺ probleme asupra obiectelor atât din baze de date SQL cât ?i din baze de date obiectuale. Pute?i folosi Ultegra Personal pentru a crea aplica?ii mobile compacte care pot accesa ?i manipula date SQL din cadrul unei interfe?e grafice orientate pe obiecte, sau care pot interoga instan?e ale unei clase C++ sau Java ca ?i cum ar fi fost rânduri într-o tabelĺ SQL. Mediul de dezvoltare suportĺ Windows NT 3.51 (sau o versiune superioarĺ), Windows 95, Windows 98 ?i Windows CE.
English to Romanian: Programming reference (WinHelp format)
Source text - English #$KATLockType Property
{ewc HLP95EN.DLL,DYNALINK,"See Also":"mdproLockType_C"} {ewc HLP95EN.DLL,DYNALINK,"Example":"mdproLockType_X":1} {ewc HLP95EN.DLL,DYNALINK,"Applies To":"mdproLockType_A"} {ewc HLP95EN.DLL,DYNALINK,"Specifics":"mdproLockType_S"}
Indicates the type of locks placed on records during editing.
Settings and Return Values
Sets or returns one of the following LockTypeEnum values.
Constant Description
adLockReadOnly Default. Read-only—you cannot alter the data.
adLockPessimistic Pessimistic locking, record by record—the provider does what is necessary to ensure successful editing of the records, usually by locking records at the data source immediately upon editing.
adLockOptimistic Optimistic locking, record by record—the provider uses optimistic locking, locking records only when you call the Update method.
adLockBatchOptimistic Optimistic batch updates—required for batch update mode as opposed to immediate update mode.
Remarks
Set the LockType property before opening a Recordset to specify what type of locking the provider should use when opening it. Read the property to return the type of locking in use on an open Recordset object. The LockType property is read/write when the Recordset is closed and read-only when it is open.
Providers may not support all lock types. If a provider cannot support the requested LockType setting, it will substitute another type of locking. To determine the actual locking functionality available in a Recordset object, use the Supports method with adUpdate and adUpdateBatch.
The adLockPessimistic setting is not supported if the CursorLocation property is set to adUseClient. If an unsupported value is set, then no error will result; the closest supported LockType will be used instead.
adLockPessimistic Blocare pesimistĺ, înregistrare cu înregistrare—furnizorul face ceea ce este necesar pentru a asigura editarea cu succes a înregistrĺrilor, de obicei blocând înregistrĺrile la nivelul sursei de date imediat dupĺ editare.
adLockOptimistic Blocare optimistĺ, înregistrare cu înregistrare—furnizorul folose?te blocarea optimistĺ, blocând înregistrĺrile doar atunci când apela?i metoda Update.
adLockBatchOptimistic Actualizĺri optimiste pe loturi—necesar? pentru modul de actualizare pe loturi, spre deosebire de modul de actualizare imediatĺ.
Observa?ii
Seta?i proprietatea LockType înainte de a deschide un Recordset pentru a specifica tipul de blocare pe care s? îl foloseascĺ furnizorul în momentul deschiderii. Citi?i proprietatea pentru a ob?ine tipul de blocare în uz pentru un obiect Recordset deschis. Proprietatea LockType este read/write când obiectul Recordset este închis ?i read-only când el este deschis.
Furnizorii pot sĺ nu suporte toate tipurile de bloc?ri. Dacĺ un furnizor nu poate suporta setarea LockType cerutĺ, el va folosi în schimb un alt tip de blocare. Pentru a determina posibilitĺ?ile efective de blocare disponibile într-un obiect Recordset, folosi?i metoda Supports cu parametrii adUpdate ?i adUpdateBatch.
Setarea adLockPessimistic nu este suportatĺ dacĺ proprietatea CursorLocation este setatĺ la valoarea adUseClient. Dac? este setatĺ o valoarea nesuportatĺ, nu va apĺrea nici o eroare; va fi folosit în schimb cel mai apropiat tip de blocare LockType suportat.
Native Romanian speaker, former Google and Yahoo! software engineer. Serial entrepreneur (fintech, edtech, crypto) and open-source software developer. Lived in Silicon Valley 2004 - 2019. Digital nomad since.
At Yahoo! I was lead localization engineer and managed the globalization of several properties, including Flickr and Yahoo! Mail.
Prior to Yahoo!, I translated two books (TCP/IP Unleashed and Building Web Solutions with ASP.NET) and co-wrote three books on C/C++ (in Romanian).
