-
Notifications
You must be signed in to change notification settings - Fork 14
/
nb_NO.po
4253 lines (3728 loc) · 133 KB
/
nb_NO.po
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: translators@lists.fsfe.org\n"
"POT-Creation-Date: 2024-06-24 09:53+0000\n"
"PO-Revision-Date: 2022-01-11 09:55+0000\n"
"Last-Translator: Imre Kristoffer Eilertsen <imreeil42@gmail.com>\n"
"Language-Team: Norwegian Bokmål <https://hosted.weblate.org/projects/fsfe/"
"reuse-docs/nb_NO/>\n"
"Language: nb_NO\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
"X-Generator: Weblate 4.10.1\n"
#. type: Yaml Front Matter Hash Value: title
#: site/content/en/comparison.md
#, no-wrap
msgid "Comparison of license compliance projects"
msgstr ""
#. type: Plain text
#: site/content/en/comparison.md
msgid ""
"It is easy to get confused by the multitude of initiatives and tools that "
"help with software license compliance. Provided below is a short and "
"incomplete overview of some noteworthy projects."
msgstr ""
#. type: Plain text
#: site/content/en/comparison.md
msgid ""
"REUSE does not intend to replace, but rather complement them. We try to "
"solve unclear and missing license and copyright information at the very "
"source. We empower developers to ensure proper and exhaustive licensing of "
"their project."
msgstr ""
#. type: Bullet: '* '
#: site/content/en/comparison.md
msgid ""
"[**SPDX**](https://spdx.org) is the rock upon which REUSE is built. SPDX "
"defines a standardized way to share copyright and licensing information "
"between projects and people. Read more in [our FAQ](/faq/#what-is-spdx)."
msgstr ""
#. type: Bullet: '* '
#: site/content/en/comparison.md
msgid ""
"[**ClearlyDefined**](https://clearlydefined.io) collects and displays meta "
"and security information about a large number of projects distributed on "
"different package registries. It also motivates developers and curators to "
"extend data about a project's licensing and copyright situation. REUSE in "
"comparison concentrates on fixing the problem at the file level for "
"individual projects, which in turn will ease ClearlyDefined's efforts."
msgstr ""
#. type: Bullet: '* '
#: site/content/en/comparison.md
msgid ""
"[**OpenChain**](https://www.openchainproject.org) focuses on making Free "
"Software license compliance more transparent, predictable, and "
"understandable for participants in the software supply chain. OpenChain "
"recommends REUSE as one component to increase clarity of the licensing and "
"copyright situation, but has higher requirements to achieve full conformance."
msgstr ""
#. type: Bullet: '* '
#: site/content/en/comparison.md
msgid ""
"[**FOSSology**](https://www.fossology.org) is a toolkit for Free Software "
"compliance, stores information in a database, and includes license, "
"copyright and export scanners. It is more complex than REUSE and its helper "
"tool and rather optimized for compliance officers and lawyers. REUSE instead "
"intends to have all licensing and copyright information stored in or next to "
"the source files to safeguard this information when reused elsewhere."
msgstr ""
#. type: Bullet: '* '
#: site/content/en/comparison.md
msgid ""
"[**ORT**](https://oss-review-toolkit.org/), the OSS Review Toolkit, is a set "
"of tools that complement existing compliance projects. Its scanner tool runs "
"the license scanner of your choice on the source code of projects and their "
"transitive dependencies. With these being REUSE compliant, it will be much "
"easier for ORT to correctly determine the licenses of all files used in the "
"project."
msgstr ""
#. type: Yaml Front Matter Hash Value: title
#: site/content/en/dev.md
#, no-wrap
msgid "Help for developers"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"Licensing should be easy for developers. We provide several tools and "
"services to allow you to concentrate on coding."
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"Contents: [Helper tool](#tool), [example repositories](#repos), [REUSE API]"
"(#api), [CI/CD workflows](#ci)"
msgstr ""
#. type: Title ##
#: site/content/en/dev.md
#, fuzzy, no-wrap
#| msgid "The tool {#tool}"
msgid "Helper Tool {#tool}"
msgstr "Verktøyet {#tool}"
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"The [REUSE helper tool](https://git.fsfe.org/reuse/tool) assists with "
"achieving and confirming REUSE compliance. It downloads the full license "
"texts, adds copyright and license information to file headers, and contains "
"a linter to identify problems. Eventually, you can generate a software bill "
"of materials."
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"Read the [documentation](https://reuse.readthedocs.io) to learn more about "
"the tool. You will also find a [tool section in our FAQ](/faq/#tool) for the "
"most pressing questions."
msgstr ""
#. type: Title ##
#: site/content/en/dev.md
#, no-wrap
msgid "Example repositories {#repos}"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"What does a REUSE-compliant project look like? The following repositories "
"are basic, but each of them is REUSE-compliant. We make them available to "
"demonstrate how REUSE works in practice."
msgstr ""
#. type: Bullet: '- '
#: site/content/en/dev.md
msgid ""
"[reuse-example](https://git.fsfe.org/reuse/example) - a REUSE compliant "
"repository showing a few methods to add copyright and licensing information. "
"Includes a non-compliant branch for testing. This project is the basis for "
"[our tutorial](/tutorial)."
msgstr ""
#. type: Bullet: '- '
#: site/content/en/dev.md
msgid ""
"[reuse-tool](https://git.fsfe.org/reuse/tool) - the helper tool itself is "
"compliant, just like [all other REUSE repositories](https://git.fsfe.org/"
"reuse/)."
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"Consider registering your project with the [REUSE API](#api) to include a "
"dynamic compliance badge."
msgstr ""
#. type: Title ##
#: site/content/en/dev.md
#, no-wrap
msgid "API {#api}"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"The [REUSE API](https://api.reuse.software) helps you to continuously check "
"and display compliance with the REUSE guidelines. You can include a badge "
"indicating the live status in your README file, and parse the output using "
"the generated JSON file."
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"This is how the badge will look like for a REUSE compliant project. You can "
"click on the badge to see more information: [![REUSE status](https://api."
"reuse.software/badge/git.fsfe.org/reuse/api)](https://api.reuse.software/"
"info/git.fsfe.org/reuse/api)"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"The API is the perfect tool for everyone who wants to show that their "
"repository follows best practices in providing licensing and copyright "
"information. It allows third-party services to integrate the live REUSE "
"status, and offers a simple alternative for people who do not want to "
"install the [REUSE helper tool](#tool) for a first quick check."
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"As everything else in REUSE, the API is [publicly available](https://git."
"fsfe.org/reuse/api) under Free Software licenses."
msgstr ""
#. type: Title ##
#: site/content/en/dev.md
#, no-wrap
msgid "Pre-commit hook {#pre-commit-hook}"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"You can automatically run `reuse lint` on every commit as a pre-commit hook "
"for Git. This uses [pre-commit](https://pre-commit.com/). Once you [have it "
"installed](https://pre-commit.com/#install), add this to the `.pre-commit-"
"config.yaml` in your repository:"
msgstr ""
#. type: Fenced code block (yaml)
#: site/content/en/dev.md
#, no-wrap
msgid ""
"repos:\n"
"- repo: https://github.com/fsfe/reuse-tool\n"
" rev: v1.0.0\n"
" hooks:\n"
" - id: reuse\n"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"Then run `pre-commit install`. Now, every time you commit, `reuse lint` is "
"run in the background, and will prevent your commit from going through if "
"there was an error."
msgstr ""
#. type: Title ##
#: site/content/en/dev.md
#, no-wrap
msgid "Inclusion in CI/CD workflows {#ci}"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"REUSE can be easily integrated into your existing CI/CD processes to "
"continuously test your repository and its changes for REUSE compliance."
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"The FSFE offers a Docker image which can be used in numerous CI solutions. "
"Find a few examples below:"
msgstr ""
#. type: Title ###
#: site/content/en/dev.md
#, no-wrap
msgid "Drone"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid "Include the following snippet in your `.drone.yml` file:"
msgstr ""
#. type: Fenced code block
#: site/content/en/dev.md
#, no-wrap
msgid ""
"steps:\n"
"- name: reuse\n"
" image: fsfe/reuse:latest\n"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid "More information about Drone on [drone.io](https://drone.io)."
msgstr ""
#. type: Title ###
#: site/content/en/dev.md
#, no-wrap
msgid "GitHub"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"GitHub users can integrate the REUSE action in their workflow. Visit the "
"[action's marketplace page](https://github.com/marketplace/actions/reuse-"
"compliance-check) for usage instructions."
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"More information about GitHub Actions on [help.github.com](https://help."
"github.com/en/actions/automating-your-workflow-with-github-actions)."
msgstr ""
#. type: Title ###
#: site/content/en/dev.md
#, no-wrap
msgid "GitLab"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid "Include the following snippet in your `.gitlab-ci.yml` file:"
msgstr ""
#. type: Fenced code block
#: site/content/en/dev.md
#, no-wrap
msgid ""
"reuse:\n"
" image:\n"
" name: fsfe/reuse:latest\n"
" entrypoint: [\"\"]\n"
" script:\n"
" - reuse lint\n"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"More information about GitLab's CI on [docs.gitlab.com](https://docs.gitlab."
"com/ce/ci/quick_start/)."
msgstr ""
#. type: Title ###
#: site/content/en/dev.md
#, no-wrap
msgid "Travis CI"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid "Include the following snippet in your `.travis.yml` file:"
msgstr ""
#. type: Fenced code block
#: site/content/en/dev.md
#, no-wrap
msgid ""
"language: minimal\n"
"\n"
"services:\n"
" - docker\n"
"\n"
"before_install:\n"
"- docker pull fsfe/reuse:latest\n"
"- docker run -v ${TRAVIS_BUILD_DIR}:/data fsfe/reuse:latest lint\n"
msgstr ""
#. type: Plain text
#: site/content/en/dev.md
msgid ""
"More information on Travis CI on [travis-ci.com](https://travis-ci.com)."
msgstr ""
#. type: Yaml Front Matter Hash Value: title
#: site/content/en/resources.md
#, no-wrap
msgid "Resources"
msgstr ""
#. type: Plain text
#: site/content/en/resources.md
msgid ""
"You have already explored parts of the REUSE universe and would like to go "
"one step further? Read more background, get in touch with the community and "
"help us spread the word!"
msgstr ""
#. type: Plain text
#: site/content/en/resources.md
#, no-wrap
msgid ""
"{{< component fa=\"fas fa-users\" headline=\"Get in touch\" id=\"contact\" >}}\n"
" Just like Free Software, the REUSE project is based on its community \n"
" and the people who support and adopt it. Become part of it by joining \n"
" the [mailing list](https://lists.fsfe.org/mailman/listinfo/reuse) to \n"
" get to know other users, and influence the way REUSE evolves. \n"
" Likewise, you can directly contact the REUSE coordinators throughout \n"
" our mailing list.\n"
"{{< /component >}}\n"
msgstr ""
#. type: Plain text
#: site/content/en/resources.md
#, no-wrap
msgid ""
"{{< component fa=\"fas fa-rocket\" headline=\"REUSE Booster\">}}\n"
" To help even more projects adopt the REUSE best practices, we have \n"
" initiated [REUSE Booster](/booster/): a program that gives Free \n"
" Software projects the opportunity to reach out to us and receive help \n"
" by the FSFE’s licensing experts. Our REUSE Booster team is also \n"
" actively reaching out to projects. With individual assessments and \n"
" direct technical assistance, we boost the communication of \n"
" licensing and copyright information. \n"
"{{< /component >}}\n"
msgstr ""
#. type: Plain text
#: site/content/en/resources.md
#, no-wrap
msgid ""
"{{< component fa=\"fas fa-info-circle\" headline=\"Latest news\">}}\n"
" REUSE evolves rapidly thanks to its active community. Have a look at the\n"
" [latest official news](https://fsfe.org/tags/tagged-reuse.html). Also make\n"
" sure to sign up the [mailing\n"
" list](https://lists.fsfe.org/mailman/listinfo/reuse) to stay up-to-date with\n"
" the most important discussions.\n"
"{{< /component >}}\n"
msgstr ""
#. type: Plain text
#: site/content/en/resources.md
#, no-wrap
msgid ""
"{{< component fa=\"fas fa-exchange-alt\" headline=\"Similar initiatives\">}}\n"
" There are many initiatives working on Free Software licensing and compliance.\n"
" REUSE contributes to this effort but does not replace tools and best\n"
" practices in other places of the compliance chain. Have a look at [other\n"
" projects](/comparison) we collaborate with and their specifics.\n"
"{{< /component >}}\n"
msgstr ""
#. type: Plain text
#: site/content/en/resources.md
#, no-wrap
msgid ""
"{{< component fa=\"far fa-comments\" headline=\"Spread the word\">}}\n"
" The more projects understand and adopt REUSE, the easier use and re-use of\n"
" software is for everyone. Please feel free to use ready material to spread\n"
" the word. The [REUSE graphics](https://git.fsfe.org/reuse/reuse-ci/) can be\n"
" used under a Creative Commons license. Different versions and file formats of\n"
" the REUSE video are directly [available on our download\n"
" server](https://download.fsfe.org/videos/reuse/).\n"
"{{< /component >}}\n"
msgstr ""
#. type: Yaml Front Matter Hash Value: title
#: site/content/en/supporters.md
#, no-wrap
msgid "Supporters"
msgstr ""
#. type: Plain text
#: site/content/en/supporters.md
msgid ""
"We are grateful for everyone who supports REUSE. The ever-growing ecosystem "
"of specification, documentation, helper tool, API and a lot more demands "
"time and funds. Thanks to volunteers, cooperating organisations and "
"projects, as well as corporate sponsors, REUSE can constantly evolve and "
"improve."
msgstr ""
#. type: Title ##
#: site/content/en/supporters.md
#, no-wrap
msgid "Users and adopters"
msgstr ""
#. type: Plain text
#: site/content/en/supporters.md
msgid ""
"A project that follows the REUSE best practices makes its licensing and "
"copyright situation transparent, ensures that third-party code is attributed "
"correctly, and makes it easily re-usable for other developers. Because REUSE "
"does not require a registration and can even be used offline, we don't have "
"precise user statistics. Below you can find some we know of."
msgstr ""
#. type: Bullet: '* '
#: site/content/en/supporters.md
msgid ""
"All 1000+ [compliant projects](https://api.reuse.software/projects) of the "
"REUSE API"
msgstr ""
#. type: Bullet: '* '
#: site/content/en/supporters.md
msgid ""
"Many projects of the [EU-funded Next Generation Internet project](https://"
"fsfe.org/activities/ngi/) we help to become REUSE compliant from the start."
msgstr ""
#. type: Bullet: '* '
#: site/content/en/supporters.md
msgid ""
"The KDE community made REUSE the standard for its [licensing policy](https://"
"community.kde.org/Policies/Licensing_Policy#License_Statements). Also read "
"[this interview](https://fsfe.org/news/2020/news-20201215-01.html) about "
"their rationale and path."
msgstr ""
#. type: Bullet: '* '
#: site/content/en/supporters.md
msgid ""
"Corporate licensing policies of Siemens, SAP, Huawei, Liferay and many more."
msgstr ""
#. type: Bullet: '* '
#: site/content/en/supporters.md
msgid "Large parts of the Linux Kernel with ~70% by now."
msgstr ""
#. type: Bullet: '* '
#: site/content/en/supporters.md
msgid "[You?](/tutorial/)"
msgstr ""
#. type: Plain text
#: site/content/en/supporters.md
msgid ""
"If your community or company has implemented REUSE but is not listed, feel "
"free to [contact us](/resources/#contact)."
msgstr ""
#. type: Title ##
#: site/content/en/supporters.md
#, no-wrap
msgid "Corporate Sponsors"
msgstr ""
#. type: Plain text
#: site/content/en/supporters.md
msgid ""
"We kindly invite companies to adopt and support REUSE. As standardised and "
"simple best practices for declaring copyright and licensing information "
"largely improve internal compliance processes, we are happy if corporate "
"actors contribute back to REUSE."
msgstr ""
#. type: Plain text
#: site/content/en/supporters.md
msgid ""
"If your company is interested in becoming a REUSE sponsor, [please approach "
"us](/resources/#contact)."
msgstr ""
#. type: Plain text
#: site/content/en/supporters.md
#, fuzzy, no-wrap
#| msgid "{{< toc >}}\n"
msgid "{{< supporters >}}\n"
msgstr "{{< toc >}}\n"
#. type: Yaml Front Matter Hash Value: title
#: site/content/en/faq.md
#, no-wrap
msgid "Frequently Asked Questions"
msgstr "Ofte stilte spørsmål"
#. type: Plain text
#: site/content/en/faq.md site/content/en/tutorial.md
#, no-wrap
msgid "<!-- REUSE-IgnoreStart -->\n"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"This page lists common questions and their answers when dealing with "
"licensing and copyright, and with the adoption of REUSE specifically. Please "
"note that nothing here is legal advice."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
#, no-wrap
msgid "{{< toc >}}\n"
msgstr "{{< toc >}}\n"
#. type: Title #
#: site/content/en/faq.md
#, no-wrap
msgid "General {#general}"
msgstr "Generelt {#general}"
#. type: Title ##
#: site/content/en/faq.md
#, no-wrap
msgid "I am short on time. Can you give me the quickest possible summary? {#quick-summary}"
msgstr "Har dårlig tid. Hvilke deler er viktige? {#quick-summary}"
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"We want to improve the way that people license their software projects. We "
"propose three steps to achieve this:"
msgstr ""
"For å forbedre måten folk lisensieres deres programvareprosjekter, foreslås "
"disse tre stegene:"
#. type: Title ##
#: site/content/en/faq.md site/content/en/tutorial.md
#, no-wrap
msgid "1. Choose and provide licenses {#step-1}"
msgstr "1. Velg og angi lisenser {#step-1}"
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"Choose a [Free Software](https://fsfe.org/about/basics/freesoftware) license "
"for your project. Find the SPDX identifier of your license in the [SPDX "
"License List](https://spdx.org/licenses/). Download the license text for "
"your license from the [license-list-data](https://github.com/spdx/license-"
"list-data/tree/master/text) repository and put it in the `LICENSES/` "
"directory."
msgstr ""
"Velg en [fri programvare](https://fsfe.org/about/basics/freesoftware)-lisens "
"for ditt prosjekt. Finn SPDC-identifikatoren for din lisens i [SPDX-"
"lisenslisten](https://spdx.org/licenses/). Last ned lisensteksten for din "
"lisens fra [license-list-data](https://github.com/spdx/license-list-data/"
"tree/master/text)-kodelageret og putt den i `LICENSES/`-mappen."
#. type: Title ##
#: site/content/en/faq.md site/content/en/tutorial.md
#, no-wrap
msgid "2. Add copyright and licensing information to each file {#step-2}"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid "Then, for all files, edit the header to contain the following:"
msgstr ""
#. type: Fenced code block
#: site/content/en/faq.md
#, no-wrap
msgid ""
"# SPDX-FileCopyrightText: [year] [copyright holder] <[email address]>\n"
"#\n"
"# SPDX-License-Identifier: [identifier]\n"
msgstr ""
#. type: Title ##
#: site/content/en/faq.md site/content/en/tutorial.md
#, no-wrap
msgid "3. Confirm REUSE compliance {#step-3}"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"Use the [REUSE tool](https://github.com/fsfe/reuse-tool) to automate some of "
"these steps, and to check whether you did everything correctly."
msgstr ""
#. type: Title ##
#: site/content/en/faq.md
#, no-wrap
msgid "I'm used to doing things differently; can't I just keep doing what I have always been doing? {#tradition}"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"Some people, when they first encounter REUSE, run into a couple of things "
"that are very different from what they are used to. They miss the long legal "
"blurbs at the tops of files, miss the `COPYING`/`LICENSE` file in the root "
"of the repository, think that `.license` files clutter the directory, or "
"find it very strange that even insignificant non-code files get licensing "
"headers. The different-ness of REUSE can seem peculiar in that way."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"One of REUSE's main goals is to be as compatible to existing best practices "
"as possible. It explicitly breaks with some old traditions, however. We "
"believe that REUSE is better for it. By breaking new ground, REUSE is "
"simpler, more comprehensive, and more unambiguous than it would have been if "
"we tried to maintain compatibility with traditions of old."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"Nothing prevents you from adding long legal blurbs to your headers or "
"putting a `COPYING` file in the root of your directory *anyway* though. "
"These things can be done to your liking. Some other aspects of REUSE are "
"unavoidable, however. REUSE maintains that *every single file should "
"contain licensing information*, so that even the tiniest of files get a "
"header, are accompanied by a corresponding `.license` file, or marked in a "
"bulk. These things are simply inherent to the goal of REUSE, and we hope "
"that these eccentricities will soon become commonplace, such that they would "
"no longer seem so peculiar anymore."
msgstr ""
#. type: Title ##
#: site/content/en/faq.md
#, no-wrap
msgid "Why can't I just use the metadata fields in pictures, SVG, text documents etc.? {#metadata}"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"Several file formats support the storage of metadata information within the "
"file itself, and some even contain fields for copyright and license. "
"However, we do not support these in REUSE for practical reasons:"
msgstr ""
#. type: Bullet: '1. '
#: site/content/en/faq.md
msgid ""
"For humans and machines alike it's not always trivial to spot this "
"information. REUSE intents to make it simple to find licensing and copyright "
"information."
msgstr ""
#. type: Bullet: '2. '
#: site/content/en/faq.md
msgid ""
"Some tools redact metadata fields, for example to make files smaller or "
"remove potentially sensible personal information. This could also wipe your "
"or someone else's copyright information, and detecting this mistake is hard."
msgstr ""
#. type: Bullet: '3. '
#: site/content/en/faq.md
msgid ""
"With some file types, there are competing and unstandardised methods to "
"store metadata."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"This question is also related to [why we cannot use version control to "
"record copyright](#vcs-copyright)."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
#, no-wrap
msgid "<!-- ## Do I really need to include the license and copyright headers in all files? Why should I care? {#why-care}\n"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
#, no-wrap
msgid "TODO -->\n"
msgstr ""
#. type: Title ##
#: site/content/en/faq.md
#, no-wrap
msgid "What is SPDX? {#what-is-spdx}"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"SPDX stands for [Software Package Data Exchange](https://spdx.org/). It is a "
"project by the [Linux Foundation](https://www.linuxfoundation.org/) and the "
"rock upon which REUSE is built. SPDX defines a standardized way to share "
"copyright and licensing information between projects and people. Most "
"importantly for REUSE, SPDX maintains the [SPDX License List](https://spdx."
"org/licenses/), which defines standardized identifiers for a lot of licenses."
msgstr ""
#. type: Title #
#: site/content/en/faq.md
#, no-wrap
msgid "The tool {#tool}"
msgstr "Verktøyet {#tool}"
#. type: Title ##
#: site/content/en/faq.md
#, no-wrap
msgid "How do I install and use the REUSE tool? {#install-tool}"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"The REUSE tool is a handy companion that can verify your compliance with "
"REUSE and automate a lot of adjacent tasks. You can find the full "
"documentation for the tool at <https://reuse.readthedocs.io/>. But the short "
"of it is:"
msgstr ""
#. type: Fenced code block
#: site/content/en/faq.md
#, no-wrap
msgid ""
"$ pip3 install --user fsfe-reuse\n"
"$ export PATH=~/.local/bin:$PATH\n"
"$ reuse --help\n"
msgstr ""
#. type: Title ##
#: site/content/en/faq.md
#, no-wrap
msgid "How do I exclude a file from REUSE compliance testing? {#exclude-file}"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"If the file is a build artifact and you use Git, simply make sure that the "
"file is covered by your `.gitignore` file."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"Otherwise, you cannot exclude files from REUSE compliance testing. It would "
"go entirely against the purpose of REUSE: making sure that every file has a "
"copyright and license tag."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"If you really want to exclude a file, consider using the [CC0](https://"
"creativecommons.org/publicdomain/zero/1.0/) license for this file. By doing "
"this, you put the file in the [public domain, or your country's equivalent]"
"(https://fsfe.org/freesoftware/legal/faq.html#public-domain)."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"There is one exception: License files are automatically excluded from "
"compliance testing."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"If you have an entire directory that you want to \"exclude\" from REUSE "
"compliance testing, you can [use a DEP5 file](#bulk-license)."
msgstr ""
#. type: Title ##
#: site/content/en/faq.md
#, no-wrap
msgid "How do I exclude certain lines from REUSE compliance testing? {#exclude-lines}"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"In order to make the tool ignore a specific section containing strings that "
"may falsely be detected as copyright or license statements, you can wrap it "
"within the two comments `REUSE-IgnoreStart` and `REUSE-IgnoreEnd`."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"Please note that this must not be used to ignore valid copyright and "
"licensing information by yourself or a third party. The ignore blocks must "
"only be used for marking blocks that may trigger false-positive detections "
"and errors."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"An example for a file that contains commands or documentation that confuse "
"the REUSE helper tool:"
msgstr ""
#. type: Fenced code block
#: site/content/en/faq.md
#, no-wrap
msgid ""
"# SPDX-FileCopyrightText: 2021 Jane Doe\n"
"#\n"
"# SPDX-License-Identifier: GPL-3.0-or-later\n"
"\n"
"echo \"SPDX-FileCopyrightText: $(date +'%Y') John Doe\" > file.txt\n"
"echo \"SPDX-License-Identifier: MIT\" >> file.txt\n"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"The tool would complain that it cannot parse the license in the last line "
"and it would falsely understand the second-last line as an additional "
"copyright holder:"
msgstr ""
#. type: Fenced code block
#: site/content/en/faq.md
#, no-wrap
msgid ""
"reuse._util - ERROR - Could not parse 'MIT\" > file.txt'\n"
"reuse.project - ERROR - 'foobar.sh' holds an SPDX expression that cannot be parsed, skipping the file\n"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid "This is how the section that causes these errors can be ignored:"
msgstr ""
#. type: Fenced code block
#: site/content/en/faq.md
#, no-wrap
msgid ""
"# SPDX-FileCopyrightText: 2021 Jane Doe\n"
"#\n"
"# SPDX-License-Identifier: GPL-3.0-or-later\n"
"\n"
"# REUSE-IgnoreStart\n"
"echo \"SPDX-FileCopyrightText: $(date +'%Y') John Doe\" > file.txt\n"
"echo \"SPDX-License-Identifier: MIT\" >> file.txt\n"
"# REUSE-IgnoreEnd\n"
msgstr ""
#. type: Title ##
#: site/content/en/faq.md
#, no-wrap
msgid "Do you support a version control system other than Git? {#no-git}"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"Yes, the helper tool also supports [Mercurial](https://www.mercurial-scm."
"org/). If you miss another version control system, please consider creating "
"an issue or ideally a pull request in the [tool's repository](https://github."
"com/fsfe/reuse-tool)."
msgstr ""
#. type: Title #
#: site/content/en/faq.md
#, no-wrap
msgid "Copyright {#copyright}"
msgstr ""
#. type: Title ##
#: site/content/en/faq.md
#, no-wrap
msgid "What is copyright? {#what-is-copyright}"
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"Copyright is a legal construct that grants someone exclusive rights over a "
"creative work. The most important exclusive right is in the name: The right "
"to produce copies. Only the copyright holder is allowed to give new copies "
"of their work to people."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"Usually the author is the copyright holder, but often copyright is "
"transferred to the author's employer. In most places, you do not need to do "
"anything to gain copyright. As soon as you make a creative work, you (or "
"your employer) instantly gain copyright over it."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
msgid ""
"Creative Commons provides a better and lengthier answer in their [Frequently "
"Asked Questions](https://creativecommons.org/faq/#what-is-copyright-and-why-"
"does-it-matter)."
msgstr ""
#. type: Plain text
#: site/content/en/faq.md
#, no-wrap
msgid "<!-- ## Which licenses are compatible? {#compatible-licenses} -->\n"
msgstr ""
#. type: Title ##
#: site/content/en/faq.md
#, no-wrap
msgid "Is there a standard format for declaring copyright? {#standard-copyright}"
msgstr ""