Romanian translation

[HarrisonNewman]

Hello,

I have completed the Romanian translation for DB Browser for SQLite 1.13.x. I initiated the translation work at the beginning of January, and I have currently translated all 1444 strings in the .ts file.I know i should announce this but i just wasn't sure at all if i will be able to do all the translations or deal with all the technical terms. I am not a professional translator, but I did my best to provide accurate translations. The accuracy of the translations should be at least 95% and completely understandable by native speakers.

I plan on committing and pushing it to github today or tomorrow, but I have a few questions before I do. If I can get some answers, I'll be able to make any necessary modifications and corrections.

I know this might be a lot to read, but I wanted to clarify all or some of the issues I came across. I've made my own decisions for now regarding to the issues. Just need a thumbs up to know everything's good to go. If I do not receive any response in 48 hours, I will consider everything done. These notes will also serve as a helpful resource for any future Romanian translators who may join. I have already reviewed the discussions and related issues, but I have not found any answers to my questions. (If I receive any feedback or replies, I will update the comment fields in the .ts file accordingly.)

Translation Issues

1. In the category for FileExtensionManager, '*.extension' require translation or not?. Currently, it is translated.
2. The translation for 'Passphrase' in the CipherDialog category, "Frază De Acces," does not seem to fit well in the drop-down box(GUI).
3. The translation for 'SQLCipher 3/4 defaults' as "SQLCipher 3 implicite/4 implicite" does not seem fit well on the GUI.
4. In the Application category, there are more words between [ ], but it is unclear if these require translation.
5. It is unclear if terms like 'unix epoch, java epoch, windows DATE, julian day' in the ColumnDisplayFormatDialog should be translated.
6. In the RemotePushDialog category, 'Database name to push to' can be abbreviated to BD (translated) to fit better on the GUI. (currently is abbreviated)
7. In the EditTableDialog category, the word 'parser' does not have a definitive translation for now, maybe it doesn't require translation at all.
8. In the EditTableDialog category, 'PK' has been changed to "CP" as PK stands for "Primary Key" and CP for "Cheie Primară".
9. The translation of '(X) The count(X) function returns a count...' in the SqlUiLexer is not entirely clear. The translation may not be 100% accurate but should be understandable.
10. 'C-language' in the context of '(FORMAT) The printf(FORMAT)' has been translated to 'limbaj-C', but maybe it doesn't require translation.
11. The content within parentheses like '(timestring,modifier,modifier,...)' has been translated in the SqlUiLexer category, but it is unsure if words between parentheses should be translated.
12. The translation of 'Preview only (N/A)' in the PreferencesDialog is not fully visible on the GUI field.
13. 'Organization' in the PreferencesDialog may refer to the organization of things rather than a building. It has been translated as "Organizare" for now, as for building would be "Organizație"
14. The term 'FAQ' in 'SQLCipher FAQ' has not been translated as it is widely understood but a translation is possible.
15. Abbreviating 'database' to "BD" in 'Open Database Read Only' helps with the length in the 'File' tab(GUI content visibility).
16. Translating 'optimize' in the context of 'Runs the optimize pragma...' seems appropriate but "optimize pragma" shouldn't be translated maybe.
17. 'In-Memory database' in the MainWindow category(or other categories) has been translated but it is unclear if 'In-Memory' should be translated.
18. The phrases 'EXECUTING SELECTION IN,' 'EXECUTING LINE IN,' and 'EXECUTING ALL IN' in uppercase should be translated or not? as they are not keywords. Currently all are translated.
19. I have translated 'backup', but I believe it may not require translation as it is commonly used as is by native speakers, and the meaning is clear regardless.
20. Should 'settings_file' be translated or left as is? At the moment, it has been translated.
21. In the FindReplaceDialog category, 'Match exact case', 'Match only whole words', and 'Use regular expressions' do not seem to fit well within the GUI.

Overall

