Danish term
Fast, Reliable & Accurate Translations
Native in: English
Works in: Spanish to English, Swedish to English
angive (this context)
I have a reference document from the client in English which always translates 'angive' as 'specify'. E.g:
If the data type is a numeric integer or a decimal number, the reference is specified with the selected code list name and a trailing full-stop
I also have a reference from the client which uses the term 'declare' E.g:
In row number 20 in the data file mydata the variable measure1 has a value 2001 , with a length that is longer than the length declared in the data format notation f1.0 for that variable under the subtitle VARIABEL in the metadata file Table1
What I'm wondering is whether there is a specific/standard way to express this, or if give/specify/declare/state, etc, are all valid translations.
Examples from the text:
Koden {2} for variablen {1} under etiketten BRUGERKODE angivet i metadatafilen {0} stemmer ikke overens med dataformatnotationen {3} (numerisk decimaltal) for variablen
Etiketnavne skal angives med store bogstaver.
Tomme værdier i datafilen må ikke angives med koder som NA, NaN, none, n.a. og NULL, punktum eller lignende, men skal altid angives enten med ingen værdi »«, eller et mellemrum » « (U+0020).
En angivet nøglevariabel begynder med et tal.
Hvis datafilnavnet angivet er et reserveret ord i SQL:1999 skal datafilnavnet omkranses af dobbeltapostroffer.
Any help much appreciated!
Michael
| 3 +1 | appear; write; enter; state; state |
Thomas T. Frost
|
| 2 | display (the date file name etc.) |
Adrian MM.
|
| 1 | designate |
Diarmuid Kennan
|
Non-PRO (1): Christopher Schröder
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
Portugal
‘Very good precision work’ – Comunica.dk
Native in: Danish (Variant: Standard (rigsdansk)) 
, English (Variants: UK, British)
Works in: Danish to English, English to Danish, French to Danish
appear; write; enter; state; state
The above suggestions correspond to the five examples you have stated at the end:
'The code \{2\} for the variable \{1\} under the label BRUGERKODE that appears in the meta data file {0} …': The text does not refer to the action of entering the code here; it's just sitting there already, doing nothing. Actually you could leave out 'that appears' altogether without changing the meaning. It's mainly fluff.
'Label names must be written in uppercase.'
As for 'NA' etc., it seems to be about how they are entered.
I would use 'state' in the last two examples, I think. But I might also change my mind a few times while working through a text like this. I suggest you play it by ear.
Some other translations of 'angive'/'anføre' that may or may not be appropriate in a given context:
set out
set forth
emphasise
define
lay down
indicate
set
provide
mention
| agree |
Christopher Schröder
5 hrs
|
|
Thanks, Chris. I'm glad you agree with my scattergun approach. I hope you ducked at the right time.
|
|
| neutral |
Adrian MM.
: yes, scattergun so utterly inconclusive.
17 hrs
|
|
Because there’s no one-size-fits-all solution to translating 'angive' and the Asker has given context and 5 examples. So I’ve given 5 conclusive answers to the 5 examples. I can’t do miracles. Microsoft’s term base is just as inconclusive, as you call it.
|
Ireland
Reliable and accurate
Native in: English 
Works in: Danish to English, Norwegian to English, Swedish to English
designate
Austria
Retd.T&I, Barrister & Austro-Advokat
Native in: English (Variants: British, Scottish)
Works in: Spanish to English, English to Spanish, French to English, and 5 more.
display (the date file name etc.)
Tomme værdier i datafilen må ikke angives med koder > --- must be displayed---
I was going to use 'indicate' but noticed that such permutation has already been fired by the scatter-gun answer.
Otherwise, the clients need (to) be consulted over their own inconsistency of specify vs. declare and, on that footing or (IrE) on foot of such variance, whether they would insist on a single, different term throughout. Some clients (notably lawyers and adversiting agents) tend to be very touchy about diversifying out of a one-size-fits-all approach.
C = textscan( fileID , formatSpec ) reads data from an open text file into a cell array, C . The text file is indicated by the file identifier, fileID
Select the Data Files tab. Double click on the pst-file for which you want to change the display name-
| neutral |
Christopher Schröder
: I think it's more about the input than the output here // That's not what I meant but never mind :-)
4 hrs
|
|
I'd thought of input but 1. too far from the Danish and 2. problem with the past tense: input or inputted. // again, I was going to use input or - as already scattergunned by Thmas F. - entered e.g. into the system.
|
Discussion