@@ -11,7 +11,7 @@ msgid ""
1111msgstr ""
1212"Project-Id-Version : Python 3.9\n "
1313"Report-Msgid-Bugs-To : \n "
14- "POT-Creation-Date : 2021-04-26 06:10 +0000\n "
14+ "POT-Creation-Date : 2021-05-23 06:25 +0000\n "
1515"PO-Revision-Date : 2017-02-16 17:43+0000\n "
1616"Last-Translator : oon arfiandwi <oon.arfiandwi@gmail.com>, 2021\n "
1717"Language-Team : Indonesian (https://www.transifex.com/python-doc/teams/5390/id/)\n "
@@ -237,16 +237,17 @@ msgstr "Bagaimana cara membuat sebuah executable dari skrip Python?"
237237
238238#: ../../faq/windows.rst:143
239239msgid ""
240- "See `cx_Freeze <https://cx-freeze.readthedocs.io/en/latest/>`_ and `py2exe "
241- "<http://www.py2exe.org/>`_, both are distutils extensions that allow you to "
242- "create console and GUI executables from Python code."
240+ "See :ref:`faq-create-standalone-binary` for a list of tools that can be used"
241+ " to make executables."
243242msgstr ""
243+ "Lihat :ref:`faq-create-standalone-binary` untuk daftar perkakas yang dapat "
244+ "digunakan membuat aplikasi yang dapat dieksekusi."
244245
245- #: ../../faq/windows.rst:149
246+ #: ../../faq/windows.rst:148
246247msgid "Is a ``*.pyd`` file the same as a DLL?"
247248msgstr "Apakah file ``*.pyd`` sama dengan DLL?"
248249
249- #: ../../faq/windows.rst:151
250+ #: ../../faq/windows.rst:150
250251msgid ""
251252"Yes, .pyd files are dll's, but there are a few differences. If you have a "
252253"DLL named ``foo.pyd``, then it must have a function ``PyInit_foo()``. You "
@@ -263,7 +264,7 @@ msgstr ""
263264"menautkan .exe Anda dengan foo.lib, karena hal itu akan menyebabkan Windows "
264265"memerlukan DLL."
265266
266- #: ../../faq/windows.rst:158
267+ #: ../../faq/windows.rst:157
267268msgid ""
268269"Note that the search path for foo.pyd is PYTHONPATH, not the same as the "
269270"path that Windows uses to search for foo.dll. Also, foo.pyd need not be "
@@ -282,19 +283,19 @@ msgstr ""
282283"``__declspec(dllexport)``. Di file .pyd, keterkaitan didefinisikan sebagai "
283284"sebuah list dari fungsi yang tersedia."
284285
285- #: ../../faq/windows.rst:167
286+ #: ../../faq/windows.rst:166
286287msgid "How can I embed Python into a Windows application?"
287288msgstr "Bagaimana cara memasukkan Python ke dalam aplikasi Windows?"
288289
289- #: ../../faq/windows.rst:169
290+ #: ../../faq/windows.rst:168
290291msgid ""
291292"Embedding the Python interpreter in a Windows app can be summarized as "
292293"follows:"
293294msgstr ""
294295"Menyematkan interpreter Python di aplikasi Windows dapat diringkas menjadi "
295296"sebagai:"
296297
297- #: ../../faq/windows.rst:171
298+ #: ../../faq/windows.rst:170
298299msgid ""
299300"Do _not_ build Python into your .exe file directly. On Windows, Python must"
300301" be a DLL to handle importing modules that are themselves DLL's. (This is "
@@ -309,7 +310,7 @@ msgstr ""
309310"``C:\\ Windows\\ System``. *NN* adalah Python versi, angka seperti \" 33\" "
310311"untuk Python 3.3."
311312
312- #: ../../faq/windows.rst:177
313+ #: ../../faq/windows.rst:176
313314msgid ""
314315"You can link to Python in two different ways. Load-time linking means "
315316"linking against :file:`python{NN}.lib`, while run-time linking means linking"
@@ -324,7 +325,7 @@ msgstr ""
324325" dengan :file:`python{NN}.dll`. itu hanya mendefinisikan simbol untuk "
325326"linker.)"
326327
327- #: ../../faq/windows.rst:183
328+ #: ../../faq/windows.rst:182
328329msgid ""
329330"Run-time linking greatly simplifies link options; everything happens at run "
330331"time. Your code must load :file:`python{NN}.dll` using the Windows "
@@ -342,15 +343,15 @@ msgstr ""
342343" menggunakan pointer tersebut ke kode C apapun yang memanggil rutinitas di C"
343344" Python API."
344345
345- #: ../../faq/windows.rst:190
346+ #: ../../faq/windows.rst:189
346347msgid ""
347348"Borland note: convert :file:`python{NN}.lib` to OMF format using "
348349"Coff2Omf.exe first."
349350msgstr ""
350351"Catatan Borland: ubah :file:`python{NN}.lib` ke format OMF menggunakan "
351352"Coff20mf.exe terlebih dahulu."
352353
353- #: ../../faq/windows.rst:195
354+ #: ../../faq/windows.rst:194
354355msgid ""
355356"If you use SWIG, it is easy to create a Python \" extension module\" that "
356357"will make the app's data and methods available to Python. SWIG will handle "
@@ -364,7 +365,7 @@ msgstr ""
364365"Hasilnya adalah kode C Anda yang terkaitkan ke .exe file Anda (!) Kamu "
365366"tidak perlu membuat sebuah file DLL, dan ini juga memudahkan proses linking."
366367
367- #: ../../faq/windows.rst:201
368+ #: ../../faq/windows.rst:200
368369msgid ""
369370"SWIG will create an init function (a C function) whose name depends on the "
370371"name of the extension module. For example, if the name of the module is "
@@ -379,7 +380,7 @@ msgstr ""
379380"kelas pembantu yang sebagian besar tersembunyi yang digunakan oleh kelas "
380381"bayangan."
381382
382- #: ../../faq/windows.rst:207
383+ #: ../../faq/windows.rst:206
383384msgid ""
384385"The reason you can link the C code in step 2 into your .exe file is that "
385386"calling the initialization function is equivalent to importing the module "
@@ -389,15 +390,15 @@ msgstr ""
389390"itu memanggil fungsi inisialisasi sama dengan mengimpor modul ke dalam "
390391"Python! (Ini adalah fakta kunci tak terdokumentasi kedua.)"
391392
392- #: ../../faq/windows.rst:211
393+ #: ../../faq/windows.rst:210
393394msgid ""
394395"In short, you can use the following code to initialize the Python "
395396"interpreter with your extension module."
396397msgstr ""
397398"Singkatnya, Anda dapat menggunakan kode berikut untuk menginisialisasi "
398399"Python interpreter dengan ekstensi modul Anda."
399400
400- #: ../../faq/windows.rst:222
401+ #: ../../faq/windows.rst:221
401402msgid ""
402403"There are two problems with Python's C API which will become apparent if you"
403404" use a compiler other than MSVC, the compiler used to build pythonNN.dll."
@@ -406,7 +407,7 @@ msgstr ""
406407"kompilator selain MSVC, kompilator yang digunakan untuk membangun "
407408"pythonNN.dll."
408409
409- #: ../../faq/windows.rst:225
410+ #: ../../faq/windows.rst:224
410411msgid ""
411412"Problem 1: The so-called \" Very High Level\" functions that take FILE * "
412413"arguments will not work in a multi-compiler environment because each "
@@ -418,15 +419,15 @@ msgstr ""
418419"masing-masing Gagasan kompiler tentang struct FILE akan berbeda. Dari sebuah"
419420" sudut pandang implementasi ini adalah fungsi level yang sangat _low_."
420421
421- #: ../../faq/windows.rst:230
422+ #: ../../faq/windows.rst:229
422423msgid ""
423424"Problem 2: SWIG generates the following code when generating wrappers to "
424425"void functions:"
425426msgstr ""
426427"Masalah 2: SWIG menghasilkan kode berikut saat membuat wrappers ke dalam "
427428"fungsi void:"
428429
429- #: ../../faq/windows.rst:239
430+ #: ../../faq/windows.rst:238
430431msgid ""
431432"Alas, Py_None is a macro that expands to a reference to a complex data "
432433"structure called _Py_NoneStruct inside pythonNN.dll. Again, this code will "
@@ -436,7 +437,7 @@ msgstr ""
436437"struktur yang disebut _Py_NoneStruct di dalam pythonNN.dll. Sekali lagi, "
437438"kode ini akan gagal di lingkungan mult-compiler. Ganti kode tersebut dengan:"
438439
439- #: ../../faq/windows.rst:247
440+ #: ../../faq/windows.rst:246
440441msgid ""
441442"It may be possible to use SWIG's ``%typemap`` command to make the change "
442443"automatically, though I have not been able to get this to work (I'm a "
@@ -446,7 +447,7 @@ msgstr ""
446447"perubahan secara otomatis, meskipun saya belum bisa membuat ini berfungsi "
447448"(saya adalah pemula SWIG)."
448449
449- #: ../../faq/windows.rst:251
450+ #: ../../faq/windows.rst:250
450451msgid ""
451452"Using a Python shell script to put up a Python interpreter window from "
452453"inside your Windows app is not a good idea; the resulting window will be "
@@ -466,12 +467,12 @@ msgstr ""
466467"semua yang Anda butuhkan adalah objek Python (didefinisikan dalam modul "
467468"ekstensi Anda) yang berisi metode read() dan write()."
468469
469- #: ../../faq/windows.rst:260
470+ #: ../../faq/windows.rst:259
470471msgid "How do I keep editors from inserting tabs into my Python source?"
471472msgstr ""
472473"Bagaimana cara mencegah editor memasukkan tab ke dalam sumber Python saya?"
473474
474- #: ../../faq/windows.rst:262
475+ #: ../../faq/windows.rst:261
475476msgid ""
476477"The FAQ does not recommend using tabs, and the Python style guide, :pep:`8`,"
477478" recommends 4 spaces for distributed Python code; this is also the Emacs "
@@ -481,7 +482,7 @@ msgstr ""
481482":pep:`8`, merekomendasikan dengan 4 spasi untuk distribusi kode Python; ini "
482483"juga Emacs python-mode secara default."
483484
484- #: ../../faq/windows.rst:266
485+ #: ../../faq/windows.rst:265
485486msgid ""
486487"Under any editor, mixing tabs and spaces is a bad idea. MSVC is no "
487488"different in this respect, and is easily configured to use spaces: Take "
@@ -495,7 +496,7 @@ msgstr ""
495496"tipe \" Default\" set \" Tab size\" dan \" Indent size\" menjadi 4, dan pilih "
496497"\" Insert spaces\" tombol radio."
497498
498- #: ../../faq/windows.rst:271
499+ #: ../../faq/windows.rst:270
499500msgid ""
500501"Python raises :exc:`IndentationError` or :exc:`TabError` if mixed tabs and "
501502"spaces are causing problems in leading whitespace. You may also run the "
@@ -506,11 +507,11 @@ msgstr ""
506507"Anda juga dapat menjalankan :mod:`tabnanny` modul untuk mengecek sebuah "
507508"direktori di mode batch."
508509
509- #: ../../faq/windows.rst:278
510+ #: ../../faq/windows.rst:277
510511msgid "How do I check for a keypress without blocking?"
511512msgstr "Bagaimana cara memeriksa tombol yang ditekan tanpa memblokir?"
512513
513- #: ../../faq/windows.rst:280
514+ #: ../../faq/windows.rst:279
514515msgid ""
515516"Use the :mod:`msvcrt` module. This is a standard Windows-specific extension"
516517" module. It defines a function ``kbhit()`` which checks whether a keyboard "
0 commit comments