1. I have chosen to keep "dumneavoastră" unabbreviated as "dvs." can be abbreviated (is like Ms. or Mrs.)
2. For "remote," I have used the translated form 'la distanță,' but it can also be 'remote' without translation. I notice that 'remote' is used more frequently by natives.
3. "Index" has been translated as 'indice,' but it can also remain as 'index,' as it is more commonly used by natives.
4. "DB" stands for database, while "BD" is 'bază de date.' It follows the order of 'base' first and 'data' after, thus I have changed the abbreviation order.
5. In Romanian, 'directory/folder' is 'dosar,' although 'folder' is also widely used. I have chosen to translate it as 'dosar' for both 'directory' and 'folder.'
6. I have kept "dock" translated as "doc" for now. I am not certain if 'dock' should be translated or not.
7. "Push" has been translated as "Împinge," but I am unsure if this word should be translated. Some people do not translate it. I think I can also associate 'push' with 'send.'(Github push)
8. I have translated "fetch" as 'preluare,' which fits the context, although I am not completely sure about this translation.
9. At the word "dialog," the translation can be 'fereastră de dialog' as an option, but I have chosen to keep it as "dialog."
10. I have made a distinction between "view" in the context of a database view and the view tab. Thus, I have translated database view to "vedere" and view (as an interface) as "vizualizare."
11. I have chosen to keep the translation of "foreign key" as 'Cheie Străină,' although the variant 'Cheie Externă' is also commonly used in many sources.
12. In the FilterLineEdit category, the translation of the word 'wildcard' is uncertain for now.
13. In the CipherDialog category, 'Raw key' could be translated as 'Cheie necriptată' instead of 'Cheia brută' in the context of password protection maybe, for now I translated as 'Cheia brută'.
14. In the RemoteDock category, the translation of 'Go' as "Continuă" fits better in the context of software/action completion instead of "Du-te". I have chosen to keep it as "Continuă(Continue)" for now.
15. The terms 'Hex blob' and 'Hex number' in the ColumnDisplayFormatDialog should be kept as they are, as 'Hex' is commonly understood by natives, an alternative 'Hexadecimal' (non-abbreviated).
16. The date formats like 'dd/mm/yyyy' in the ColumnDisplayFormatDialog should be kept untranslated as 'zz/ll/aaaa' from zi/lună/an (day/month/year) may not be as widely recognized.
17. In the DBBrowserDB category, translating 'and rolling back' to "și derulând înapoi" seems suitable. Other options like "și restabilind" or "și revenind la starea anterioară" convey similar meanings.
18. For 'peer' in the context of '( ) The row_number() of the first peer...', using 'equal' as a replacement is appropriate as 'colleague' might not fit the context.
19. Both 'Undo' and 'Cancel' translate to the same word 'Anulare', but I have noticed that when a user hovers over 'Undo', a tooltip pops up explaining its function, which should help avoid any confusion arising from the identical translations for these two words.
20. The translation for 'Check Constraints' is currently unclear to me, and I am unsure if it is entirely 100% accurate at this time.
21. The translation of the term 'call' in the 'Custom display format must contain a function call...', context, can be "apel" or "chemare", I'm not sure for now, the current translation is 'apel'.

Other

1. I am unable to find a Romanian translation for the Regular Expression link(s) on Wikibooks.
2. In Romanian, there is no paucal form, so I have used the plural form in the paucal field.
3. I have not used accelerators before and am unsure if there is a specific pattern for Romanian. I have tried to adapt every occurrence to the best key, as some letters disappear during translation.
4. All comment fields are currently empty.
5. I have not made any modifications to the code, only added the language and a small Romanian flag image.
6. There is a misspelling in TableBrowser for the word "acomplishing," which should be spelled with two 'c's as "accomplishing."(English)
7. There is a misspelling in MainWindow for the word "currenctly," which should be spelled as "currently."(English)
8. There is an unknown issue at MainWindow where I receive a warning about a missing place marker %n/%Ln in the translation. (I check it as translated)( just a remainder)