-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminology Dictionary #4
Comments
Nouns
Verbs
Phrases
|
Changes incorporated, thanks! |
Incorporated changes from https://pastebin.com/egGdebv1 per request. |
Some more trouble words:
I know that gälla is used for the sense of like "this applies only to ..." and tillämpa is sort of like "use in practice" and applicera is like to apply as in "to the skin" as well as some other meanings and so on. But in a programming context? Like to "apply a transition effect" for example? I have no idea. Seems safest to go with applicera, so that's what I have been doing. |
Array can be translated as fält, uppställning or tabell but since we use fält for field I think we should stick to tabell? |
The only change in your list is to use As for Lastly, I think Array should be added to the "no translation required" list with an initial translation only once: |
See that's the thing, I would have thought that it'd make more sense to use the "no translation required" list for uncommon terms. Basically I've been going off of "if I can find several Wikipedia articles relating to computer science that use the Swedish term then it's a valid term". And tabell and fält as far as I can tell are valid terms. We definitely need to come to an agreement, in any case. It might be helpful to create some kind of script or I suppose git hook that checks that we are conforming to our conventions, even? I can maybe look into that though I'm not sure how good of an idea it actually is. Especially considering the surface area we have to cover (i.e. not so much that doing it manually is a great hassle). |
Some more I'm unsure about:
It might actually be useful for me (I probably have more free time!) to do a sweep of the docs and make a list of all the terms that I think could be a problem. Then we can figure all of this out in one fell swoop and afterwards simply focus on the actual task at hand. Another approach would be to just leave the English word/term/phrasing in for all of these kinds of occurences and then when we're done translating the rest we can compile a list, decide which should be translated, which shouldn't then basically find-and-replace the code- uhh I mean docsbase. Thoughts? |
I like the idea with a script 😄 E.g.
➡️
|
Essentially, insert the magic string ”REPLACE” when in any doubt. This results in a single CTRL+F action when later applying terms that eventually get agreed upon. |
I quite like the convention idea but that becomes slightly more complicated when you take into account all possible conjugations... no? Surely for it to be truly worthwhile (and for us to be able to automatically replace all occurrences) we would need to do e.g. |
Sure, just adding a Okay, I think I'm just gonna add a (The word translate is far less likely to be used in the docs than replace). |
Then we can grep the entire "codebase" when we're "done". Sounds like a plan? |
Yes, TRANSLATE it is. Yup, I just realized that automatically replacing is a lot more complicated as you say, and isn’t a realistic approach 😂 |
@Pwntus I have adopted this convention in the current document:
👍 |
Examples:
I think this is pretty good? (Some of those translations are soooo awkward, I know). |
Yes this is even better. When possible, a separate issue should be made, explaining the convention for (possibly) other translators to see. |
If you know a translation that I'm missing (see unchecked items below) or have a better translation than the one I'm using then please leave a comment.
I don't have very much experience with strictly technical reading/writing in this language, hence the need for this little dictionary.
Technical Dictionary
No Translation Required
NOTE: Recommended to translate upon first occurrence but not afterwards.
Nouns
| en abstraktion | an abstraction |
| ett användargränssnitt | a user interface |
| ett attribut | an attribute |
| ett bibliotek | a library |
| en bindning | a binding |
| en cache | a cache |
| ett direktiv | a directive |
| en egenskap | a property |
| (ett) element | an element |
| en flik | a tab |
| en frontendutvecklare | a front-end developer |
| en funktion | a feature; a function |
| ett fält | a field |
| (en) inmatning | (an) input |
| en instans | an instance |
| en klass | a class |
| (en) kod | (a) code |
| en kommandorad | a command-line interpeter |
| en komponent | a component |
| en konstruktor | a constructor |
| en kryssruta | a checkbox |
| (en) logik | (a) logic |
| en mall | a template |
| en metod | a method |
| en operatör | an operator |
| en parameter | a parameter |
| (en) prestanda | (a) performance |
| ett ramverk | a framework |
| en scope; (en räckvidd) | a scope |
| en syntax; (en satslära) | a syntax |
| en styrstruktur | a control structure |
| en slinga | a loop |
| ett tillstånd | a state |
| en transition | a transition |
| ett uttryck | an expression |
| en variabel | a variable |
| en verktyg | a tool; (a) tooling |
| ett värde | a value |
| ett repo | a repository (i.e. SCM) |
| ett villkor | a conditional |
| (en) verktyg | (a) tooling |
Adjectives
Verbs
Phrases
Hard to translate
The text was updated successfully, but these errors were encountered: